This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H
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 08 22.3424 2461274.8424 12.10 23:35:00.69 +50:11:06.2
110.60994 -10.84929 galactic And Second-epoch detections are separated by 1.4" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:35:00.69 +50:11:06.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:00.69 +50:11:06.2: 15.43 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:00.69 +50:11:06.2: 14.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 35 00.69 +50 11 06.2 12.1 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,2461274.8424,12.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 12.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 12.02 23:24:00.53 +54:33:47.5
110.39229 -6.16600 galactic Cas Second-epoch detections are separated by 4.9" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:00.53 +54:33:47.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:00.53 +54:33:47.5: 15.32 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:00.53 +54:33:47.5: 14.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 00.53 +54 33 47.5 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 12.08 23:34:35.47 +50:44:04.8
110.71109 -10.30462 galactic Cas Second-epoch detections are separated by 2.8" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:35.47 +50:44:04.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:35.47 +50:44:04.8: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:35.47 +50:44:04.8: 14.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 35.47 +50 44 04.8 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,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
target 20260822.3424 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 08 22.3424 2461274.8424 12.02 23:35:15.89 +55:34:27.5
112.24869 -5.70949 galactic Cas Second-epoch detections are separated by 1.5" and 5.5 pix
The object was found in VSX16" ZTF J233517.72+553431.1
Type: BY
# Max. Min./Amp. JD0 Period
17.494 r Y 0.081 r 2458278.97240 1.306261700000
ATTENTION: measured mag 12.02 is 5.4 mag brighter than the VSX record maximum brightness 17.41 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:15.89 +55:34:27.5: 15.33 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:15.89 +55:34:27.5: 14.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 35 15.89 +55 34 27.5 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J233517.72+553431.1,2461274.8424,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J233517.72+553431.1 20260822.3424 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 11.63 23:45:25.38 +54:19:00.2
113.31473 -7.31773 galactic Cas Second-epoch detections are separated by 5.8" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:25.38 +54:19:00.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:45:25.38 +54:19:00.2: 15.57 +/- 0.36 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:45:25.38 +54:19:00.2: 14.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.57 +/- 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 08 22.3424* 23 45 25.38 +54 19 00.2 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
target,2461274.8424,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 11.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 10.61 23:21:42.62 +50:06:35.8
108.53280 -10.23645 galactic And Second-epoch detections are separated by 2.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.4335+50.1053 | 23:21:42.62 +50:06:35.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:42.62 +50:06:35.8: 15.33 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:42.62 +50:06:35.8: 14.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 42.62 +50 06 35.8 10.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 J350.4335+50.1053,2461274.8424,10.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
ATO J350.4335+50.1053 20260822.3424 10.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 08 22.3424 2461274.8424 11.32 00:15:49.03 +57:32:30.9
118.14815 -4.99860 galactic Cas Second-epoch detections are separated by 0.6" and 5.9 pix
The object was found in VSX16" FN Cas
Type: M
# Max. Min./Amp. JD0 Period
12.800 pg < 17.400 pg 2435507.00000 173.900000000000 M3
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:49.03 +57:32:30.9: 12.73 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:15:49.03 +57:32:30.9: 12.93 +/- 0.06 detection
Forced photometry reference-image weighted average: 12.77 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 15 49.03 +57 32 30.9 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
FN Cas,2461274.8424,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
FN Cas 20260822.3424 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 08 22.3424 2461274.8424 11.64 00:00:07.62 +51:20:28.5
114.81721 -10.72025 galactic Cas Second-epoch detections are separated by 5.8" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:07.62 +51:20:28.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:07.62 +51:20:28.5: 14.16 +/- 0.10 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:07.62 +51:20:28.5: 14.87 +/- 0.35 detection
Forced photometry reference-image weighted average: 14.21 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 00 07.62 +51 20 28.5 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
target,2461274.8424,11.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 11.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 11.88 00:15:00.49 +53:35:32.6
117.47541 -8.89296 galactic Cas Second-epoch detections are separated by 3.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:00.49 +53:35:32.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:00.49 +53:35:32.6: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:15:00.49 +53:35:32.6: 14.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 15 00.49 +53 35 32.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
target,2461274.8424,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 20260822.3424 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 08 22.3424 2461274.8424 14.29 23:16:18.05 +55:26:09.5
109.65480 -4.96416 galactic Cas Second-epoch detections are separated by 8.1" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1997075542566312832 | 23:16:23.37 +55:26:18.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:16:18.05 +55:26:09.5: 15.43 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:16:18.05 +55:26:09.5: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 16 18.05 +55 26 09.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997075542566312832,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997075542566312832 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.38 00:23:16.42 +54:07:27.3
118.76643 -8.51955 galactic Cas Second-epoch detections are separated by 6.8" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:16.42 +54:07:27.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:23:16.42 +54:07:27.3: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:23:16.42 +54:07:27.3: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 23 16.42 +54 07 27.3 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:34:55.40 +53:37:35.0
111.62649 -7.55743 galactic Cas Second-epoch detections are separated by 2.4" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:55.40 +53:37:35.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:55.40 +53:37:35.0: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:55.40 +53:37:35.0: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 55.40 +53 37 35.0 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.32 23:24:46.04 +55:53:02.9
110.93483 -4.95563 galactic Cas Second-epoch detections are separated by 5.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:46.04 +55:53:02.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:46.04 +55:53:02.9: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:46.04 +55:53:02.9: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 46.04 +55 53 02.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.47 00:15:37.89 +51:47:05.9
117.31030 -10.69552 galactic Cas Second-epoch detections are separated by 8.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:37.89 +51:47:05.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:37.89 +51:47:05.9: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:15:37.89 +51:47:05.9: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 15 37.89 +51 47 05.9 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.53 23:37:30.27 +55:27:05.5
112.51837 -5.91830 galactic Cas Second-epoch detections are separated by 4.1" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:30.27 +55:27:05.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:30.27 +55:27:05.5: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:30.27 +55:27:05.5: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 30.27 +55 27 05.5 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 23:35:59.38 +55:24:07.8
112.29716 -5.90403 galactic Cas Second-epoch detections are separated by 6.9" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:35:59.38 +55:24:07.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:59.38 +55:24:07.8: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:59.38 +55:24:07.8: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 35 59.38 +55 24 07.8 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.21 23:52:24.98 +54:32:28.7
114.36444 -7.34569 galactic Cas Second-epoch detections are separated by 3.4" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:24.98 +54:32:28.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:24.98 +54:32:28.7: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:24.98 +54:32:28.7: 15.10 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 24.98 +54 32 28.7 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:39:02.44 +55:35:25.1
112.76731 -5.84615 galactic Cas Second-epoch detections are separated by 2.2" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:39:02.44 +55:35:25.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:39:02.44 +55:35:25.1: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:39:02.44 +55:35:25.1: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 39 02.44 +55 35 25.1 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.15 23:17:57.18 +52:26:57.5
108.80639 -7.83966 galactic And Second-epoch detections are separated by 6.6" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1992585141374213248 | 23:17:53.56 +52:27:11.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:57.18 +52:26:57.5: 15.30 +/- 0.33 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:57.18 +52:26:57.5: 14.82 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.30 +/- 0.33
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 57.18 +52 26 57.5 14.2 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 1992585141374213248,2461274.8424,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1992585141374213248 20260822.3424 14.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.37 23:52:13.43 +52:40:04.3
113.90202 -9.16261 galactic Cas Second-epoch detections are separated by 8.9" and 3.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:52:13.43 +52:40:04.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:13.43 +52:40:04.3: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:13.43 +52:40:04.3: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 13.43 +52 40 04.3 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.35 23:42:54.02 +55:43:45.1
113.33184 -5.85984 galactic Cas Second-epoch detections are separated by 3.2" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:54.02 +55:43:45.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:42:54.02 +55:43:45.1: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:42:54.02 +55:43:45.1: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 42 54.02 +55 43 45.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.38 23:44:13.88 +53:16:51.4
112.87399 -8.27330 galactic Cas Second-epoch detections are separated by 4.8" and 5.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:44:13.88 +53:16:51.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:44:13.88 +53:16:51.4: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:44:13.88 +53:16:51.4: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 44 13.88 +53 16 51.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.19 23:23:13.88 +51:43:24.6
109.32014 -8.80184 galactic And Second-epoch detections are separated by 3.6" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:13.88 +51:43:24.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:13.88 +51:43:24.6: 15.52 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:13.88 +51:43:24.6: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 13.88 +51 43 24.6 14.2 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,2461274.8424,14.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 00:10:03.65 +55:10:39.2
116.99950 -7.21688 galactic Cas Second-epoch detections are separated by 5.6" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:03.65 +55:10:39.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:10:03.65 +55:10:39.2: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:10:03.65 +55:10:39.2: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 10 03.65 +55 10 39.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.47 23:47:10.97 +53:39:21.8
113.39949 -8.02224 galactic Cas Second-epoch detections are separated by 7.4" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:10.97 +53:39:21.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:47:10.97 +53:39:21.8: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:47:10.97 +53:39:21.8: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 47 10.97 +53 39 21.8 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.27 23:28:39.25 +53:12:34.2
110.60067 -7.66868 galactic Cas Second-epoch detections are separated by 1.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:39.25 +53:12:34.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:28:39.25 +53:12:34.2: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:28:39.25 +53:12:34.2: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 28 39.25 +53 12 34.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.43 00:01:43.90 +50:08:50.6
114.82936 -11.94074 galactic Cas Second-epoch detections are separated by 8.6" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:43.90 +50:08:50.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:01:43.90 +50:08:50.6: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:01:43.90 +50:08:50.6: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 01 43.90 +50 08 50.6 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.44 23:34:24.21 +52:49:52.3
111.31427 -8.29415 galactic Cas Second-epoch detections are separated by 8.1" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4009422 | 23:34:24.21 +52:49:52.3 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:24.21 +52:49:52.3: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:24.21 +52:49:52.3: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 24.21 +52 49 52.3 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4009422,2461274.8424,14.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
DocumentRef: VOTx4009422 20260822.3424 14.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 08 22.3424 2461274.8424 14.34 00:14:51.47 +52:19:01.5
117.26759 -10.15190 galactic Cas Second-epoch detections are separated by 7.7" and 6.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 395154141045536256 | 00:14:53.83 +52:18:29.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:14:51.47 +52:19:01.5: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:14:51.47 +52:19:01.5: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 14 51.47 +52 19 01.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 395154141045536256,2461274.8424,14.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
Gaia DR3 395154141045536256 20260822.3424 14.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 08 22.3424 2461274.8424 14.39 23:28:01.74 +55:38:43.8
111.29295 -5.33003 galactic Cas Second-epoch detections are separated by 8.5" and 5.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:28:01.74 +55:38:43.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:28:01.74 +55:38:43.8: 15.39 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:28:01.74 +55:38:43.8: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 28 01.74 +55 38 43.8 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.27 23:46:01.99 +54:36:45.9
113.47686 -7.05388 galactic Cas Second-epoch detections are separated by 6.9" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:46:01.99 +54:36:45.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:46:01.99 +54:36:45.9: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:46:01.99 +54:36:45.9: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 46 01.99 +54 36 45.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 00:13:12.44 +52:24:26.5
117.02790 -10.02559 galactic Cas Second-epoch detections are separated by 1.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:12.44 +52:24:26.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:12.44 +52:24:26.5: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:12.44 +52:24:26.5: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 12.44 +52 24 26.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.37 00:12:11.75 +51:44:24.0
116.76851 -10.66152 galactic Cas Second-epoch detections are separated by 3.8" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:11.75 +51:44:24.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:12:11.75 +51:44:24.0: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:11.75 +51:44:24.0: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 12 11.75 +51 44 24.0 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.32 23:30:06.75 +51:01:46.3
110.11957 -9.80791 galactic Cas Second-epoch detections are separated by 5.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:06.75 +51:01:46.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:06.75 +51:01:46.3: 15.52 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:06.75 +51:01:46.3: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 06.75 +51 01 46.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.41 00:00:05.85 +52:33:48.4
115.06196 -9.52203 galactic Cas Second-epoch detections are separated by 7.2" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:05.85 +52:33:48.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:05.85 +52:33:48.4: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:05.85 +52:33:48.4: 15.10 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 00 05.85 +52 33 48.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.26 00:04:07.44 +51:25:23.5
115.45612 -10.76048 galactic Cas Second-epoch detections are separated by 3.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:07.44 +51:25:23.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:04:07.44 +51:25:23.5: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:04:07.44 +51:25:23.5: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 04 07.44 +51 25 23.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.19 23:26:07.11 +55:38:15.0
111.03404 -5.25090 galactic Cas Second-epoch detections are separated by 3.5" and 5.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:26:07.11 +55:38:15.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:07.11 +55:38:15.0: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:07.11 +55:38:15.0: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 07.11 +55 38 15.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.19 23:43:41.94 +52:00:43.3
112.45941 -9.47700 galactic Cas Second-epoch detections are separated by 6.8" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:41.94 +52:00:43.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:41.94 +52:00:43.3: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:41.94 +52:00:43.3: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 41.94 +52 00 43.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.48 23:27:50.92 +50:26:22.3
109.58406 -10.25325 galactic And Second-epoch detections are separated by 3.4" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:50.92 +50:26:22.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:50.92 +50:26:22.3: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:50.92 +50:26:22.3: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 50.92 +50 26 22.3 14.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,2461274.8424,14.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.26 23:32:56.79 +53:38:43.0
111.35002 -7.45213 galactic Cas Second-epoch detections are separated by 7.0" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:32:56.79 +53:38:43.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:56.79 +53:38:43.0: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:56.79 +53:38:43.0: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 56.79 +53 38 43.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.21 23:37:40.52 +55:28:55.3
112.55040 -5.89591 galactic Cas Second-epoch detections are separated by 2.4" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:40.52 +55:28:55.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:40.52 +55:28:55.3: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:40.52 +55:28:55.3: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 40.52 +55 28 55.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.20 23:26:23.17 +55:21:03.6
110.97662 -5.53419 galactic Cas Second-epoch detections are separated by 6.8" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:26:23.17 +55:21:03.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:23.17 +55:21:03.6: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:23.17 +55:21:03.6: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 23.17 +55 21 03.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.21 00:07:27.59 +50:53:52.0
115.88433 -11.37120 galactic Cas Second-epoch detections are separated by 2.1" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:27.59 +50:53:52.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:27.59 +50:53:52.0: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:27.59 +50:53:52.0: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 07 27.59 +50 53 52.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.30 23:53:53.89 +53:23:45.0
114.31732 -8.51076 galactic Cas Second-epoch detections are separated by 8.6" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx791943 | 23:53:53.89 +53:23:45.0 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:53:53.89 +53:23:45.0: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:53:53.89 +53:23:45.0: 15.13 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 53 53.89 +53 23 45.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx791943,2461274.8424,14.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
DocumentRef: VOTx791943 20260822.3424 14.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 08 22.3424 2461274.8424 14.04 23:37:29.90 +56:31:52.9
112.82496 -4.88250 galactic Cas Second-epoch detections are separated by 4.2" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:29.90 +56:31:52.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:29.90 +56:31:52.9: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:29.90 +56:31:52.9: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 29.90 +56 31 52.9 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.09 23:27:51.87 +57:08:15.5
111.74757 -3.90817 galactic Cas Second-epoch detections are separated by 2.8" and 5.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:27:51.87 +57:08:15.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:51.87 +57:08:15.5: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:51.87 +57:08:15.5: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 51.87 +57 08 15.5 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 00:06:13.32 +51:56:53.9
115.87832 -10.30311 galactic Cas Second-epoch detections are separated by 8.1" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:06:13.32 +51:56:53.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:06:13.32 +51:56:53.9: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:06:13.32 +51:56:53.9: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 06 13.32 +51 56 53.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.05 23:27:42.19 +53:31:02.2
110.56407 -7.33173 galactic Cas Second-epoch detections are separated by 5.3" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:42.19 +53:31:02.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:42.19 +53:31:02.2: 15.52 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:42.19 +53:31:02.2: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 42.19 +53 31 02.2 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.04 23:17:13.79 +56:28:28.8
110.14997 -4.04107 galactic Cas Second-epoch detections are separated by 1.8" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:17:13.79 +56:28:28.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:13.79 +56:28:28.8: 15.36 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:13.79 +56:28:28.8: 14.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 13.79 +56 28 28.8 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.06 23:17:10.26 +55:35:40.3
109.82728 -4.86034 galactic Cas Second-epoch detections are separated by 1.6" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.2714+55.5905 | 23:17:10.26 +55:35:40.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:10.26 +55:35:40.3: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:10.26 +55:35:40.3: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 10.26 +55 35 40.3 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.2714+55.5905,2461274.8424,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.2714+55.5905 20260822.3424 14.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 08 22.3424 2461274.8424 14.08 23:39:36.71 +51:31:08.8
111.70664 -9.78037 galactic Cas Second-epoch detections are separated by 4.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:39:36.71 +51:31:08.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:39:36.71 +51:31:08.8: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:39:36.71 +51:31:08.8: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 39 36.71 +51 31 08.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.18 23:25:28.75 +54:50:22.6
110.68576 -5.97533 galactic Cas Second-epoch detections are separated by 7.9" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:28.75 +54:50:22.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:28.75 +54:50:22.6: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:28.75 +54:50:22.6: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 28.75 +54 50 22.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.16 23:43:34.82 +55:18:55.4
113.31602 -6.28440 galactic Cas Second-epoch detections are separated by 5.0" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:34.82 +55:18:55.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:34.82 +55:18:55.4: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:34.82 +55:18:55.4: 15.14 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 34.82 +55 18 55.4 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.26 23:34:09.42 +55:46:32.9
112.15818 -5.47100 galactic Cas Second-epoch detections are separated by 5.9" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:09.42 +55:46:32.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:09.42 +55:46:32.9: 15.53 +/- 0.35 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:09.42 +55:46:32.9: 15.07 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.53 +/- 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 08 22.3424* 23 34 09.42 +55 46 32.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.26 23:34:58.59 +55:47:45.8
112.27477 -5.48555 galactic Cas Second-epoch detections are separated by 3.0" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:58.59 +55:47:45.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:58.59 +55:47:45.8: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:58.59 +55:47:45.8: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 58.59 +55 47 45.8 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.13 23:13:50.99 +55:57:40.5
109.52426 -4.34916 galactic Cas Second-epoch detections are separated by 3.6" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:13:50.99 +55:57:40.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:13:50.99 +55:57:40.5: 15.41 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:13:50.99 +55:57:40.5: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 13 50.99 +55 57 40.5 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.09 23:22:19.17 +54:46:36.1
110.23319 -5.88282 galactic Cas Second-epoch detections are separated by 7.1" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:19.17 +54:46:36.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:19.17 +54:46:36.1: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:19.17 +54:46:36.1: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 19.17 +54 46 36.1 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.11 00:03:16.36 +54:09:44.4
115.84601 -8.04543 galactic Cas Second-epoch detections are separated by 5.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:16.36 +54:09:44.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:03:16.36 +54:09:44.4: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:03:16.36 +54:09:44.4: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 03 16.36 +54 09 44.4 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.17 23:10:42.41 +56:27:19.9
109.30334 -3.72730 galactic Cas Second-epoch detections are separated by 6.0" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:10:42.41 +56:27:19.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:10:42.41 +56:27:19.9: 15.19 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:10:42.41 +56:27:19.9: 14.86 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.19 +/- 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 08 22.3424* 23 10 42.41 +56 27 19.9 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.07 23:41:20.97 +51:48:13.8
112.04891 -9.58076 galactic Cas Second-epoch detections are separated by 5.1" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:20.97 +51:48:13.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:20.97 +51:48:13.8: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:20.97 +51:48:13.8: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 20.97 +51 48 13.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.15 23:11:21.01 +56:24:12.1
109.36606 -3.80924 galactic Cas Second-epoch detections are separated by 4.2" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:11:21.01 +56:24:12.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:11:21.01 +56:24:12.1: 15.31 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:11:21.01 +56:24:12.1: 14.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 11 21.01 +56 24 12.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.12 23:47:58.44 +52:38:59.4
113.26384 -9.02651 galactic Cas Second-epoch detections are separated by 8.8" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:58.44 +52:38:59.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:47:58.44 +52:38:59.4: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:47:58.44 +52:38:59.4: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 47 58.44 +52 38 59.4 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:17:18.61 +56:04:22.4
110.01681 -4.42043 galactic Cas Second-epoch detections are separated by 2.0" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.3612+56.0624 | 23:17:23.59 +56:04:05.5 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:18.61 +56:04:22.4: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:18.61 +56:04:22.4: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 18.61 +56 04 22.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.3612+56.0624,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.3612+56.0624 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.09 23:42:19.10 +55:47:52.7
113.27079 -5.77185 galactic Cas Second-epoch detections are separated by 5.3" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:19.10 +55:47:52.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:42:19.10 +55:47:52.7: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:42:19.10 +55:47:52.7: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 42 19.10 +55 47 52.7 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.06 23:33:47.93 +57:28:40.7
112.61666 -3.83057 galactic Cas Second-epoch detections are separated by 3.9" and 5.5 pix
The object was found in VSX14" Gaia DR3 1998815901972749568
Type: ROT
# Max. Min./Amp. JD0 Period
16.190 G 16.240 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:33:47.93 +57:28:40.7: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:33:47.93 +57:28:40.7: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 33 47.93 +57 28 40.7 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998815901972749568,2461274.8424,14.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
Gaia DR3 1998815901972749568 20260822.3424 14.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 08 22.3424 2461274.8424 14.16 23:23:47.98 +53:18:18.0
109.93984 -7.34164 galactic Cas Second-epoch detections are separated by 5.1" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:47.98 +53:18:18.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:47.98 +53:18:18.0: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:47.98 +53:18:18.0: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 47.98 +53 18 18.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.09 23:44:26.33 +52:09:01.8
112.60731 -9.37305 galactic Cas Second-epoch detections are separated by 4.3" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:44:26.33 +52:09:01.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:44:26.33 +52:09:01.8: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:44:26.33 +52:09:01.8: 15.11 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 44 26.33 +52 09 01.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.01 00:20:22.17 +51:49:02.5
118.05366 -10.75987 galactic Cas Second-epoch detections are separated by 3.5" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J005.1048+51.8198 | 00:20:22.17 +51:49:02.5 (user input) | CBH (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:20:22.17 +51:49:02.5: 15.06 +/- 0.22 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:20:22.17 +51:49:02.5: 14.93 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.06 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 20 22.17 +51 49 02.5 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J005.1048+51.8198,2461274.8424,14.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.1048+51.8198 20260822.3424 14.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.09 23:26:04.73 +54:30:25.1
110.65882 -6.31804 galactic Cas Second-epoch detections are separated by 4.4" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:26:04.73 +54:30:25.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:04.73 +54:30:25.1: 15.37 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:04.73 +54:30:25.1: 14.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 04.73 +54 30 25.1 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.01 00:28:12.68 +54:30:52.4
119.53016 -8.20371 galactic Cas Second-epoch detections are separated by 8.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx2732914 | 00:28:12.68 +54:30:52.4 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:28:12.68 +54:30:52.4: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:28:12.68 +54:30:52.4: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 28 12.68 +54 30 52.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2732914,2461274.8424,14.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2732914 20260822.3424 14.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.08 23:23:13.03 +56:57:57.2
111.09273 -3.86415 galactic Cas Second-epoch detections are separated by 6.6" and 5.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:13.03 +56:57:57.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:13.03 +56:57:57.2: 15.10 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:13.03 +56:57:57.2: 14.93 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.10 +/- 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 08 22.3424* 23 23 13.03 +56 57 57.2 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.17 00:05:25.40 +52:54:34.1
115.93095 -9.33565 galactic Cas Second-epoch detections are separated by 3.0" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:25.40 +52:54:34.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:25.40 +52:54:34.1: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:05:25.40 +52:54:34.1: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 05 25.40 +52 54 34.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.93 23:33:51.73 +56:19:28.0
112.28189 -4.93479 galactic Cas Second-epoch detections are separated by 7.7" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:51.73 +56:19:28.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:33:51.73 +56:19:28.0: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:33:51.73 +56:19:28.0: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 33 51.73 +56 19 28.0 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:17:49.59 +51:39:57.4
108.50555 -8.56449 galactic And Second-epoch detections are separated by 4.7" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.4612+51.6677 | 23:17:49.59 +51:39:57.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:49.59 +51:39:57.4: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:49.59 +51:39:57.4: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 49.59 +51 39 57.4 14.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
ATO J349.4612+51.6677,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.4612+51.6677 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 23:14:00.65 +56:16:06.4
109.65864 -4.07183 galactic Cas Second-epoch detections are separated by 8.4" and 5.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:14:00.65 +56:16:06.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:00.65 +56:16:06.4: 15.43 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:00.65 +56:16:06.4: 14.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 00.65 +56 16 06.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.00 23:22:22.22 +51:21:59.3
109.06987 -9.09213 galactic And Second-epoch detections are separated by 3.0" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3655659 | 23:22:22.22 +51:21:59.3 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:22.22 +51:21:59.3: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:22.22 +51:21:59.3: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 22.22 +51 21 59.3 14.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
DocumentRef: VOTx3655659,2461274.8424,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3655659 20260822.3424 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 00:30:57.41 +55:56:16.0
120.04628 -6.81918 galactic Cas Second-epoch detections are separated by 7.0" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3545927 | 00:30:57.41 +55:56:16.0 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:30:57.41 +55:56:16.0: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:30:57.41 +55:56:16.0: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 30 57.41 +55 56 16.0 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3545927,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3545927 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.94 23:54:47.01 +49:59:46.1
113.68289 -11.85545 galactic Cas Second-epoch detections are separated by 3.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:54:47.01 +49:59:46.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:54:47.01 +49:59:46.1: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:54:47.01 +49:59:46.1: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 54 47.01 +49 59 46.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.00 23:15:31.82 +55:29:12.1
109.57102 -4.87738 galactic Cas Second-epoch detections are separated by 6.7" and 5.7 pix
The object was found in VSX 8" Gaia DR3 1997079601312812032
Type: S
# Max. Min./Amp. JD0 Period
15.090 G 15.880 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:15:31.82 +55:29:12.1: 15.42 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:15:31.82 +55:29:12.1: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 15 31.82 +55 29 12.1 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997079601312812032,2461274.8424,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997079601312812032 20260822.3424 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.80 23:17:33.22 +56:09:22.6
110.07839 -4.35458 galactic Cas Second-epoch detections are separated by 2.7" and 5.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 | DocumentRef: VOTx3664128 | 23:17:33.22 +56:09:22.6 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:33.22 +56:09:22.6: 15.37 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:33.22 +56:09:22.6: 14.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 33.22 +56 09 22.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3664128,2461274.8424,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3664128 20260822.3424 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.91 23:29:09.84 +53:28:15.7
110.75696 -7.44466 galactic Cas Second-epoch detections are separated by 8.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:09.84 +53:28:15.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:29:09.84 +53:28:15.7: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:29:09.84 +53:28:15.7: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 29 09.84 +53 28 15.7 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.88 23:22:50.81 +51:55:37.3
109.33334 -8.59022 galactic And Second-epoch detections are separated by 5.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:50.81 +51:55:37.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:50.81 +51:55:37.3: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:50.81 +51:55:37.3: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 50.81 +51 55 37.3 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 23:14:39.08 +54:01:55.6
108.91909 -6.18537 galactic Cas Second-epoch detections are separated by 3.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:14:39.08 +54:01:55.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:39.08 +54:01:55.6: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:39.08 +54:01:55.6: 14.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 39.08 +54 01 55.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.02 23:22:41.52 +50:08:52.2
108.69618 -10.25488 galactic And Second-epoch detections are separated by 3.9" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:41.52 +50:08:52.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:41.52 +50:08:52.2: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:41.52 +50:08:52.2: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 41.52 +50 08 52.2 14.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,2461274.8424,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.17 00:10:41.97 +53:58:59.1
116.89870 -8.41076 galactic Cas Second-epoch detections are separated by 2.9" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:41.97 +53:58:59.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:10:41.97 +53:58:59.1: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:10:41.97 +53:58:59.1: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 10 41.97 +53 58 59.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.02 23:40:56.31 +56:21:53.4
113.23719 -5.17413 galactic Cas Second-epoch detections are separated by 4.5" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1997804797952790144 | 23:40:55.81 +56:21:17.7 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A1V (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:40:56.31 +56:21:53.4: 15.04 +/- 0.20 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:40:56.31 +56:21:53.4: 14.94 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.01 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 40 56.31 +56 21 53.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997804797952790144,2461274.8424,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997804797952790144 20260822.3424 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.12 23:52:43.95 +51:16:51.2
113.65586 -10.53046 galactic Cas Second-epoch detections are separated by 5.4" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:43.95 +51:16:51.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:43.95 +51:16:51.2: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:43.95 +51:16:51.2: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 43.95 +51 16 51.2 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 23:14:43.69 +55:59:17.7
109.64883 -4.36916 galactic Cas Second-epoch detections are separated by 2.9" and 5.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:43.69 +55:59:17.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:43.69 +55:59:17.7: 15.09 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:43.69 +55:59:17.7: 14.76 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.09 +/- 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 08 22.3424* 23 14 43.69 +55 59 17.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 13.95 23:27:03.30 +51:35:13.2
109.84083 -9.12710 galactic Cas Second-epoch detections are separated by 3.8" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:03.30 +51:35:13.2 (user input) | T | P | (position from user input) J-Ks=0.497+/-0.178 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:03.30 +51:35:13.2: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:03.30 +51:35:13.2: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 03.30 +51 35 13.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.98 23:17:24.25 +53:56:33.4
109.26597 -6.41531 galactic Cas Second-epoch detections are separated by 5.1" and 5.1 pix
The object was found in VSX16" Gaia DR3 1995953426527758208
Type: ROT
# Max. Min./Amp. JD0 Period
14.320 G 14.340 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:24.25 +53:56:33.4: 15.46 +/- 0.35 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:24.25 +53:56:33.4: 14.90 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.46 +/- 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 08 22.3424* 23 17 24.25 +53 56 33.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1995953426527758208,2461274.8424,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1995953426527758208 20260822.3424 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:21:31.46 +51:34:43.2
109.01826 -8.84763 galactic And Second-epoch detections are separated by 4.2" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:31.46 +51:34:43.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:31.46 +51:34:43.2: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:31.46 +51:34:43.2: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 31.46 +51 34 43.2 14.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,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.94 00:00:45.69 +52:08:01.9
115.07590 -9.96321 galactic Cas Second-epoch detections are separated by 5.2" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:45.69 +52:08:01.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:45.69 +52:08:01.9: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:45.69 +52:08:01.9: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 00 45.69 +52 08 01.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.88 23:27:04.54 +55:04:53.9
110.98269 -5.82088 galactic Cas Second-epoch detections are separated by 6.9" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:04.54 +55:04:53.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:04.54 +55:04:53.9: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:04.54 +55:04:53.9: 14.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 04.54 +55 04 53.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.93 23:36:50.41 +55:44:36.5
112.51154 -5.61172 galactic Cas Second-epoch detections are separated by 8.1" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3985938 | 23:36:50.41 +55:44:36.5 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:36:50.41 +55:44:36.5: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:36:50.41 +55:44:36.5: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 36 50.41 +55 44 36.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3985938,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3985938 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.92 23:14:10.81 +56:23:41.4
109.72710 -3.96292 galactic Cas Second-epoch detections are separated by 1.7" and 5.4 pix
The object was found in VSX21" ZTF J231413.20+562335.6
Type: BY
# Max. Min./Amp. JD0 Period
17.547 r Y 0.056 r 2458258.95650 1.042040500000
ATTENTION: measured mag 13.92 is 3.6 mag brighter than the VSX record maximum brightness 17.49 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:10.81 +56:23:41.4: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:10.81 +56:23:41.4: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 10.81 +56 23 41.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J231413.20+562335.6,2461274.8424,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J231413.20+562335.6 20260822.3424 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.98 23:48:03.18 +49:59:47.6
112.60932 -11.60051 galactic Cas Second-epoch detections are separated by 6.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:03.18 +49:59:47.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:48:03.18 +49:59:47.6: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:48:03.18 +49:59:47.6: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 48 03.18 +49 59 47.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.94 23:52:37.41 +53:51:42.7
114.23765 -8.01410 galactic Cas Second-epoch detections are separated by 5.2" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:37.41 +53:51:42.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:37.41 +53:51:42.7: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:37.41 +53:51:42.7: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 37.41 +53 51 42.7 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.89 23:17:19.86 +55:48:34.8
109.92543 -4.66740 galactic Cas Second-epoch detections are separated by 1.8" and 5.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:17:19.86 +55:48:34.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:19.86 +55:48:34.8: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:19.86 +55:48:34.8: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 19.86 +55 48 34.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.79 23:21:37.01 +52:40:18.1
109.41148 -7.82609 galactic And Second-epoch detections are separated by 1.7" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx237855 | 23:21:37.01 +52:40:18.1 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:37.01 +52:40:18.1: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:37.01 +52:40:18.1: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 37.01 +52 40 18.1 13.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
DocumentRef: VOTx237855,2461274.8424,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx237855 20260822.3424 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.90 23:24:53.44 +51:36:44.3
109.52777 -8.99284 galactic And Second-epoch detections are separated by 5.1" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:53.44 +51:36:44.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:53.44 +51:36:44.3: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:53.44 +51:36:44.3: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 53.44 +51 36 44.3 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.89 23:41:49.02 +54:48:54.3
112.93775 -6.70005 galactic Cas Second-epoch detections are separated by 5.2" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:49.02 +54:48:54.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:49.02 +54:48:54.3: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:49.02 +54:48:54.3: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 49.02 +54 48 54.3 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.93 23:38:15.07 +53:10:00.6
111.97230 -8.14046 galactic Cas Second-epoch detections are separated by 7.6" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx530203 | 23:38:15.07 +53:10:00.6 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:38:15.07 +53:10:00.6: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:38:15.07 +53:10:00.6: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 38 15.07 +53 10 00.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx530203,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx530203 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.91 23:15:34.86 +53:05:16.0
108.70087 -7.11480 galactic And Second-epoch detections are separated by 3.3" and 4.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 J348.9078+53.0883 | 23:15:39.12 +53:05:10.9 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:15:34.86 +53:05:16.0: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:15:34.86 +53:05:16.0: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 15 34.86 +53 05 16.0 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J348.9078+53.0883,2461274.8424,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J348.9078+53.0883 20260822.3424 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.06 23:16:49.50 +56:44:36.6
110.19407 -3.77007 galactic Cas Second-epoch detections are separated by 5.4" and 5.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:16:49.50 +56:44:36.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:16:49.50 +56:44:36.6: 15.41 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:16:49.50 +56:44:36.6: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 16 49.50 +56 44 36.6 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 13.85 23:55:32.65 +51:24:49.0
114.12129 -10.49944 galactic Cas Second-epoch detections are separated by 6.5" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J358.8978+51.4028 | 23:55:32.65 +51:24:49.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:55:32.65 +51:24:49.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:55:32.65 +51:24:49.0: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 55 32.65 +51 24 49.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J358.8978+51.4028,2461274.8424,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.8978+51.4028 20260822.3424 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.98 00:08:06.08 +51:46:32.5
116.13835 -10.52350 galactic Cas Second-epoch detections are separated by 5.2" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:08:06.08 +51:46:32.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:08:06.08 +51:46:32.5: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:08:06.08 +51:46:32.5: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 08 06.08 +51 46 32.5 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.78 23:20:42.93 +52:15:32.8
109.13765 -8.16600 galactic And Second-epoch detections are separated by 6.8" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:20:42.93 +52:15:32.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:20:42.93 +52:15:32.8: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:20:42.93 +52:15:32.8: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 20 42.93 +52 15 32.8 13.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,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.88 23:23:13.51 +55:06:38.9
110.46955 -5.61220 galactic Cas Second-epoch detections are separated by 7.9" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:13.51 +55:06:38.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:13.51 +55:06:38.9: 15.38 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:13.51 +55:06:38.9: 14.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 13.51 +55 06 38.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.00 23:18:01.86 +52:26:53.8
108.81723 -7.84486 galactic And Second-epoch detections are separated by 8.6" and 5.6 pix
The object was found in VSX21" Gaia DR3 1992584419819719296
Type: S
# Max. Min./Amp. JD0 Period
17.460 G 18.650 G
ATTENTION: measured mag 14.00 is 3.5 mag brighter than the VSX record maximum brightness 17.46 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:18:01.86 +52:26:53.8: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:18:01.86 +52:26:53.8: 14.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 18 01.86 +52 26 53.8 14.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
Gaia DR3 1992584419819719296,2461274.8424,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1992584419819719296 20260822.3424 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.86 00:13:02.05 +53:50:13.4
117.21933 -8.60819 galactic Cas Second-epoch detections are separated by 5.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:02.05 +53:50:13.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:02.05 +53:50:13.4: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:02.05 +53:50:13.4: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 02.05 +53 50 13.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.89 23:26:51.69 +50:21:04.8
109.40374 -10.28563 galactic And Second-epoch detections are separated by 2.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.7300+50.3490 | 23:26:51.69 +50:21:04.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:51.69 +50:21:04.8: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:51.69 +50:21:04.8: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 51.69 +50 21 04.8 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J351.7300+50.3490,2461274.8424,13.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 J351.7300+50.3490 20260822.3424 13.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 08 22.3424 2461274.8424 13.99 23:30:42.17 +51:38:08.2
110.40043 -9.26098 galactic Cas Second-epoch detections are separated by 7.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:42.17 +51:38:08.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:42.17 +51:38:08.2: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:42.17 +51:38:08.2: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 42.17 +51 38 08.2 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 23:33:46.95 +50:32:48.2
110.52955 -10.44559 galactic And Second-epoch detections are separated by 3.3" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx726520 | 23:33:46.95 +50:32:48.2 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:33:46.95 +50:32:48.2: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:33:46.95 +50:32:48.2: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 33 46.95 +50 32 48.2 14.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
DocumentRef: VOTx726520,2461274.8424,14.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
DocumentRef: VOTx726520 20260822.3424 14.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 08 22.3424 2461274.8424 13.73 23:16:54.50 +55:48:01.6
109.86648 -4.65480 galactic Cas Second-epoch detections are separated by 0.8" and 5.2 pix
The object was found in VSX25" Gaia DR3 1997099014565172736
Type: ROT
# Max. Min./Amp. JD0 Period
15.060 G 15.080 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:16:54.50 +55:48:01.6: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:16:54.50 +55:48:01.6: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 16 54.50 +55 48 01.6 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997099014565172736,2461274.8424,13.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 1997099014565172736 20260822.3424 13.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 08 22.3424 2461274.8424 13.80 23:19:09.98 +54:34:48.6
109.73497 -5.91009 galactic Cas Second-epoch detections are separated by 8.7" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1996050866444946176 | 23:19:12.17 +54:34:24.6 (Gaia DR3) | E (local) | 0.250070000000 (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:09.98 +54:34:48.6: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:19:09.98 +54:34:48.6: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 19 09.98 +54 34 48.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1996050866444946176,2461274.8424,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1996050866444946176 20260822.3424 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.04 00:07:25.85 +52:06:06.5
116.09166 -10.18451 galactic Cas Second-epoch detections are separated by 7.4" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 395849547791048320 | 00:07:21.34 +52:06:26.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE J-Ks=0.710+/- (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:25.85 +52:06:06.5: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:25.85 +52:06:06.5: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 07 25.85 +52 06 06.5 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 395849547791048320,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 395849547791048320 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.83 23:28:15.83 +51:28:50.6
109.98641 -9.28830 galactic Cas Second-epoch detections are separated by 3.5" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:15.83 +51:28:50.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:28:15.83 +51:28:50.6: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:28:15.83 +51:28:50.6: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 28 15.83 +51 28 50.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.79 23:57:17.16 +54:23:56.1
115.02911 -7.63981 galactic Cas Second-epoch detections are separated by 8.7" and 5.9 pix
The object was found in VSX23" Gaia DR3 1993606244081527168
Type: E
# Max. Min./Amp. JD0 Period
16.910 G 17.180 G 1.462400000000 F
ATTENTION: measured mag 13.79 is 3.1 mag brighter than the VSX record maximum brightness 16.91 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:57:17.16 +54:23:56.1: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:57:17.16 +54:23:56.1: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 57 17.16 +54 23 56.1 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993606244081527168,2461274.8424,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993606244081527168 20260822.3424 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 23:39:31.96 +55:38:14.2
112.84749 -5.82026 galactic Cas Second-epoch detections are separated by 8.5" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1115085 | 23:39:31.96 +55:38:14.2 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:39:31.96 +55:38:14.2: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:39:31.96 +55:38:14.2: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 39 31.96 +55 38 14.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1115085,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1115085 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.86 23:21:30.79 +50:33:07.4
108.65781 -9.81066 galactic And Second-epoch detections are separated by 0.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:30.79 +50:33:07.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:30.79 +50:33:07.4: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:30.79 +50:33:07.4: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 30.79 +50 33 07.4 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 23:57:57.45 +50:00:30.2
114.19448 -11.95388 galactic Cas Second-epoch detections are separated by 5.0" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:57.45 +50:00:30.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:57:57.45 +50:00:30.2: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:57:57.45 +50:00:30.2: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 57 57.45 +50 00 30.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 00:26:01.52 +49:49:08.2
118.73247 -12.84548 galactic Cas Second-epoch detections are separated by 7.4" and 7.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:26:01.52 +49:49:08.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:26:01.52 +49:49:08.2: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:26:01.52 +49:49:08.2: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 26 01.52 +49 49 08.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.94 23:24:06.39 +51:31:42.6
109.38316 -9.03119 galactic And Second-epoch detections are separated by 0.7" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:06.39 +51:31:42.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:06.39 +51:31:42.6: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:06.39 +51:31:42.6: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 06.39 +51 31 42.6 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.93 23:28:10.10 +53:34:41.6
110.64972 -7.29608 galactic Cas Second-epoch detections are separated by 7.3" and 5.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:28:10.10 +53:34:41.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:28:10.10 +53:34:41.6: 15.32 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:28:10.10 +53:34:41.6: 15.00 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.32 +/- 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 08 22.3424* 23 28 10.10 +53 34 41.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.71 00:09:04.02 +51:44:06.9
116.28127 -10.58852 galactic Cas Second-epoch detections are separated by 4.2" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:04.02 +51:44:06.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:09:04.02 +51:44:06.9: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:09:04.02 +51:44:06.9: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 09 04.02 +51 44 06.9 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.77 23:41:48.33 +51:06:34.3
111.92719 -10.26831 galactic Cas Second-epoch detections are separated by 8.8" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:48.33 +51:06:34.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:48.33 +51:06:34.3: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:48.33 +51:06:34.3: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 48.33 +51 06 34.3 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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
target 20260822.3424 13.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 08 22.3424 2461274.8424 13.78 00:10:11.06 +50:58:29.6
116.32915 -11.36722 galactic Cas Second-epoch detections are separated by 3.4" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:11.06 +50:58:29.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:10:11.06 +50:58:29.6: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:10:11.06 +50:58:29.6: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 10 11.06 +50 58 29.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.84 23:37:51.56 +55:18:45.1
112.52741 -6.06588 galactic Cas Second-epoch detections are separated by 3.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:51.56 +55:18:45.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:51.56 +55:18:45.1: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:51.56 +55:18:45.1: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 51.56 +55 18 45.1 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.83 23:41:14.11 +49:49:14.1
111.48096 -11.48387 galactic Cas Second-epoch detections are separated by 8.9" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:14.11 +49:49:14.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:14.11 +49:49:14.1: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:14.11 +49:49:14.1: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 14.11 +49 49 14.1 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.88 23:24:41.18 +50:40:04.3
109.17829 -9.87270 galactic And Second-epoch detections are separated by 8.3" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:41.18 +50:40:04.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:41.18 +50:40:04.3: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:41.18 +50:40:04.3: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 41.18 +50 40 04.3 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.81 00:16:43.69 +55:04:48.4
117.93514 -7.45453 galactic Cas Second-epoch detections are separated by 5.9" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1638477 | 00:16:43.69 +55:04:48.4 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:16:43.69 +55:04:48.4: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:16:43.69 +55:04:48.4: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 16 43.69 +55 04 48.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1638477,2461274.8424,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1638477 20260822.3424 13.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 23:48:14.88 +49:50:27.4
112.60100 -11.75904 galactic Cas Second-epoch detections are separated by 3.5" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:14.88 +49:50:27.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:48:14.88 +49:50:27.4: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:48:14.88 +49:50:27.4: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 48 14.88 +49 50 27.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.78 00:16:58.68 +49:56:54.5
117.26497 -12.54373 galactic Cas Second-epoch detections are separated by 5.2" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:58.68 +49:56:54.5 (user input) | T | P | (position from user input) SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:16:58.68 +49:56:54.5: 15.24 +/- 0.24 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:16:58.68 +49:56:54.5: 15.01 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.24 +/- 0.24
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 16 58.68 +49 56 54.5 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.73 23:30:42.23 +58:00:32.4
112.38291 -3.19964 galactic Cas Second-epoch detections are separated by 4.4" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1885462 | 23:30:42.23 +58:00:32.4 (user input) | (GCVS) | (GCVS) | (position from user input) J-Ks=0.458+/-0.045 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:42.23 +58:00:32.4: 15.03 +/- 0.25 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:42.23 +58:00:32.4: 14.87 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.03 +/- 0.25
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 42.23 +58 00 32.4 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1885462,2461274.8424,13.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
DocumentRef: VOTx1885462 20260822.3424 13.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 08 22.3424 2461274.8424 13.64 23:17:20.32 +56:42:33.0
110.24775 -3.82729 galactic Cas Second-epoch detections are separated by 6.3" and 5.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:17:20.32 +56:42:33.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:20.32 +56:42:33.0: 15.43 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:20.32 +56:42:33.0: 14.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 20.32 +56 42 33.0 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.62 23:21:56.72 +51:25:13.0
109.02544 -9.01889 galactic And Second-epoch detections are separated by 2.9" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:56.72 +51:25:13.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:56.72 +51:25:13.0: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:56.72 +51:25:13.0: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 56.72 +51 25 13.0 13.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,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.62 23:21:22.07 +54:59:40.4
110.17851 -5.63136 galactic Cas Second-epoch detections are separated by 8.1" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:22.07 +54:59:40.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:22.07 +54:59:40.4: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:22.07 +54:59:40.4: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 22.07 +54 59 40.4 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.62 23:14:32.81 +57:06:02.1
110.03317 -3.32472 galactic Cas Second-epoch detections are separated by 7.1" and 5.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 | DocumentRef: VOTx2383279 | 23:14:32.81 +57:06:02.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:32.81 +57:06:02.1: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:32.81 +57:06:02.1: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 32.81 +57 06 02.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2383279,2461274.8424,13.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
DocumentRef: VOTx2383279 20260822.3424 13.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 08 22.3424 2461274.8424 13.60 00:05:32.26 +50:54:27.7
115.58191 -11.30784 galactic Cas Second-epoch detections are separated by 5.0" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx2303902 | 00:05:32.26 +50:54:27.7 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:32.26 +50:54:27.7: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:05:32.26 +50:54:27.7: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 05 32.26 +50 54 27.7 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2303902,2461274.8424,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2303902 20260822.3424 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.54 23:41:27.83 +55:38:04.4
113.11031 -5.89715 galactic Cas Second-epoch detections are separated by 3.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:27.83 +55:38:04.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:27.83 +55:38:04.4: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:27.83 +55:38:04.4: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 27.83 +55 38 04.4 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.52 00:29:14.27 +55:53:35.5
119.80082 -6.84353 galactic Cas Second-epoch detections are separated by 5.3" and 6.1 pix
The object was found in VSX 4" Gaia DR3 421288944019483264
Type: ROT
# Max. Min./Amp. JD0 Period
15.710 G 15.750 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:29:14.27 +55:53:35.5: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:29:14.27 +55:53:35.5: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 29 14.27 +55 53 35.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 421288944019483264,2461274.8424,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 421288944019483264 20260822.3424 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.40 23:25:30.20 +56:41:11.7
111.29593 -4.23120 galactic Cas Second-epoch detections are separated by 6.2" and 5.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 | DocumentRef: VOTx2497165 | 23:25:30.20 +56:41:11.7 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:30.20 +56:41:11.7: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:30.20 +56:41:11.7: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 30.20 +56 41 11.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2497165,2461274.8424,13.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2497165 20260822.3424 13.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.38 23:27:35.60 +56:31:40.6
111.51746 -4.47425 galactic Cas Second-epoch detections are separated by 1.4" and 5.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:27:35.60 +56:31:40.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:35.60 +56:31:40.6: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:35.60 +56:31:40.6: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 35.60 +56 31 40.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.39 00:05:57.46 +52:01:29.6
115.85146 -10.22051 galactic Cas Second-epoch detections are separated by 3.8" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx2909785 | 00:05:57.46 +52:01:29.6 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:57.46 +52:01:29.6: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:05:57.46 +52:01:29.6: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 05 57.46 +52 01 29.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2909785,2461274.8424,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2909785 20260822.3424 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.37 00:13:15.18 +52:31:09.5
117.05193 -9.91595 galactic Cas Second-epoch detections are separated by 4.5" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:15.18 +52:31:09.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:15.18 +52:31:09.5: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:15.18 +52:31:09.5: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 15.18 +52 31 09.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.29 23:25:51.42 +52:56:18.2
110.11111 -7.78980 galactic Cas Second-epoch detections are separated by 2.4" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:51.42 +52:56:18.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:51.42 +52:56:18.2: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:51.42 +52:56:18.2: 14.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 51.42 +52 56 18.2 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.39 00:25:38.30 +51:57:33.1
118.89207 -10.71007 galactic Cas Second-epoch detections are separated by 2.6" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx2852684 | 00:25:38.30 +51:57:33.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:25:38.30 +51:57:33.1: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:25:38.30 +51:57:33.1: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 25 38.30 +51 57 33.1 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2852684,2461274.8424,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2852684 20260822.3424 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.39 23:56:49.66 +50:03:02.6
114.02247 -11.87396 galactic Cas Second-epoch detections are separated by 4.4" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx2958150 | 23:56:49.66 +50:03:02.6 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:56:49.66 +50:03:02.6: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:56:49.66 +50:03:02.6: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 56 49.66 +50 03 02.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2958150,2461274.8424,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2958150 20260822.3424 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.20 23:22:06.89 +49:53:01.4
108.51562 -10.47122 galactic And Second-epoch detections are separated by 1.2" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.5455+49.8904 | 23:22:06.89 +49:53:01.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:06.89 +49:53:01.4: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:06.89 +49:53:01.4: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 06.89 +49 53 01.4 13.2 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.5455+49.8904,2461274.8424,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J350.5455+49.8904 20260822.3424 13.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.05 23:39:45.94 +51:01:25.7
111.59011 -10.26280 galactic Cas Second-epoch detections are separated by 4.7" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3023562 | 23:39:45.94 +51:01:25.7 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:39:45.94 +51:01:25.7: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:39:45.94 +51:01:25.7: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 39 45.94 +51 01 25.7 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3023562,2461274.8424,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3023562 20260822.3424 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.04 23:53:42.64 +50:58:18.9
113.73638 -10.86625 galactic Cas Second-epoch detections are separated by 4.8" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:53:42.64 +50:58:18.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:53:42.64 +50:58:18.9: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:53:42.64 +50:58:18.9: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 53 42.64 +50 58 18.9 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 12.85 23:12:00.81 +56:27:21.2
109.47101 -3.79506 galactic Cas Second-epoch detections are separated by 4.9" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3188661 | 23:12:00.81 +56:27:21.2 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:12:00.81 +56:27:21.2: 15.21 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:12:00.81 +56:27:21.2: 14.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 12 00.81 +56 27 21.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
DocumentRef: VOTx3188661,2461274.8424,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
DocumentRef: VOTx3188661 20260822.3424 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 08 22.3424 2461274.8424 12.77 00:07:16.61 +51:00:10.5
115.87399 -11.26265 galactic Cas Second-epoch detections are separated by 1.6" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:16.61 +51:00:10.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:16.61 +51:00:10.5: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:16.61 +51:00:10.5: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 07 16.61 +51 00 10.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,2461274.8424,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
target 20260822.3424 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 08 22.3424 2461274.8424 12.85 23:32:12.89 +57:11:42.5
112.32739 -4.03645 galactic Cas Second-epoch detections are separated by 7.9" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3511404 | 23:32:12.89 +57:11:42.5 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:12.89 +57:11:42.5: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:12.89 +57:11:42.5: 14.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 12.89 +57 11 42.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
DocumentRef: VOTx3511404,2461274.8424,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
DocumentRef: VOTx3511404 20260822.3424 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 08 22.3424 2461274.8424 12.73 23:21:09.71 +55:54:03.5
110.46280 -4.76979 galactic Cas Second-epoch detections are separated by 4.8" and 5.1 pix
The object was found in VSX18" ZTF J232111.75+555357.2
Type: EW
# Max. Min./Amp. JD0 Period
17.487 r Y 0.217 r 2458273.92520 0.421857800000
ATTENTION: measured mag 12.73 is 4.5 mag brighter than the VSX record maximum brightness 17.27 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:09.71 +55:54:03.5: 15.38 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:09.71 +55:54:03.5: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 09.71 +55 54 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
ZTF J232111.75+555357.2,2461274.8424,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
ZTF J232111.75+555357.2 20260822.3424 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 08 22.3424 2461274.8424 12.62 23:11:34.56 +56:00:12.8
109.24414 -4.19139 galactic Cas Second-epoch detections are separated by 4.8" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3504227 | 23:11:34.56 +56:00:12.8 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:11:34.56 +56:00:12.8: 14.17 +/- 0.13 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:11:34.56 +56:00:12.8: 14.64 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.17 +/- 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 08 22.3424* 23 11 34.56 +56 00 12.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
DocumentRef: VOTx3504227,2461274.8424,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
DocumentRef: VOTx3504227 20260822.3424 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 08 22.3424 2461274.8424 12.53 00:23:21.01 +54:55:48.6
118.86717 -7.71975 galactic Cas Second-epoch detections are separated by 6.4" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:21.01 +54:55:48.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:23:21.01 +54:55:48.6: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:23:21.01 +54:55:48.6: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 23 21.01 +54 55 48.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,2461274.8424,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 20260822.3424 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 08 22.3424 2461274.8424 12.43 23:27:19.37 +56:40:17.5
111.52814 -4.32630 galactic Cas Second-epoch detections are separated by 8.2" and 5.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:27:19.37 +56:40:17.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:19.37 +56:40:17.5: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:19.37 +56:40:17.5: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 19.37 +56 40 17.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,2461274.8424,12.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 12.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 12.55 23:12:59.22 +56:18:49.4
109.54311 -3.97724 galactic Cas Second-epoch detections are separated by 7.3" and 5.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 J348.2419+56.3061 | 23:12:59.22 +56:18:49.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:12:59.22 +56:18:49.4: 15.37 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:12:59.22 +56:18:49.4: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 12 59.22 +56 18 49.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 J348.2419+56.3061,2461274.8424,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
ATO J348.2419+56.3061 20260822.3424 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 08 22.3424 2461274.8424 13.51 23:13:28.29 +56:57:07.3
109.84215 -3.40907 galactic Cas Second-epoch detections are separated by 6.8" and 5.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 | DocumentRef: VOTx3610259 | 23:13:28.29 +56:57:07.3 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:13:28.29 +56:57:07.3: 15.37 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:13:28.29 +56:57:07.3: 14.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 13 28.29 +56 57 07.3 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3610259,2461274.8424,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3610259 20260822.3424 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.48 00:24:45.52 +53:56:01.6
118.96501 -8.73235 galactic Cas Second-epoch detections are separated by 3.6" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.2159+53.9365 | 00:24:49.95 +53:55:37.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:24:45.52 +53:56:01.6: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:24:45.52 +53:56:01.6: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 24 45.52 +53 56 01.6 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J006.2159+53.9365,2461274.8424,13.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 J006.2159+53.9365 20260822.3424 13.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 08 22.3424 2461274.8424 13.51 23:33:19.98 +56:17:51.8
112.20359 -4.93846 galactic Cas Second-epoch detections are separated by 5.1" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J353.3179+56.3052 | 23:33:19.98 +56:17:51.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:33:19.98 +56:17:51.8: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:33:19.98 +56:17:51.8: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 33 19.98 +56 17 51.8 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J353.3179+56.3052,2461274.8424,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J353.3179+56.3052 20260822.3424 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.61 23:17:13.98 +56:09:06.8
110.03498 -4.34278 galactic Cas Second-epoch detections are separated by 1.4" and 5.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 1997188727843968896 | 23:17:14.58 +56:08:21.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A7V (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:13.98 +56:09:06.8: 15.34 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:13.98 +56:09:06.8: 14.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 13.98 +56 09 06.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997188727843968896,2461274.8424,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997188727843968896 20260822.3424 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.52 00:26:57.25 +51:56:51.5
119.09623 -10.74167 galactic Cas Second-epoch detections are separated by 3.3" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:26:57.25 +51:56:51.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:26:57.25 +51:56:51.5: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:26:57.25 +51:56:51.5: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 26 57.25 +51 56 51.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.55 00:11:25.43 +51:27:58.5
116.60453 -10.91324 galactic Cas Second-epoch detections are separated by 8.8" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:25.43 +51:27:58.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:11:25.43 +51:27:58.5: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:11:25.43 +51:27:58.5: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 11 25.43 +51 27 58.5 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.63 23:37:00.76 +55:33:52.6
112.48362 -5.79008 galactic Cas Second-epoch detections are separated by 6.6" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:00.76 +55:33:52.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:00.76 +55:33:52.6: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:00.76 +55:33:52.6: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 00.76 +55 33 52.6 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.62 23:43:57.52 +50:48:28.8
112.17772 -10.64934 galactic Cas Second-epoch detections are separated by 6.2" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:57.52 +50:48:28.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:57.52 +50:48:28.8: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:57.52 +50:48:28.8: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 57.52 +50 48 28.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.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 20260822.3424 13.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 08 22.3424 2461274.8424 13.56 00:12:47.37 +49:45:30.1
116.55229 -12.63405 galactic Cas Second-epoch detections are separated by 6.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:47.37 +49:45:30.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:12:47.37 +49:45:30.1: 15.50 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:47.37 +49:45:30.1: 14.98 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.50 +/- 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 08 22.3424* 00 12 47.37 +49 45 30.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.57 23:48:48.78 +49:47:32.0
112.67897 -11.82872 galactic Cas Second-epoch detections are separated by 1.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:48.78 +49:47:32.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:48:48.78 +49:47:32.0: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:48:48.78 +49:47:32.0: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 48 48.78 +49 47 32.0 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.55 23:23:37.91 +52:10:26.6
109.53256 -8.39849 galactic And Second-epoch detections are separated by 2.0" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.9019+52.1860 | 23:23:37.91 +52:10:26.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:37.91 +52:10:26.6: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:37.91 +52:10:26.6: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 37.91 +52 10 26.6 13.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 J350.9019+52.1860,2461274.8424,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J350.9019+52.1860 20260822.3424 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.79 23:32:50.17 +51:17:32.7
110.61404 -9.68969 galactic Cas Second-epoch detections are separated by 6.4" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:32:50.17 +51:17:32.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:50.17 +51:17:32.7: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:50.17 +51:17:32.7: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 50.17 +51 17 32.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.78 23:19:26.43 +55:24:32.2
110.06329 -5.14744 galactic Cas Second-epoch detections are separated by 8.8" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:26.43 +55:24:32.2 (user input) | T | P | (position from user input) J-Ks=0.566+/- (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:26.43 +55:24:32.2: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:19:26.43 +55:24:32.2: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 19 26.43 +55 24 32.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.80 00:30:44.10 +55:16:19.3
119.96081 -7.48024 galactic Cas Second-epoch detections are separated by 8.3" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:30:44.10 +55:16:19.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:30:44.10 +55:16:19.3: 15.36 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:30:44.10 +55:16:19.3: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 30 44.10 +55 16 19.3 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.80 00:08:01.33 +52:54:48.5
116.32264 -9.40023 galactic Cas Second-epoch detections are separated by 7.6" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3961979 | 00:08:01.33 +52:54:48.5 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:08:01.33 +52:54:48.5: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:08:01.33 +52:54:48.5: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 08 01.33 +52 54 48.5 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3961979,2461274.8424,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3961979 20260822.3424 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.90 23:18:15.39 +54:05:47.9
109.43882 -6.31588 galactic Cas Second-epoch detections are separated by 6.3" and 5.5 pix
The object was found in VSX14" Gaia DR3 1995967754538602368
Type: RS
# Max. Min./Amp. JD0 Period
16.680 G 16.760 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:18:15.39 +54:05:47.9: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:18:15.39 +54:05:47.9: 14.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 18 15.39 +54 05 47.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1995967754538602368,2461274.8424,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1995967754538602368 20260822.3424 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.77 23:48:50.93 +52:53:26.7
113.45337 -8.82529 galactic Cas Second-epoch detections are separated by 3.3" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J357.2195+52.8965 | 23:48:52.47 +52:54:03.6 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:48:50.93 +52:53:26.7: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:48:50.93 +52:53:26.7: 15.13 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 48 50.93 +52 53 26.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.2195+52.8965,2461274.8424,13.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 J357.2195+52.8965 20260822.3424 13.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 08 22.3424 2461274.8424 13.77 23:18:00.09 +54:03:30.8
109.39005 -6.33823 galactic Cas Second-epoch detections are separated by 2.0" and 5.8 pix
The object was found in VSX18" ZTF J231759.49+540348.4
Type: EW
# Max. Min./Amp. JD0 Period
19.034 r Y 0.396 r 2458634.92800 0.433017000000
ATTENTION: measured mag 13.77 is 4.9 mag brighter than the VSX record maximum brightness 18.64 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:18:00.09 +54:03:30.8: 15.42 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:18:00.09 +54:03:30.8: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 18 00.09 +54 03 30.8 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J231759.49+540348.4,2461274.8424,13.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
ZTF J231759.49+540348.4 20260822.3424 13.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 08 22.3424 2461274.8424 13.78 00:24:54.29 +53:42:17.4
118.96255 -8.96230 galactic Cas Second-epoch detections are separated by 5.9" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:54.29 +53:42:17.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:24:54.29 +53:42:17.4: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:24:54.29 +53:42:17.4: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 24 54.29 +53 42 17.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.88 23:57:04.14 +52:12:07.1
114.52762 -9.78035 galactic Cas Second-epoch detections are separated by 8.2" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:04.14 +52:12:07.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:57:04.14 +52:12:07.1: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:57:04.14 +52:12:07.1: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 57 04.14 +52 12 07.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.95 00:05:13.84 +51:50:45.1
115.70671 -10.37648 galactic Cas Second-epoch detections are separated by 7.6" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4021008 | 00:05:13.84 +51:50:45.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:13.84 +51:50:45.1: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:05:13.84 +51:50:45.1: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 05 13.84 +51 50 45.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4021008,2461274.8424,13.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx4021008 20260822.3424 13.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.82 23:24:14.45 +53:00:33.2
109.90302 -7.64252 galactic And Second-epoch detections are separated by 4.3" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4046046 | 23:24:14.45 +53:00:33.2 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:14.45 +53:00:33.2: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:14.45 +53:00:33.2: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 14.45 +53 00 33.2 13.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
DocumentRef: VOTx4046046,2461274.8424,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx4046046 20260822.3424 13.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.78 23:21:43.60 +55:58:25.2
110.56231 -4.72850 galactic Cas Second-epoch detections are separated by 3.5" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:43.60 +55:58:25.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:43.60 +55:58:25.2: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:43.60 +55:58:25.2: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 43.60 +55 58 25.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.87 23:30:29.36 +54:34:20.5
111.29002 -6.45936 galactic Cas Second-epoch detections are separated by 2.7" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:29.36 +54:34:20.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:29.36 +54:34:20.5: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:29.36 +54:34:20.5: 14.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 29.36 +54 34 20.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.82 00:27:11.98 +54:05:42.0
119.34219 -8.60772 galactic Cas Second-epoch detections are separated by 4.6" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 419566769506900736 | 00:27:07.88 +54:06:01.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:27:11.98 +54:05:42.0: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:27:11.98 +54:05:42.0: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 27 11.98 +54 05 42.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 419566769506900736,2461274.8424,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419566769506900736 20260822.3424 13.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.88 00:05:10.94 +52:08:57.8
115.75516 -10.07663 galactic Cas Second-epoch detections are separated by 2.7" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4089337 | 00:05:10.94 +52:08:57.8 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:10.94 +52:08:57.8: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:05:10.94 +52:08:57.8: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 05 10.94 +52 08 57.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4089337,2461274.8424,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx4089337 20260822.3424 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.92 00:27:35.95 +51:54:37.9
119.19338 -10.78809 galactic Cas Second-epoch detections are separated by 2.1" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:27:35.95 +51:54:37.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:27:35.95 +51:54:37.9: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:27:35.95 +51:54:37.9: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 27 35.95 +51 54 37.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.89 00:18:16.28 +50:20:06.5
117.52822 -12.18830 galactic Cas Second-epoch detections are separated by 8.3" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4111586 | 00:18:16.28 +50:20:06.5 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:18:16.28 +50:20:06.5: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:18:16.28 +50:20:06.5: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 18 16.28 +50 20 06.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4111586,2461274.8424,13.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
DocumentRef: VOTx4111586 20260822.3424 13.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 08 22.3424 2461274.8424 14.00 00:14:55.85 +52:36:26.6
117.32107 -9.86619 galactic Cas Second-epoch detections are separated by 5.4" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:14:55.85 +52:36:26.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:14:55.85 +52:36:26.6: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:14:55.85 +52:36:26.6: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 14 55.85 +52 36 26.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.94 00:07:14.12 +54:10:58.2
116.42588 -8.12959 galactic Cas Second-epoch detections are separated by 3.9" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4169030 | 00:07:14.12 +54:10:58.2 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:14.12 +54:10:58.2: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:14.12 +54:10:58.2: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 07 14.12 +54 10 58.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4169030,2461274.8424,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx4169030 20260822.3424 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:53:56.57 +50:54:38.7
113.75863 -10.93409 galactic Cas Second-epoch detections are separated by 2.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:53:56.57 +50:54:38.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:53:56.57 +50:54:38.7: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:53:56.57 +50:54:38.7: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 53 56.57 +50 54 38.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.02 00:09:57.80 +50:50:42.4
116.27250 -11.48958 galactic Cas Second-epoch detections are separated by 1.8" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:57.80 +50:50:42.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:09:57.80 +50:50:42.4: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:09:57.80 +50:50:42.4: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 09 57.80 +50 50 42.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.92 23:36:32.93 +49:50:56.6
110.74982 -11.24303 galactic And Second-epoch detections are separated by 8.5" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:36:32.93 +49:50:56.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:36:32.93 +49:50:56.6: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:36:32.93 +49:50:56.6: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 36 32.93 +49 50 56.6 13.9 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 00:03:48.58 +53:38:54.6
115.82763 -8.56499 galactic Cas Second-epoch detections are separated by 2.4" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:48.58 +53:38:54.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:03:48.58 +53:38:54.6: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:03:48.58 +53:38:54.6: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 03 48.58 +53 38 54.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.04 23:34:35.33 +52:37:11.9
111.27808 -8.50420 galactic Cas Second-epoch detections are separated by 2.0" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx102307 | 23:34:35.33 +52:37:11.9 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:35.33 +52:37:11.9: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:35.33 +52:37:11.9: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 35.33 +52 37 11.9 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx102307,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx102307 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:30:12.41 +50:50:41.1
110.07505 -9.98802 galactic Cas Second-epoch detections are separated by 5.1" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx113088 | 23:30:12.41 +50:50:41.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:12.41 +50:50:41.1: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:12.41 +50:50:41.1: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 12.41 +50 50 41.1 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx113088,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx113088 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.02 23:51:21.35 +49:51:40.4
113.10264 -11.86039 galactic Cas Second-epoch detections are separated by 1.6" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:51:21.35 +49:51:40.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:51:21.35 +49:51:40.4: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:51:21.35 +49:51:40.4: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 51 21.35 +49 51 40.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.98 23:19:19.45 +51:15:48.0
108.58158 -9.02368 galactic And Second-epoch detections are separated by 4.7" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1991528609478611200 | 23:19:17.87 +51:16:31.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:19.45 +51:15:48.0: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:19:19.45 +51:15:48.0: 14.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 19 19.45 +51 15 48.0 14.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
Gaia DR3 1991528609478611200,2461274.8424,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1991528609478611200 20260822.3424 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.93 23:26:40.69 +52:55:03.1
110.22233 -7.84989 galactic Cas Second-epoch detections are separated by 6.7" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.6870+52.9113 | 23:26:40.69 +52:55:03.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:40.69 +52:55:03.1: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:40.69 +52:55:03.1: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 40.69 +52 55 03.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J351.6870+52.9113,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J351.6870+52.9113 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.96 23:14:03.80 +55:28:47.7
109.37440 -4.80772 galactic Cas Second-epoch detections are separated by 7.9" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J348.5326+55.4819 | 23:14:03.80 +55:28:47.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:03.80 +55:28:47.7: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:03.80 +55:28:47.7: 14.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 03.80 +55 28 47.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J348.5326+55.4819,2461274.8424,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J348.5326+55.4819 20260822.3424 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.99 23:31:43.27 +51:03:17.0
110.37144 -9.86257 galactic Cas Second-epoch detections are separated by 6.7" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx226913 | 23:31:43.27 +51:03:17.0 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:31:43.27 +51:03:17.0: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:31:43.27 +51:03:17.0: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 31 43.27 +51 03 17.0 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx226913,2461274.8424,13.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx226913 20260822.3424 13.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.99 00:07:47.15 +53:00:29.4
116.30345 -9.30086 galactic Cas Second-epoch detections are separated by 7.0" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.9369+52.9964 | 00:07:47.15 +53:00:29.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:47.15 +53:00:29.4: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:47.15 +53:00:29.4: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 07 47.15 +53 00 29.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.9369+52.9964,2461274.8424,13.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.9369+52.9964 20260822.3424 13.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.01 23:23:22.60 +51:40:38.1
109.32578 -8.85298 galactic And Second-epoch detections are separated by 5.1" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:22.60 +51:40:38.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:22.60 +51:40:38.1: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:22.60 +51:40:38.1: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 22.60 +51 40 38.1 14.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,2461274.8424,14.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.90 23:55:21.24 +50:40:11.1
113.92557 -11.21866 galactic Cas Second-epoch detections are separated by 4.5" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx207834 | 23:55:21.24 +50:40:11.1 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:55:21.24 +50:40:11.1: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:55:21.24 +50:40:11.1: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 55 21.24 +50 40 11.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx207834,2461274.8424,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx207834 20260822.3424 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.00 23:27:00.19 +54:16:26.7
110.71092 -6.58197 galactic Cas Second-epoch detections are separated by 4.7" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:00.19 +54:16:26.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:00.19 +54:16:26.7: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:00.19 +54:16:26.7: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 00.19 +54 16 26.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.93 23:34:14.12 +55:20:17.7
112.03876 -5.89225 galactic Cas Second-epoch detections are separated by 2.4" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:14.12 +55:20:17.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:14.12 +55:20:17.7: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:14.12 +55:20:17.7: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 14.12 +55 20 17.7 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.04 23:22:05.80 +53:17:47.3
109.69550 -7.26370 galactic Cas Second-epoch detections are separated by 5.5" and 5.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:22:05.80 +53:17:47.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:05.80 +53:17:47.3: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:05.80 +53:17:47.3: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 05.80 +53 17 47.3 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.86 23:13:13.49 +55:44:24.7
109.36053 -4.52211 galactic Cas Second-epoch detections are separated by 1.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx280076 | 23:13:13.49 +55:44:24.7 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:13:13.49 +55:44:24.7: 15.38 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:13:13.49 +55:44:24.7: 14.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 13 13.49 +55 44 24.7 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx280076,2461274.8424,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx280076 20260822.3424 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.04 23:42:14.10 +53:08:23.2
112.54501 -8.33064 galactic Cas Second-epoch detections are separated by 7.8" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx289576 | 23:42:14.10 +53:08:23.2 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:42:14.10 +53:08:23.2: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:42:14.10 +53:08:23.2: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 42 14.10 +53 08 23.2 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx289576,2461274.8424,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx289576 20260822.3424 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.03 23:40:46.26 +52:40:44.0
112.20413 -8.71469 galactic Cas Second-epoch detections are separated by 3.1" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J355.2046+52.6758 | 23:40:46.26 +52:40:44.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:40:46.26 +52:40:44.0: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:40:46.26 +52:40:44.0: 15.10 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 40 46.26 +52 40 44.0 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.2046+52.6758,2461274.8424,14.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
ATO J355.2046+52.6758 20260822.3424 14.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 08 22.3424 2461274.8424 14.27 23:53:13.59 +50:51:15.3
113.63350 -10.96354 galactic Cas Second-epoch detections are separated by 8.0" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J358.3007+50.8653 | 23:53:13.59 +50:51:15.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:53:13.59 +50:51:15.3: 15.23 +/- 0.24 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:53:13.59 +50:51:15.3: 14.94 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.14 +/- 0.20
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 53 13.59 +50 51 15.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J358.3007+50.8653,2461274.8424,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.3007+50.8653 20260822.3424 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.06 23:30:30.78 +54:53:17.5
111.39169 -6.16011 galactic Cas Second-epoch detections are separated by 2.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:30.78 +54:53:17.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:30.78 +54:53:17.5: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:30.78 +54:53:17.5: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 30.78 +54 53 17.5 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.09 00:14:11.97 +51:14:39.1
117.00651 -11.19862 galactic Cas Second-epoch detections are separated by 5.8" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx389016 | 00:14:11.97 +51:14:39.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:14:11.97 +51:14:39.1: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:14:11.97 +51:14:39.1: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 14 11.97 +51 14 39.1 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx389016,2461274.8424,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx389016 20260822.3424 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.97 23:17:56.32 +56:24:57.6
110.22087 -4.13070 galactic Cas Second-epoch detections are separated by 8.9" and 5.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 | DocumentRef: VOTx402409 | 23:17:56.32 +56:24:57.6 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:56.32 +56:24:57.6: 15.26 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:56.32 +56:24:57.6: 14.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.26 +/- 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 08 22.3424* 23 17 56.32 +56 24 57.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx402409,2461274.8424,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx402409 20260822.3424 13.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 13.98 23:55:59.11 +52:04:39.5
114.33572 -9.86615 galactic Cas Second-epoch detections are separated by 6.2" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:59.11 +52:04:39.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:55:59.11 +52:04:39.5: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:55:59.11 +52:04:39.5: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 55 59.11 +52 04 39.5 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.15 23:36:21.73 +55:45:35.0
112.45149 -5.57686 galactic Cas Second-epoch detections are separated by 4.4" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:36:21.73 +55:45:35.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:36:21.73 +55:45:35.0: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:36:21.73 +55:45:35.0: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 36 21.73 +55 45 35.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.20 00:12:55.73 +51:32:02.4
116.85085 -10.88249 galactic Cas Second-epoch detections are separated by 8.3" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:55.73 +51:32:02.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:12:55.73 +51:32:02.4: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:55.73 +51:32:02.4: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 12 55.73 +51 32 02.4 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.23 23:17:45.15 +56:02:14.3
110.06201 -4.47564 galactic Cas Second-epoch detections are separated by 2.9" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:17:45.15 +56:02:14.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:45.15 +56:02:14.3: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:45.15 +56:02:14.3: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 45.15 +56 02 14.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 23:16:26.86 +55:52:30.9
109.83284 -4.56178 galactic Cas Second-epoch detections are separated by 3.9" and 5.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 | DocumentRef: VOTx901485 | 23:16:26.86 +55:52:30.9 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:16:26.86 +55:52:30.9: 15.39 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:16:26.86 +55:52:30.9: 14.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 16 26.86 +55 52 30.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx901485,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx901485 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.21 23:55:40.56 +51:20:10.9
114.12455 -10.57931 galactic Cas Second-epoch detections are separated by 5.8" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx948947 | 23:55:40.56 +51:20:10.9 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:55:40.56 +51:20:10.9: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:55:40.56 +51:20:10.9: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 55 40.56 +51 20 10.9 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx948947,2461274.8424,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx948947 20260822.3424 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.15 23:21:29.90 +53:08:53.6
109.55953 -7.37237 galactic And Second-epoch detections are separated by 2.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx986824 | 23:21:29.90 +53:08:53.6 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:29.90 +53:08:53.6: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:29.90 +53:08:53.6: 14.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 29.90 +53 08 53.6 14.2 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
DocumentRef: VOTx986824,2461274.8424,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx986824 20260822.3424 14.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.20 23:34:13.01 +49:48:44.1
110.37249 -11.16704 galactic And Second-epoch detections are separated by 2.1" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1034767 | 23:34:13.01 +49:48:44.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:13.01 +49:48:44.1: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:13.01 +49:48:44.1: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 13.01 +49 48 44.1 14.2 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
DocumentRef: VOTx1034767,2461274.8424,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1034767 20260822.3424 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.23 23:26:59.06 +52:45:09.1
110.21247 -8.02097 galactic Cas Second-epoch detections are separated by 5.9" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:26:59.06 +52:45:09.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:59.06 +52:45:09.1: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:59.06 +52:45:09.1: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 59.06 +52 45 09.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.28 23:20:52.72 +50:30:19.5
108.54541 -9.81946 galactic And Second-epoch detections are separated by 7.3" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:20:52.72 +50:30:19.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:20:52.72 +50:30:19.5: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:20:52.72 +50:30:19.5: 14.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 20 52.72 +50 30 19.5 14.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.43 00:07:39.23 +50:26:56.5
115.83604 -11.81850 galactic Cas Second-epoch detections are separated by 1.9" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.9246+50.4449 | 00:07:39.23 +50:26:56.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:07:39.23 +50:26:56.5: 15.53 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:07:39.23 +50:26:56.5: 15.01 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.53 +/- 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 08 22.3424* 00 07 39.23 +50 26 56.5 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.9246+50.4449,2461274.8424,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.9246+50.4449 20260822.3424 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.38 00:13:00.67 +50:20:20.4
116.67893 -12.06562 galactic Cas Second-epoch detections are separated by 5.1" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1248865 | 00:13:00.67 +50:20:20.4 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:00.67 +50:20:20.4: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:00.67 +50:20:20.4: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 00.67 +50 20 20.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1248865,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1248865 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.45 23:32:56.10 +50:39:59.2
110.43604 -10.29082 galactic And Second-epoch detections are separated by 5.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:32:56.10 +50:39:59.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:56.10 +50:39:59.2: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:56.10 +50:39:59.2: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 56.10 +50 39 59.2 14.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,2461274.8424,14.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.14 23:17:33.59 +53:46:10.8
109.22540 -6.58506 galactic Cas Second-epoch detections are separated by 5.2" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1379423 | 23:17:33.59 +53:46:10.8 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:33.59 +53:46:10.8: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:33.59 +53:46:10.8: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 33.59 +53 46 10.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1379423,2461274.8424,14.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1379423 20260822.3424 14.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 23:43:52.54 +51:14:18.6
112.27994 -10.23054 galactic Cas Second-epoch detections are separated by 6.6" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:52.54 +51:14:18.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:52.54 +51:14:18.6: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:52.54 +51:14:18.6: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 52.54 +51 14 18.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 23:49:20.50 +51:33:06.1
113.19847 -10.14269 galactic Cas Second-epoch detections are separated by 8.1" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:49:20.50 +51:33:06.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:49:20.50 +51:33:06.1: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:49:20.50 +51:33:06.1: 15.05 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 49 20.50 +51 33 06.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.28 23:14:47.90 +57:31:28.9
110.21997 -2.94231 galactic Cas Second-epoch detections are separated by 6.5" and 5.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:14:47.90 +57:31:28.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:47.90 +57:31:28.9: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:47.90 +57:31:28.9: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 47.90 +57 31 28.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:21:51.60 +51:29:52.1
109.03973 -8.94151 galactic And Second-epoch detections are separated by 7.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J350.4617+51.4863 | 23:21:51.60 +51:29:52.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:51.60 +51:29:52.1: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:51.60 +51:29:52.1: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 51.60 +51 29 52.1 14.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
ATO J350.4617+51.4863,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J350.4617+51.4863 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.32 23:37:19.73 +55:38:16.1
112.54759 -5.73263 galactic Cas Second-epoch detections are separated by 4.4" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J354.3493+55.6493 | 23:37:22.98 +55:38:19.5 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:19.73 +55:38:16.1: 15.46 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:19.73 +55:38:16.1: 14.99 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.46 +/- 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 08 22.3424* 23 37 19.73 +55 38 16.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J354.3493+55.6493,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J354.3493+55.6493 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.16 23:32:22.09 +56:20:28.9
112.08869 -4.85666 galactic Cas Second-epoch detections are separated by 3.8" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1998509000783675648 | 23:32:21.99 +56:21:12.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:22.09 +56:20:28.9: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:22.09 +56:20:28.9: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 22.09 +56 20 28.9 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998509000783675648,2461274.8424,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998509000783675648 20260822.3424 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.21 23:41:00.07 +52:48:21.7
112.27311 -8.60187 galactic Cas Second-epoch detections are separated by 7.5" and 5.9 pix
The object was found in VSX22" ZTF J234058.91+524841.0
Type: RS
# Max. Min./Amp. JD0 Period
19.348 g Y 0.166 g 2458321.97400 1.609414800000
ATTENTION: measured mag 14.21 is 5.0 mag brighter than the VSX record maximum brightness 19.18 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:41:00.07 +52:48:21.7: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:41:00.07 +52:48:21.7: 15.10 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 41 00.07 +52 48 21.7 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J234058.91+524841.0,2461274.8424,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J234058.91+524841.0 20260822.3424 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.28 23:32:59.80 +52:10:47.4
110.91044 -8.85151 galactic Cas Second-epoch detections are separated by 7.8" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1993126749633618048 | 23:32:58.13 +52:11:25.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:59.80 +52:10:47.4: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:59.80 +52:10:47.4: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 32 59.80 +52 10 47.4 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993126749633618048,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1993126749633618048 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.20 00:12:03.51 +57:04:15.6
117.57510 -5.39061 galactic Cas Second-epoch detections are separated by 8.5" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:03.51 +57:04:15.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:12:03.51 +57:04:15.6: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:03.51 +57:04:15.6: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 12 03.51 +57 04 15.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.14 23:24:23.16 +56:09:52.8
110.97740 -4.67326 galactic Cas Second-epoch detections are separated by 5.4" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1687960 | 23:24:23.16 +56:09:52.8 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:23.16 +56:09:52.8: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:23.16 +56:09:52.8: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 23.16 +56 09 52.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1687960,2461274.8424,14.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1687960 20260822.3424 14.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.41 23:27:07.81 +50:41:41.7
109.55841 -9.97468 galactic Cas Second-epoch detections are separated by 3.8" and 6.1 pix
The object was found in VSX20" Gaia DR3 1991298467951102592
Type: VAR
# Max. Min./Amp. JD0 Period
17.590 G 17.730 G 0.064023500000
ATTENTION: measured mag 14.41 is 3.2 mag brighter than the VSX record maximum brightness 17.59 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:07.81 +50:41:41.7: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:07.81 +50:41:41.7: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 07.81 +50 41 41.7 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1991298467951102592,2461274.8424,14.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
Gaia DR3 1991298467951102592 20260822.3424 14.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 08 22.3424 2461274.8424 14.32 23:27:35.41 +51:17:51.6
109.82592 -9.42785 galactic Cas Second-epoch detections are separated by 2.4" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:35.41 +51:17:51.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:27:35.41 +51:17:51.6: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:35.41 +51:17:51.6: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 27 35.41 +51 17 51.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.37 23:19:28.03 +49:32:04.5
107.98367 -10.64912 galactic And Second-epoch detections are separated by 7.7" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:28.03 +49:32:04.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:28.03 +49:32:04.5: 15.33 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:19:28.03 +49:32:04.5: 14.78 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.33 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 19 28.03 +49 32 04.5 14.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,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.23 23:23:20.83 +49:55:24.5
108.71908 -10.50165 galactic And Second-epoch detections are separated by 0.8" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1846591 | 23:23:20.83 +49:55:24.5 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:20.83 +49:55:24.5: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:20.83 +49:55:24.5: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 20.83 +49 55 24.5 14.2 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
DocumentRef: VOTx1846591,2461274.8424,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1846591 20260822.3424 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.27 23:43:04.50 +51:10:43.8
112.14101 -10.25495 galactic Cas Second-epoch detections are separated by 2.4" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx1987733 | 23:43:04.50 +51:10:43.8 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:04.50 +51:10:43.8: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:04.50 +51:10:43.8: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 04.50 +51 10 43.8 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1987733,2461274.8424,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1987733 20260822.3424 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.13 00:13:09.78 +52:52:03.0
117.09122 -9.56965 galactic Cas Second-epoch detections are separated by 6.5" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:09.78 +52:52:03.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:09.78 +52:52:03.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:09.78 +52:52:03.0: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 09.78 +52 52 03.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.41 00:16:34.97 +51:26:36.1
117.41082 -11.05436 galactic Cas Second-epoch detections are separated by 0.6" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J004.1653+51.4421 | 00:16:34.97 +51:26:36.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:16:34.97 +51:26:36.1: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:16:34.97 +51:26:36.1: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 16 34.97 +51 26 36.1 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.1653+51.4421,2461274.8424,14.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 J004.1653+51.4421 20260822.3424 14.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 08 22.3424 2461274.8424 14.07 23:26:55.30 +56:27:00.1
111.40432 -4.51833 galactic Cas Second-epoch detections are separated by 4.0" and 5.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:26:55.30 +56:27:00.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:26:55.30 +56:27:00.1: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:26:55.30 +56:27:00.1: 14.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 26 55.30 +56 27 00.1 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.28 23:24:57.18 +56:11:24.6
111.06058 -4.67523 galactic Cas Second-epoch detections are separated by 0.9" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.2440+56.1972 | 23:24:57.18 +56:11:24.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:57.18 +56:11:24.6: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:57.18 +56:11:24.6: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 24 57.18 +56 11 24.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J351.2440+56.1972,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.2440+56.1972 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.36 00:13:03.03 +53:57:49.5
117.24096 -8.48329 galactic Cas Second-epoch detections are separated by 4.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:03.03 +53:57:49.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:13:03.03 +53:57:49.5: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:13:03.03 +53:57:49.5: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 13 03.03 +53 57 49.5 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.37 23:23:01.87 +49:50:17.6
108.64091 -10.56451 galactic And Second-epoch detections are separated by 4.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:01.87 +49:50:17.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:23:01.87 +49:50:17.6: 15.42 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:23:01.87 +49:50:17.6: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 23 01.87 +49 50 17.6 14.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,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.31 23:15:49.86 +56:17:11.3
109.90106 -4.14720 galactic Cas Second-epoch detections are separated by 4.1" and 5.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:15:49.86 +56:17:11.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:15:49.86 +56:17:11.3: 15.33 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:15:49.86 +56:17:11.3: 14.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 15 49.86 +56 17 11.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.22 23:14:25.17 +56:23:21.9
109.75599 -3.98011 galactic Cas Second-epoch detections are separated by 3.9" and 4.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:14:25.17 +56:23:21.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:25.17 +56:23:21.9: 15.38 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:25.17 +56:23:21.9: 14.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 25.17 +56 23 21.9 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.30 23:18:33.24 +51:55:27.1
108.70479 -8.36322 galactic And Second-epoch detections are separated by 4.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:18:33.24 +51:55:27.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:18:33.24 +51:55:27.1: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:18:33.24 +51:55:27.1: 14.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 18 33.24 +51 55 27.1 14.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.24 00:11:43.58 +53:03:48.3
116.90483 -9.34298 galactic Cas Second-epoch detections are separated by 2.6" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 395960461024531072 | 00:11:47.38 +53:03:50.9 (Gaia DR3) | ROT (local) | (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:11:43.58 +53:03:48.3: 15.58 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:11:43.58 +53:03:48.3: 15.05 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.58 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 11 43.58 +53 03 48.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 395960461024531072,2461274.8424,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 395960461024531072 20260822.3424 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.22 00:23:47.71 +50:48:32.2
118.47666 -11.82352 galactic Cas Second-epoch detections are separated by 7.5" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:47.71 +50:48:32.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:23:47.71 +50:48:32.2: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:23:47.71 +50:48:32.2: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 23 47.71 +50 48 32.2 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.51 00:00:54.74 +50:41:25.2
114.80800 -11.38272 galactic Cas Second-epoch detections are separated by 5.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 394024805165032576 | 00:00:55.81 +50:42:10.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: B5 1927AnHar.100...33C HD 236273
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:54.74 +50:41:25.2: 15.56 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:54.74 +50:41:25.2: 14.98 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.56 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 00 54.74 +50 41 25.2 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 394024805165032576,2461274.8424,14.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 394024805165032576 20260822.3424 14.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 23:31:21.08 +52:54:30.6
110.89430 -8.08127 galactic Cas Second-epoch detections are separated by 4.6" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:21.08 +52:54:30.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:31:21.08 +52:54:30.6: 15.46 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:31:21.08 +52:54:30.6: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 31 21.08 +52 54 30.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.24 00:09:12.86 +53:00:00.4
116.51676 -9.34490 galactic Cas Second-epoch detections are separated by 8.9" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:12.86 +53:00:00.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:09:12.86 +53:00:00.4: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:09:12.86 +53:00:00.4: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 09 12.86 +53 00 00.4 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 23:43:04.70 +54:54:23.7
113.13840 -6.66006 galactic Cas Second-epoch detections are separated by 6.9" and 5.6 pix
The object was found in VSX23" Gaia DR3 1994247048902984960
Type: E
# Max. Min./Amp. JD0 Period
19.090 G 19.350 G 0.296124000000
ATTENTION: measured mag 14.34 is 4.8 mag brighter than the VSX record maximum brightness 19.09 - 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:04.70 +54:54:23.7: 15.62 +/- 0.36 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:04.70 +54:54:23.7: 14.97 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.62 +/- 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 08 22.3424* 23 43 04.70 +54 54 23.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1994247048902984960,2461274.8424,14.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
Gaia DR3 1994247048902984960 20260822.3424 14.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 08 22.3424 2461274.8424 14.29 23:17:32.12 +55:39:03.6
109.89571 -4.82591 galactic Cas Second-epoch detections are separated by 5.6" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.4005+55.6482 | 23:17:32.12 +55:39:03.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:32.12 +55:39:03.6: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:32.12 +55:39:03.6: 14.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 32.12 +55 39 03.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.4005+55.6482,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J349.4005+55.6482 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.32 23:17:22.54 +55:37:27.5
109.86504 -4.84283 galactic Cas Second-epoch detections are separated by 7.6" and 5.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:17:22.54 +55:37:27.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:22.54 +55:37:27.5: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:22.54 +55:37:27.5: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 22.54 +55 37 27.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.29 00:28:58.98 +53:42:04.1
119.57041 -9.02399 galactic Cas Second-epoch detections are separated by 7.9" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3295737 | 00:28:58.98 +53:42:04.1 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:28:58.98 +53:42:04.1: 15.54 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:28:58.98 +53:42:04.1: 14.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 28 58.98 +53 42 04.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3295737,2461274.8424,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3295737 20260822.3424 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.39 00:01:26.42 +50:22:03.1
114.82684 -11.71574 galactic Cas Second-epoch detections are separated by 4.3" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:26.42 +50:22:03.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:01:26.42 +50:22:03.1: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:01:26.42 +50:22:03.1: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 01 26.42 +50 22 03.1 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.38 00:00:45.69 +51:03:39.9
114.85932 -11.01464 galactic Cas Second-epoch detections are separated by 7.7" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:45.69 +51:03:39.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:45.69 +51:03:39.9: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:45.69 +51:03:39.9: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 00 45.69 +51 03 39.9 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.32 23:30:56.17 +51:13:56.1
110.30834 -9.65566 galactic Cas Second-epoch detections are separated by 7.8" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3363350 | 23:30:56.17 +51:13:56.1 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:30:56.17 +51:13:56.1: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:56.17 +51:13:56.1: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 30 56.17 +51 13 56.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3363350,2461274.8424,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3363350 20260822.3424 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.24 23:14:43.92 +53:06:03.5
108.58620 -7.05590 galactic And Second-epoch detections are separated by 2.7" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3360612 | 23:14:43.92 +53:06:03.5 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:43.92 +53:06:03.5: 15.42 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:43.92 +53:06:03.5: 14.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 43.92 +53 06 03.5 14.2 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
DocumentRef: VOTx3360612,2461274.8424,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3360612 20260822.3424 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.39 23:21:55.22 +51:05:36.7
108.90813 -9.32445 galactic And Second-epoch detections are separated by 4.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3504299 | 23:21:55.22 +51:05:36.7 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:55.22 +51:05:36.7: 15.53 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:55.22 +51:05:36.7: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 55.22 +51 05 36.7 14.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
DocumentRef: VOTx3504299,2461274.8424,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3504299 20260822.3424 14.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:25:01.13 +56:45:07.0
111.25444 -4.14767 galactic Cas Second-epoch detections are separated by 5.4" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.2596+56.7467 | 23:25:01.13 +56:45:07.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:01.13 +56:45:07.0: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:01.13 +56:45:07.0: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 01.13 +56 45 07.0 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J351.2596+56.7467,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J351.2596+56.7467 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.37 23:37:56.15 +56:26:08.7
112.85601 -4.99128 galactic Cas Second-epoch detections are separated by 2.2" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:37:56.15 +56:26:08.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:37:56.15 +56:26:08.7: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:37:56.15 +56:26:08.7: 14.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 37 56.15 +56 26 08.7 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.37 23:17:36.19 +50:30:27.5
108.05194 -9.63327 galactic And Second-epoch detections are separated by 2.8" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:17:36.19 +50:30:27.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:17:36.19 +50:30:27.5: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:17:36.19 +50:30:27.5: 14.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 17 36.19 +50 30 27.5 14.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,2461274.8424,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.24 23:33:43.67 +53:53:45.8
111.53690 -7.24753 galactic Cas Second-epoch detections are separated by 7.2" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:43.67 +53:53:45.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:33:43.67 +53:53:45.8: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:33:43.67 +53:53:45.8: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 33 43.67 +53 53 45.8 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.43 23:52:18.79 +50:33:05.4
113.41923 -11.22499 galactic Cas Second-epoch detections are separated by 7.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3759901 | 23:52:18.79 +50:33:05.4 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:18.79 +50:33:05.4: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:18.79 +50:33:05.4: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 18.79 +50 33 05.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3759901,2461274.8424,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3759901 20260822.3424 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.31 23:34:13.53 +56:18:06.3
112.32345 -4.97138 galactic Cas Second-epoch detections are separated by 2.5" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:13.53 +56:18:06.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:13.53 +56:18:06.3: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:13.53 +56:18:06.3: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 34 13.53 +56 18 06.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.31 23:12:27.57 +56:09:43.7
109.41832 -4.09061 galactic Cas Second-epoch detections are separated by 4.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3755012 | 23:12:27.57 +56:09:43.7 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:12:27.57 +56:09:43.7: 15.31 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:12:27.57 +56:09:43.7: 14.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 12 27.57 +56 09 43.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3755012,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3755012 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:48:21.25 +51:56:48.5
113.14573 -9.72225 galactic Cas Second-epoch detections are separated by 7.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3760235 | 23:48:21.25 +51:56:48.5 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:48:21.25 +51:56:48.5: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:48:21.25 +51:56:48.5: 15.12 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 48 21.25 +51 56 48.5 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3760235,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3760235 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:51:33.28 +50:53:06.4
113.37940 -10.87260 galactic Cas Second-epoch detections are separated by 2.6" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:51:33.28 +50:53:06.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:51:33.28 +50:53:06.4: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:51:33.28 +50:53:06.4: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 51 33.28 +50 53 06.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.31 23:22:24.22 +49:39:45.1
108.48288 -10.69497 galactic And Second-epoch detections are separated by 4.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:24.22 +49:39:45.1 (user input) | T | P | (position from user input) J-Ks=0.675+/-0.144 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:24.22 +49:39:45.1: 15.47 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:24.22 +49:39:45.1: 14.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 24.22 +49 39 45.1 14.3 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.40 23:13:59.58 +56:34:36.6
109.77008 -3.78417 galactic Cas Second-epoch detections are separated by 2.8" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:13:59.58 +56:34:36.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:13:59.58 +56:34:36.6: 15.39 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:13:59.58 +56:34:36.6: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 13 59.58 +56 34 36.6 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.47 23:22:05.22 +50:07:46.4
108.59726 -10.23883 galactic And Second-epoch detections are separated by 3.8" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:05.22 +50:07:46.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:05.22 +50:07:46.4: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:05.22 +50:07:46.4: 14.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 05.22 +50 07 46.4 14.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,2461274.8424,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.47 23:43:49.10 +49:48:53.3
111.88898 -11.60154 galactic Cas Second-epoch detections are separated by 6.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:49.10 +49:48:53.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:43:49.10 +49:48:53.3: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:43:49.10 +49:48:53.3: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 43 49.10 +49 48 53.3 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.45 00:11:32.61 +50:42:08.2
116.50082 -11.67064 galactic Cas Second-epoch detections are separated by 2.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:32.61 +50:42:08.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:11:32.61 +50:42:08.2: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:11:32.61 +50:42:08.2: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 11 32.61 +50 42 08.2 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.31 23:54:21.46 +50:47:55.7
113.79805 -11.05786 galactic Cas Second-epoch detections are separated by 6.8" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:54:21.46 +50:47:55.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:54:21.46 +50:47:55.7: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:54:21.46 +50:47:55.7: 15.11 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 54 21.46 +50 47 55.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.35 23:38:10.23 +50:41:38.0
111.25015 -10.50856 galactic Cas Second-epoch detections are separated by 4.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:38:10.23 +50:41:38.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:38:10.23 +50:41:38.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:38:10.23 +50:41:38.0: 15.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 38 10.23 +50 41 38.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.42 23:35:11.46 +51:47:21.8
111.11900 -9.32498 galactic Cas Second-epoch detections are separated by 6.1" and 6.0 pix
The object was found in VSX19" Gaia DR3 1992860191080584448
Type: ROT
# Max. Min./Amp. JD0 Period
14.480 G 14.510 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:11.46 +51:47:21.8: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:11.46 +51:47:21.8: 15.03 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 35 11.46 +51 47 21.8 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1992860191080584448,2461274.8424,14.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 1992860191080584448 20260822.3424 14.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 08 22.3424 2461274.8424 14.36 23:56:55.48 +51:01:06.4
114.24921 -10.93198 galactic Cas Second-epoch detections are separated by 5.9" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:56:55.48 +51:01:06.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:56:55.48 +51:01:06.4: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:56:55.48 +51:01:06.4: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 56 55.48 +51 01 06.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.47 23:31:26.83 +50:23:06.7
110.11953 -10.48600 galactic And Second-epoch detections are separated by 1.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:26.83 +50:23:06.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:31:26.83 +50:23:06.7: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:31:26.83 +50:23:06.7: 15.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 31 26.83 +50 23 06.7 14.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,2461274.8424,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.35 23:25:12.43 +54:01:44.9
110.38026 -6.72782 galactic Cas Second-epoch detections are separated by 8.6" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:12.43 +54:01:44.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:12.43 +54:01:44.9: 15.52 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:12.43 +54:01:44.9: 14.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 12.43 +54 01 44.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.48 23:45:35.78 +54:51:42.9
113.47897 -6.79686 galactic Cas Second-epoch detections are separated by 3.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:35.78 +54:51:42.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:45:35.78 +54:51:42.9: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:45:35.78 +54:51:42.9: 15.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 45 35.78 +54 51 42.9 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.44 23:44:13.10 +51:12:16.7
112.32354 -10.27728 galactic Cas Second-epoch detections are separated by 7.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:44:13.10 +51:12:16.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:44:13.10 +51:12:16.7: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:44:13.10 +51:12:16.7: 15.11 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 44 13.10 +51 12 16.7 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.38 23:19:24.43 +56:40:31.3
110.50218 -3.95899 galactic Cas Second-epoch detections are separated by 7.8" and 5.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:19:24.43 +56:40:31.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:24.43 +56:40:31.3: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:19:24.43 +56:40:31.3: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 19 24.43 +56 40 31.3 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 23:52:42.36 +51:25:47.3
113.68649 -10.38456 galactic Cas Second-epoch detections are separated by 7.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:42.36 +51:25:47.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:52:42.36 +51:25:47.3: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:52:42.36 +51:25:47.3: 15.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 52 42.36 +51 25 47.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.35 23:49:17.43 +52:48:58.4
113.50059 -8.91374 galactic Cas Second-epoch detections are separated by 1.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:49:17.43 +52:48:58.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:49:17.43 +52:48:58.4: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:49:17.43 +52:48:58.4: 15.07 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 49 17.43 +52 48 58.4 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.46 23:28:45.64 +52:34:31.8
110.41285 -8.27500 galactic Cas Second-epoch detections are separated by 6.9" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:45.64 +52:34:31.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:28:45.64 +52:34:31.8: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:28:45.64 +52:34:31.8: 14.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 28 45.64 +52 34 31.8 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.38 00:14:22.10 +52:18:11.0
117.19032 -10.15495 galactic Cas Second-epoch detections are separated by 6.1" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx3971519 | 00:14:22.10 +52:18:11.0 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:14:22.10 +52:18:11.0: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:14:22.10 +52:18:11.0: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 14 22.10 +52 18 11.0 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3971519,2461274.8424,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx3971519 20260822.3424 14.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.34 23:14:00.70 +56:27:36.2
109.72942 -3.89370 galactic Cas Second-epoch detections are separated by 7.5" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:14:00.70 +56:27:36.2 (user input) | T | P | (position from user input) J-Ks=-0.142+/- (B)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:14:00.70 +56:27:36.2: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:00.70 +56:27:36.2: 14.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 14 00.70 +56 27 36.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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 20260822.3424 14.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 08 22.3424 2461274.8424 14.43 00:02:01.35 +52:54:05.5
115.41896 -9.24788 galactic Cas Second-epoch detections are separated by 3.0" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | DocumentRef: VOTx4019084 | 00:02:01.35 +52:54:05.5 (user input) | (GCVS) | (GCVS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:02:01.35 +52:54:05.5: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:02:01.35 +52:54:05.5: 15.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 02 01.35 +52 54 05.5 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4019084,2461274.8424,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx4019084 20260822.3424 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.31 23:25:23.20 +54:25:11.6
110.53453 -6.36743 galactic Cas Second-epoch detections are separated by 8.6" and 5.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J351.3584+54.4267 | 23:25:23.20 +54:25:11.6 (user input) | CBH (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:23.20 +54:25:11.6: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:23.20 +54:25:11.6: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 23.20 +54 25 11.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J351.3584+54.4267,2461274.8424,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J351.3584+54.4267 20260822.3424 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.28 23:15:17.88 +54:16:36.7
109.09772 -5.99220 galactic Cas Second-epoch detections are separated by 0.3" and 5.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:15:17.88 +54:16:36.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:15:17.88 +54:16:36.7: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:15:17.88 +54:16:36.7: 14.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 15 17.88 +54 16 36.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.30 23:36:06.17 +55:53:50.2
112.45628 -5.43465 galactic Cas Second-epoch detections are separated by 3.3" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:36:06.17 +55:53:50.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:36:06.17 +55:53:50.2: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:36:06.17 +55:53:50.2: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 36 06.17 +55 53 50.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.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
target 20260822.3424 14.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 08 22.3424 2461274.8424 14.40 23:25:37.03 +56:43:28.1
111.32315 -4.20049 galactic Cas Second-epoch detections are separated by 5.7" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1997265762376025728 | 23:25:41.41 +56:43:17.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:25:37.03 +56:43:28.1: 15.44 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:25:37.03 +56:43:28.1: 14.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 25 37.03 +56 43 28.1 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997265762376025728,2461274.8424,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997265762376025728 20260822.3424 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.35 00:24:26.44 +54:50:32.6
119.01497 -7.82391 galactic Cas Second-epoch detections are separated by 5.3" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:26.44 +54:50:32.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:24:26.44 +54:50:32.6: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:24:26.44 +54:50:32.6: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 00 24 26.44 +54 50 32.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.43 23:22:22.33 +56:30:16.3
110.82767 -4.25960 galactic Cas Second-epoch detections are separated by 5.5" and 5.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:22:22.33 +56:30:16.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:22:22.33 +56:30:16.3: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:22:22.33 +56:30:16.3: 14.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 22 22.33 +56 30 16.3 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.27 23:16:09.77 +55:40:04.0
109.72039 -4.74091 galactic Cas Second-epoch detections are separated by 5.9" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:16:09.77 +55:40:04.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:16:09.77 +55:40:04.0: 15.36 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:16:09.77 +55:40:04.0: 14.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 16 09.77 +55 40 04.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8424,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3424 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3424 2461274.8424 14.28 23:21:02.11 +55:24:46.2
110.27783 -5.22217 galactic Cas Second-epoch detections are separated by 8.9" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1996852586522455296 | 23:21:05.86 +55:24:27.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:02.11 +55:24:46.2: 15.52 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:02.11 +55:24:46.2: 14.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3424* 23 21 02.11 +55 24 46.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1996852586522455296,2461274.8424,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1996852586522455296 20260822.3424 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
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: 2461239.82421699 18.07.2026 07:46:42.348 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
First image: 2461239.82421699 18.07.2026 07:46:42.348 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Last image: 2461274.84265770 22.08.2026 08:13:15.625 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 23
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.76
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: 17 seconds
Number of parallel threads: 3
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
VAST_SKIP_INDEX_VS_MAG is set - skipping the lib/index_vs_mag variability-index fitting
Total objects detected (at least 2 times): 18227
Objects passed selection criteria: 18215
Measurements per detected object (mean, median, min, max): 3.5 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.5 4.0 2 4
Average stars detected per image: 18317.2
Average stars matched: 18122.5 (98.9368 %)
Memory usage VmPeak: 247796 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Aug 20 15:05:04 CDT 2026
VaST build number 1.0rc89-192-g23359006
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-08-20)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sat Aug 22 03:31:38 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: 2461239.82421699 18.07.2026 07:46:42.348 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
First image: 2461239.82421699 18.07.2026 07:46:42.348 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Last image: 2461274.84265770 22.08.2026 08:13:15.625 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 1189
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.56
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: 224 seconds
Number of parallel threads: 3
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
VAST_SKIP_INDEX_VS_MAG is set - skipping the lib/index_vs_mag variability-index fitting
Total objects detected (at least 2 times): 137731
Objects passed selection criteria: 137505
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: 130064
Average stars matched: 124976 (96.0873 %)
Memory usage VmPeak: 583716 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Thu Aug 20 15:05:04 CDT 2026
VaST build number 1.0rc89-192-g23359006
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-08-20)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sat Aug 22 03:44:18 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 --noflagimage --starmatchraius 5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.cat to cache
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Checking WCS cache directory local_wcs_cache
Checking WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Found WCS cache directory /mnt/usb/NMW_NG/solved_reference_images
Checking WCS cache directory /home/NMW_web_upload/solved_reference_images
Checking WCS cache directory /dataX/kirx/NMW_NG_rt3_autumn2019/solved_reference_images
The reference JD(UT) for computing planet and comet positions: 2461274.84208006
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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits exists and is non-empty
wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits exists and is non-empty
wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits exists and is non-empty
wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits exists and is non-empty
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits (1st reference image)
verification OK: wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Image size: 941.2'x626.6' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:01.062 +54:00:02.05 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Image size: 926.5'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 00:00:00.203 +54:01:59.36 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.062 +54:00:02.05
Second-epoch image center 00:00:00.203 +54:01:59.36
Angular distance between the image centers 0.0327 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-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Image size: 926.5'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:57.205 +54:01:35.74 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.062 +54:00:02.05
Second-epoch image center 23:59:57.205 +54:01:35.74
Angular distance between the image centers 0.0277 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 00:00:00.203 +54:01:59.36
Second-epoch second image center 23:59:57.205 +54:01:35.74
Angular distance between the image centers 0.00984 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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits &> /tmp/tmp.hnbDG7ye7G
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits &> /tmp/tmp.Z2ij9DCCUQ
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits &> /tmp/tmp.jKHXaty7Ri
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits &> /tmp/tmp.mFEIfVHx91
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits and wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits and wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat
Found non-empty wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits and wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat
The reference image (wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits) and catalog (wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat) found
'wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat' -> 'wcsmag.cat'
The field straddles RA=0: the RA boundaries wrap around (min > max)
Read 33669 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 345.3600 to 15.3869 deg, Dec +47.7769 to +59.3470 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 345.3600 to 15.3869 deg, Dec 47.7769 to 59.3470 deg
Loaded 26243 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): 16959 out of 18283 total matches.
Matched with Tycho-2 18283 out of 33669 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.677900
a=0.000000 b=1.000000 c=22.677900
From vast_summary.log: estimated ref. image limiting mag.: -7.76
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.92
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.92
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
The field straddles RA=0: the RA boundaries wrap around (min > max)
Read 33669 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 345.3600 to 15.3869 deg, Dec +47.7769 to +59.3470 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 345.3600 to 15.3869 deg, Dec 47.7769 to 59.3470 deg
Loaded 26243 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): 16959 out of 18283 total matches.
Matched with Tycho-2 18283 out of 33669 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits:
Forced-photometry filter: reusing the VaST-run aperture from image00001.cat.aperture for wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits (aperture=7.3)
The field straddles RA=0: the RA boundaries wrap around (min > max)
Read 14903 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 344.8488 to 14.8386 deg, Dec +48.0248 to +59.2553 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 344.8488 to 14.8386 deg, Dec 48.0248 to 59.2553 deg
Loaded 25721 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): 11593 out of 12074 total matches.
Matched with Tycho-2 12074 out of 14903 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits:
Forced-photometry filter: reusing the VaST-run aperture from image00002.cat.aperture for wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits (aperture=6.2)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 19 candidate transients before the final filtering. (Hard limit: 10000)
Median FWHM seeing for isolated stars:
3.5 pix Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
2.3 pix Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
2.2 pix fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
2.2 pix fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Limiting magnitude estimates:
14.9 mag. Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
14.3 mag. Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
14.7 mag. fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
14.7 mag. fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
All-image limiting magnitude estimate: 14.7 (SNR ) 11.4 (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
cp: cannot create regular file 'local_wcs_cache/': Not a directory
############ /tmp/tmp.hnbDG7ye7G (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits' -> 'wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits'
This WCS solution (astrometrynet) will be kept as is, not refit by util/solve_plate_with_UCAC5
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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=2621, bad_region=6655, passed=33669
Got 33669 stars (including 24831 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat
util/solve_plate_with_UCAC5 got 33669 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.2'
Seting catalog search parameters based on the expected field of view 941.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013072 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010458 (37.6 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.3600 through 0 to 15.3869, gap 15.3869 to 345.3600
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.8 to 59.3)
Done reading UCAC5 zone files...
Matched 4938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 4904 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 28540 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.3592 through 0 to 15.3870, gap 15.3870 to 345.3592
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.8 to 59.3)
Done reading UCAC5 zone files...
Matched 4938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 28540 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 28540 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.41"
Excluding outliers - 4904 stars left (next iteration limit 5394)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
SIP_REFIT: util/identify.sh trusts the WCS of wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits (astrometrynet) - keeping it, no refit (set VAST_FORCE_SIP_REFIT=1 to refit anyway)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits N_match=4904 sigma_overall_arcsec=0.398 sigma_q1_arcsec=0.441 sigma_q2_arcsec=0.393 sigma_q3_arcsec=0.363 sigma_q4_arcsec=0.358 n_q1=1555 n_q2=802 n_q3=1643 n_q4=904 worst_quadrant_to_overall_ratio=1.108
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits -region wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.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.Z2ij9DCCUQ (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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits 571.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits' -> 'wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits'
This WCS solution (astrometrynet) will be kept as is, not refit by util/solve_plate_with_UCAC5
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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=1092, bad_region=2856, passed=14903
Got 14903 stars (including 11103 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat
util/solve_plate_with_UCAC5 got 14903 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 938.5'
Seting catalog search parameters based on the expected field of view 938.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013035 (46.9 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010428 (37.5 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.8488 through 0 to 14.8386, gap 14.8386 to 344.8488
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.0 to 59.3)
Done reading UCAC5 zone files...
Matched 4938 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 4904 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.46"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 4904 matched stars entering correct_measured_positions(), 12704 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.48"
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.8478 through 0 to 14.8387, gap 14.8387 to 344.8478
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.0 to 59.3)
Done reading UCAC5 zone files...
Matched 4937 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 4902 matched stars entering correct_measured_positions(), 12704 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.49"
Accuracy estimation diagnostic: 4902 matched stars entering correct_measured_positions(), 12704 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.51"
Excluding outliers - 4902 stars left (next iteration limit 5394)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
SIP_REFIT: util/identify.sh trusts the WCS of wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits (astrometrynet) - keeping it, no refit (set VAST_FORCE_SIP_REFIT=1 to refit anyway)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits N_match=4902 sigma_overall_arcsec=0.528 sigma_q1_arcsec=0.495 sigma_q2_arcsec=0.443 sigma_q3_arcsec=0.586 sigma_q4_arcsec=0.534 n_q1=1550 n_q2=795 n_q3=1659 n_q4=898 worst_quadrant_to_overall_ratio=1.109
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits -region wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.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.jKHXaty7Ri (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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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=1599, bad_region=4609, passed=21975
Got 21975 stars (including 15978 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat
util/solve_plate_with_UCAC5 got 21975 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.5'
Seting catalog search parameters based on the expected field of view 926.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012868 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010294 (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.1045 through 0 to 14.8803, gap 14.8803 to 345.1045
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3496 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2177 matched stars entering correct_measured_positions(), 2383 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.44"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2023 matched stars entering correct_measured_positions(), 18187 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.05"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.1067 through 0 to 14.8982, gap 14.8982 to 345.1067
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3597 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2445 matched stars entering correct_measured_positions(), 18187 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.23"
Accuracy estimation diagnostic: 2369 matched stars entering correct_measured_positions(), 18274 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.12"
Excluding outliers - 2369 stars left (next iteration limit 2225)
SIP_REFIT: SIP order 2 trial: matched=2369 robust_rms=26.566 arcsec worst_quadrant_rms=29.691 arcsec
SIP_REFIT: SIP order 3 trial: matched=2369 robust_rms=25.887 arcsec worst_quadrant_rms=30.289 arcsec
SIP_REFIT: SIP order 5 trial: matched=2369 robust_rms=23.740 arcsec worst_quadrant_rms=29.194 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2369 robust_rms_before=31.898 arcsec robust_rms_before_corrected=19.490 arcsec robust_rms_after=26.566 arcsec worst_quadrant_rms_before=24.228 worst_quadrant_rms_after=29.691
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.228 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits N_match=2369 sigma_overall_arcsec=13.988 sigma_q1_arcsec=28.268 sigma_q2_arcsec=27.648 sigma_q3_arcsec=7.618 sigma_q4_arcsec=5.455 n_q1=545 n_q2=266 n_q3=933 n_q4=625 worst_quadrant_to_overall_ratio=2.021
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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.mFEIfVHx91 (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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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=1581, bad_region=4583, passed=21827
Got 21827 stars (including 15886 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat
util/solve_plate_with_UCAC5 got 21827 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.5'
Seting catalog search parameters based on the expected field of view 926.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012868 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010294 (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.1048 through 0 to 14.8807, gap 14.8807 to 345.1048
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3495 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2153 matched stars entering correct_measured_positions(), 2367 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2003 matched stars entering correct_measured_positions(), 18062 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.13"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.1067 through 0 to 14.8987, gap 14.8987 to 345.1067
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3605 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2421 matched stars entering correct_measured_positions(), 18062 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.30"
Accuracy estimation diagnostic: 2358 matched stars entering correct_measured_positions(), 18145 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.24"
Excluding outliers - 2358 stars left (next iteration limit 2203)
SIP_REFIT: SIP order 2 trial: matched=2358 robust_rms=26.552 arcsec worst_quadrant_rms=29.181 arcsec
SIP_REFIT: SIP order 3 trial: matched=2358 robust_rms=25.878 arcsec worst_quadrant_rms=29.730 arcsec
SIP_REFIT: SIP order 5 trial: matched=2358 robust_rms=23.560 arcsec worst_quadrant_rms=29.188 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2358 robust_rms_before=32.180 arcsec robust_rms_before_corrected=19.613 arcsec robust_rms_after=26.552 arcsec worst_quadrant_rms_before=24.438 worst_quadrant_rms_after=29.181
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.438 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits N_match=2358 sigma_overall_arcsec=14.359 sigma_q1_arcsec=29.084 sigma_q2_arcsec=28.959 sigma_q3_arcsec=7.794 sigma_q4_arcsec=6.217 n_q1=540 n_q2=263 n_q3=925 n_q4=630 worst_quadrant_to_overall_ratio=2.026
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Saving the final (post-refit) wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits'
Saving the final (post-refit) wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits'
Saving the final (post-refit) wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits'
Saving the final (post-refit) wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits'
###################################
# Pre-local-correction WCS quality summary (see WCS_QUALITY_DIAG lines above)
ref1=Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits sigma_overall=0.398 worst_q_ratio=1.108
ref2=Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits sigma_overall=0.528 worst_q_ratio=1.109
new1=fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits sigma_overall=13.988 worst_q_ratio=2.021
new2=fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits sigma_overall=14.359 worst_q_ratio=2.026
reference average sigma_overall=0.463 worst_q_ratio=1.1085
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits) flagged: sigma=13.988 (ref avg 0.463), ratio=2.021 (ref avg 1.1085), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00003.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/lib/make_outxyls_for_astrometric_calibration found 21159 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Using the local copy of Astrometry.net code
IMAGE_SIZE= --width 9576 --height 6388 SCALE_LOW=544.5 SCALE_HIGH=3025.0
Using solve-field binary
/usr/local/astrometry/bin/solve-field
Reading input file 1 of 1: "out2176270.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2176270.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 22.9782 (9.53471e+09), 7 match, 0 conflict, 20 distractors, 26 index.
RA,Dec = (359.998,54.0315), pixel scale 5.92986 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----+----+-+-----+(best)-----+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2176270.solved to indicate this.
Field: out2176270.xyls
Field center: (RA,Dec) = (359.999447, 54.032343) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:59.867, +54:01:56.433).
Field size: 15.603 x 10.4303 degrees
Field rotation angle: up is 4.49538 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits' -> 'fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Aug 22 03:34 fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:34 out2176270.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits (fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits)
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration01' / astrometry.net run
Reading input file 1 of 1: "out2176270.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2176270.axy"...
Only searching for solutions within 15.4417 degrees of RA,Dec (0.000845833,54.0332)
log-odds ratio 22.9782 (9.53471e+09), 7 match, 0 conflict, 20 distractors, 26 index.
RA,Dec = (359.998,54.0315), pixel scale 5.92986 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----+----+-+-----+(best)-----+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2176270.solved to indicate this.
Field: out2176270.xyls
Field center: (RA,Dec) = (359.999447, 54.032343) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:59.867, +54:01:56.433).
Field size: 15.603 x 10.4303 degrees
Field rotation angle: up is 4.49538 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Aug 22 03:34 fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:34 out2176270.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
Image size: 926.5'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 00:00:00.203 +54:01:59.36 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 21975 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/correct_sextractor_wcs_catalog_usingxy2sky2179335.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.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=1599, bad_region=4609, passed=21975
Got 21975 stars (including 15978 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat
util/solve_plate_with_UCAC5 got 21975 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.5'
Seting catalog search parameters based on the expected field of view 926.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012868 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010294 (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.1045 through 0 to 14.8803, gap 14.8803 to 345.1045
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3496 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2177 matched stars entering correct_measured_positions(), 2383 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.44"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2023 matched stars entering correct_measured_positions(), 18187 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.05"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.1067 through 0 to 14.8982, gap 14.8982 to 345.1067
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3597 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2445 matched stars entering correct_measured_positions(), 18187 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.23"
Accuracy estimation diagnostic: 2369 matched stars entering correct_measured_positions(), 18274 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.12"
Excluding outliers - 2369 stars left (next iteration limit 2225)
SIP_REFIT: SIP order 2 trial: matched=2369 robust_rms=26.566 arcsec worst_quadrant_rms=29.691 arcsec
SIP_REFIT: SIP order 3 trial: matched=2369 robust_rms=25.887 arcsec worst_quadrant_rms=30.289 arcsec
SIP_REFIT: SIP order 5 trial: matched=2369 robust_rms=23.740 arcsec worst_quadrant_rms=29.194 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2369 robust_rms_before=31.898 arcsec robust_rms_before_corrected=19.490 arcsec robust_rms_after=26.566 arcsec worst_quadrant_rms_before=24.228 worst_quadrant_rms_after=29.691
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.228 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits N_match=2369 sigma_overall_arcsec=13.988 sigma_q1_arcsec=28.268 sigma_q2_arcsec=27.648 sigma_q3_arcsec=7.618 sigma_q4_arcsec=5.455 n_q1=545 n_q2=266 n_q3=933 n_q4=625 worst_quadrant_to_overall_ratio=2.021
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 1st new image (fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits): sigma 13.988->13.988, ratio 2.021->2.021; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits) flagged: sigma=14.359 (ref avg 0.463), ratio=2.026 (ref avg 1.1085), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00004.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/lib/make_outxyls_for_astrometric_calibration found 20980 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Using the local copy of Astrometry.net code
IMAGE_SIZE= --width 9576 --height 6388 SCALE_LOW=544.5 SCALE_HIGH=3025.0
Using solve-field binary
/usr/local/astrometry/bin/solve-field
Reading input file 1 of 1: "out2211856.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2211856.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 23.1117 (1.08963e+10), 7 match, 0 conflict, 20 distractors, 26 index.
RA,Dec = (359.986,54.025), pixel scale 5.92978 arcsec/pix.
Hit/miss: Hit/miss: ----+++------+----+-+-----+(best)-----+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2211856.solved to indicate this.
Field: out2211856.xyls
Field center: (RA,Dec) = (359.986956, 54.025782) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.870, +54:01:32.814).
Field size: 15.6025 x 10.43 degrees
Field rotation angle: up is 4.50776 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits' -> 'fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Aug 22 03:34 fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:34 out2211856.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits (fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits)
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration01' / astrometry.net run
Reading input file 1 of 1: "out2211856.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2211856.axy"...
Only searching for solutions within 15.4417 degrees of RA,Dec (359.988,54.0266)
log-odds ratio 23.1117 (1.08963e+10), 7 match, 0 conflict, 20 distractors, 26 index.
RA,Dec = (359.986,54.025), pixel scale 5.92978 arcsec/pix.
Hit/miss: Hit/miss: ----+++------+----+-+-----+(best)-----+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2211856.solved to indicate this.
Field: out2211856.xyls
Field center: (RA,Dec) = (359.986956, 54.025782) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.870, +54:01:32.814).
Field size: 15.6025 x 10.43 degrees
Field rotation angle: up is 4.50776 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Aug 22 03:34 fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:34 out2211856.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
Image size: 926.5'x616.2' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:57.205 +54:01:35.74 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 21827 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/correct_sextractor_wcs_catalog_usingxy2sky2228704.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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=1581, bad_region=4583, passed=21827
Got 21827 stars (including 15886 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat
util/solve_plate_with_UCAC5 got 21827 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.5'
Seting catalog search parameters based on the expected field of view 926.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012868 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010294 (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.1048 through 0 to 14.8807, gap 14.8807 to 345.1048
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3495 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2153 matched stars entering correct_measured_positions(), 2367 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2003 matched stars entering correct_measured_positions(), 18062 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.13"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.1067 through 0 to 14.8987, gap 14.8987 to 345.1067
UCAC5 local query limit 5000: matching up to 5000 detected stars, deepening the UCAC5 window to mag 15.50
Reading UCAC5 zone files...
Searching UCAC5 zones 690 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 3605 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2421 matched stars entering correct_measured_positions(), 18062 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.30"
Accuracy estimation diagnostic: 2358 matched stars entering correct_measured_positions(), 18145 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.24"
Excluding outliers - 2358 stars left (next iteration limit 2203)
SIP_REFIT: SIP order 2 trial: matched=2358 robust_rms=26.552 arcsec worst_quadrant_rms=29.181 arcsec
SIP_REFIT: SIP order 3 trial: matched=2358 robust_rms=25.878 arcsec worst_quadrant_rms=29.730 arcsec
SIP_REFIT: SIP order 5 trial: matched=2358 robust_rms=23.560 arcsec worst_quadrant_rms=29.188 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2358 robust_rms_before=32.180 arcsec robust_rms_before_corrected=19.613 arcsec robust_rms_after=26.552 arcsec worst_quadrant_rms_before=24.438 worst_quadrant_rms_after=29.181
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.438 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits N_match=2358 sigma_overall_arcsec=14.359 sigma_q1_arcsec=29.084 sigma_q2_arcsec=28.959 sigma_q3_arcsec=7.794 sigma_q4_arcsec=6.217 n_q1=540 n_q2=263 n_q3=925 n_q4=630 worst_quadrant_to_overall_ratio=2.026
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 2nd new image (fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits): sigma 14.359->14.359, ratio 2.026->2.026; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=13.988 -- 30.21x the reference average (0.463); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=14.359 -- 31.01x the reference average (0.463); plate solution may be of low accuracy
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246_astrometric_residuals.png (4904 matched stars from wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.36 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111_astrometric_residuals.png (4902 matched stars from wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.46 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072_astrometric_residuals.png (2369 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 12.19 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073_astrometric_residuals.png (2358 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 12.05 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-12-25_20.00sec_-0.00C_LIGHT_0072.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_032811_TTUQ2b1x1_1808477_b19AoV5H/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073.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-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:15.89 +55:34:27.5: 15.33 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:35.47 +50:44:04.8: 15.50 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:57:13.91 +56:40:57.3: 11.89 +/- 0.04 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:24:00.53 +54:33:47.5: 15.32 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:45:25.38 +54:19:00.2: 15.57 +/- 0.36 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:32:00.25 +56:21:47.8: 11.19 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:35:00.69 +50:11:06.2: 15.43 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:42.62 +50:06:35.8: 15.33 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:12:46.71 +57:12:52.3: 11.19 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:21:42.62 +50:06:35.8: 14.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:00.69 +50:11:06.2: 14.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:45:25.38 +54:19:00.2: 14.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:32:00.25 +56:21:47.8: 99.00 +/- 99.00 bad_region
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:24:00.53 +54:33:47.5: 14.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:35.47 +50:44:04.8: 14.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:35:15.89 +55:34:27.5: 14.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:49.03 +57:32:30.9: 12.73 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:57:13.91 +56:40:57.3: 12.03 +/- 0.04 detection
Forced photometry reference-image weighted average: 15.57 +/- 0.36
Forced photometry reference-image weighted average: 11.19 +/- 0.01
Forced photometry filter KEPT candidate at 23:45:25.38 +54:19:00.2: ref_mag=15.57 +/- 0.36 new_mean_mag=11.6375 delta=3.93 (need > 0.90)
Forced photometry filter REJECTED candidate at 00:32:00.25 +56:21:47.8: ref_mag=11.19 +/- 0.01 new_mean_mag=11.4368 delta=-0.25 (need > 0.90)
Forced photometry reference-image weighted average: 11.94 +/- 0.03
Forced photometry filter REJECTED candidate at 23:57:13.91 +56:40:57.3: ref_mag=11.94 +/- 0.03 new_mean_mag=12.0086 delta=-0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:46.71 +57:12:52.3: 11.24 +/- 0.01 detection
Forced photometry reference-image weighted average: 11.20 +/- 0.01
Forced photometry filter REJECTED candidate at 00:12:46.71 +57:12:52.3: ref_mag=11.20 +/- 0.01 new_mean_mag=11.2717 delta=-0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:15:49.03 +57:32:30.9: 12.93 +/- 0.06 detection
Forced photometry reference-image weighted average: 12.77 +/- 0.03
Forced photometry filter KEPT candidate at 00:15:49.03 +57:32:30.9: ref_mag=12.77 +/- 0.03 new_mean_mag=11.3268 delta=1.44 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:07.62 +51:20:28.5: 14.16 +/- 0.10 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:00.49 +53:35:32.6: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:00:07.62 +51:20:28.5: 14.87 +/- 0.35 detection
Forced photometry reference-image weighted average: 14.21 +/- 0.09
Forced photometry filter KEPT candidate at 00:00:07.62 +51:20:28.5: ref_mag=14.21 +/- 0.09 new_mean_mag=11.6456 delta=2.57 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:15:00.49 +53:35:32.6: 14.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:42:06.38 +56:34:38.5: 11.96 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:42:06.38 +56:34:38.5: 12.06 +/- 0.03 detection
Forced photometry reference-image weighted average: 11.98 +/- 0.01
Forced photometry filter REJECTED candidate at 23:42:06.38 +56:34:38.5: ref_mag=11.98 +/- 0.01 new_mean_mag=12.1357 delta=-0.15 (need > 0.90)
Adding exclusion_list_local.txt__out50510.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50511.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50512.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50516.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50525.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50548.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50559.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50569.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50609.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 363s
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: 8s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50511_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50511_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50512_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50512_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50523_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50523_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50525_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50525_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50530_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50530_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50533_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50533_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50548_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50548_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50556_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50556_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50558_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50558_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50559_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50559_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50560_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50560_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (27.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50569_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50569_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50571_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50571_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:28:56.34 +57:11:34.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 50609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50665_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50665_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50682_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 50682_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190447_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190447_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190457_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190457_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190458_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190458_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190459_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190459_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190467_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190467_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190469_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190469_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190473_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190473_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190474_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190474_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190484_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190484_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190490_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190490_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190491_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190491_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190494_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190494_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190496_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190496_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190501_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190501_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190504_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190504_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190505_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190505_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190512_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190512_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190513_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190513_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190517_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190517_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190518_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190518_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190527_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190527_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190529_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190529_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190539_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190539_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190540_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190540_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190544_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190544_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190548_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190548_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (26.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190551_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190551_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190552_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190552_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190553_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190553_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190561_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190561_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190566_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190566_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190568_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190568_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190575_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190575_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190576_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190576_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190579_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190579_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190581_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190581_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190583_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190583_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190584_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190584_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:48:09.78 +55:32:25.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190585_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190585_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190593_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190593_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190603_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190603_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190605_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190605_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190606_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190606_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190608_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190608_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190610_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190610_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190614_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190614_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190617_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190617_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190618_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190618_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190623_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190623_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190624_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190624_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190626_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190626_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190628_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190628_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190629_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190629_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190633_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190633_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (35.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190638_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190638_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190639_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190639_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190641_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190641_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190644_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190644_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190646_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190646_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190650_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190650_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190655_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190655_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190657_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190657_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190658_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190658_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190659_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190659_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190660_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190660_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190666_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190666_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190668_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190668_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190674_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190674_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190676_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190676_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190677_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190677_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (34.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190680_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190680_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190682_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190682_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190694_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190694_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190697_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190697_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (30.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190698_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190698_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190707_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190707_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190711_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190711_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190715_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190715_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190716_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190716_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190718_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190718_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190719_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190719_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190722_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190722_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190724_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190724_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190726_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190726_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190728_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190728_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190731_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190731_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (31.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190733_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190733_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190735_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190735_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190737_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190737_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190739_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190739_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190745_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190745_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190746_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190746_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190749_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190749_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190753_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190753_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190755_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190755_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190759_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190759_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190762_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190762_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190766_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190766_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190768_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190768_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (32.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190769_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190769_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190770_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190770_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190771_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190771_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190772_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190772_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190774_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190774_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190775_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190775_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190778_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190778_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190780_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190780_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190781_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190781_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190783_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190783_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190784_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190784_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190785_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190785_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190790_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190790_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190795_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190795_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190797_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190797_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190800_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190800_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190801_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190801_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190806_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190806_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190808_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190808_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190814_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190814_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190817_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190817_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190823_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190823_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190824_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190824_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190825_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190825_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190832_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190832_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190833_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190833_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190835_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190835_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190836_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190836_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190837_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190837_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190838_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190838_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190839_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190839_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190843_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190843_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190846_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190846_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190848_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190848_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190849_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190849_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190851_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190851_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190852_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190852_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190856_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190856_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190857_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190857_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190858_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190858_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190861_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190861_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190862_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190862_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190869_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190869_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190870_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190870_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190871_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190871_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190874_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190874_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190876_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190876_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190879_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190879_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190880_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190880_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190882_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190882_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190887_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190887_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190893_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190893_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190900_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190900_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190901_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190901_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190905_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190905_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:28:42.25 +56:52:32.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190906_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190906_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190909_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190909_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190912_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190912_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190922_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190922_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190924_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190924_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190928_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190928_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190930_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190930_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190932_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190932_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190933_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190933_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190934_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190934_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190936_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190936_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190938_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190938_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190941_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190941_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190946_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190946_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190951_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190951_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190957_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190957_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190958_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190958_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190959_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190959_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190961_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190961_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190968_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190968_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190969_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190969_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190971_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190971_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190972_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190972_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190973_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190973_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190974_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190974_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190975_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190975_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190978_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190978_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190980_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190980_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190984_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190984_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190987_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190987_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190990_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190990_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190991_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190991_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 190992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190994_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190994_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190995_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190995_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190997_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 190997_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191001_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191001_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191004_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191004_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191005_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191005_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191006_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191006_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:47:23.99 +57:55:30.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191007_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191007_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191008_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191008_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191011_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191011_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191012_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191012_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191013_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191013_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191014_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191014_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191017_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191017_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191020_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191020_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191026_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191026_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191031_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191031_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191034_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191034_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191039_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191039_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191040_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191040_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191042_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191042_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191044_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191044_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191047_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191047_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:53:56.46 +56:03:15.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191049_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191049_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191052_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191052_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191054_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191054_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191055_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191055_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191057_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191057_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191058_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191058_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191059_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191059_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191061_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191061_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191062_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191062_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191063_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191063_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191065_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191065_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191069_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191069_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (30.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191070_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191070_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191074_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191074_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191075_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191075_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191076_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191076_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191078_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191078_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191079_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191079_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191080_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191080_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191085_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191085_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191086_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191086_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191089_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191089_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191092_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191092_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191093_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191093_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191096_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191096_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191097_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191097_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191099_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191099_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191103_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191103_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191104_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191104_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191108_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191108_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191114_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191114_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191115_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191115_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191117_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191117_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191120_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191120_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191123_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191123_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191125_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191125_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191126_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191126_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191129_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191129_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191130_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191130_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191133_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191133_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191136_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191136_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191137_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191137_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191138_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191138_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191139_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191139_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191140_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191140_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191142_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191142_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191143_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191143_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191144_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191144_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (28.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191145_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191145_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191146_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191146_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191150_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191150_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191151_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191151_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191155_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191155_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191157_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191157_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191159_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191159_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191161_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191161_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191162_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191162_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191163_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191163_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191169_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191169_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191170_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191170_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191171_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191171_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191172_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191172_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191174_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191174_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191179_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191179_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191180_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191180_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191184_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191184_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191185_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191185_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191189_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191189_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191190_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191190_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191191_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191191_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191192_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191192_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191194_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191194_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191196_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191196_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191197_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191197_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191199_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191199_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191200_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191200_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191201_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191201_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191203_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191203_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191205_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191205_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191212_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191212_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191213_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191213_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191215_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191215_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191219_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191219_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191220_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191220_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191221_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191221_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191222_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191222_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:21:58.92 +57:17:44.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191223_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191223_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191225_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191225_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191226_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191226_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191230_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191230_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191235_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191235_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191236_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191236_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191239_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191239_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191242_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191242_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191243_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191243_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (35.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191244_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191244_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191245_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191245_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191246_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191246_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191247_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191247_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191248_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191248_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191250_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191250_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191251_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191251_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191255_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191255_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191257_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191257_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191259_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191259_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191262_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191262_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191263_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191263_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191264_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191264_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191265_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191265_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191266_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191266_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191268_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191268_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191269_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191269_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191271_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191271_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191274_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191274_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191275_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191275_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191277_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191277_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191279_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191279_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191280_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191280_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191281_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191281_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191282_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191282_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191283_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191283_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191287_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191287_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191288_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191288_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191289_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191289_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191290_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191290_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191291_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191291_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191293_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191293_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191295_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191295_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191297_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191297_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191298_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191298_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191301_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191301_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191302_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191302_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191304_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191304_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191305_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191305_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191308_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191308_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191309_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191309_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191311_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191311_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191312_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191312_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191313_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191313_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191314_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191314_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191316_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191316_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191323_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191323_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191325_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191325_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191328_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191328_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191331_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191331_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191332_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191332_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191333_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191333_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191334_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191334_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191335_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191335_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191338_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191338_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191339_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191339_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191341_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191341_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:48:57.00 +56:40:25.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191342_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191342_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191350_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191350_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191351_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191351_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191353_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191353_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191360_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191360_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191362_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191362_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191368_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191368_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191371_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191371_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191373_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191373_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191375_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191375_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191376_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191376_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191380_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191380_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191384_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191384_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191386_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191386_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191387_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191387_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191388_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191388_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191389_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191389_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191392_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191392_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191395_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191395_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (29.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191398_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191398_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191399_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191399_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191401_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191401_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191402_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191402_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191405_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191405_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191406_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191406_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191407_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191407_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191415_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191415_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:58:03.60 +57:13:08.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191417_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191417_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (33.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191419_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191419_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191420_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191420_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191421_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191421_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191424_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191424_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191428_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191428_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191433_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191433_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191446_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191446_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191447_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191447_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191449_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191449_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191451_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191451_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191452_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191452_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191453_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191453_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (34.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191455_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191455_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191456_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191456_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191459_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191459_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191461_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191461_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191470_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191470_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191473_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191473_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191474_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191474_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191477_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191477_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191478_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191478_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191481_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191481_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191491_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191491_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191498_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191498_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191499_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191499_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191504_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191504_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191505_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191505_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191506_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191506_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191509_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191509_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191513_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191513_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191514_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191514_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:54:57.55 +56:12:38.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191517_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191517_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191518_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191518_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191528_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191528_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (31.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191529_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191529_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191530_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191530_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191531_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191531_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191532_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191532_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191533_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191533_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191534_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191534_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191536_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191536_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191537_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191537_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191538_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191538_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191546_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191546_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191549_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191549_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191550_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191550_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191554_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191554_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191558_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191558_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191560_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191560_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191562_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191562_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191563_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191563_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191574_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191574_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191575_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191575_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191576_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191576_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191580_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191580_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191587_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191587_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191589_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191589_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191590_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191590_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191592_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191592_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191593_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191593_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191595_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191595_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191598_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191598_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191600_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191600_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191601_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191601_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:02:52.65 +55:52:24.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191602_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191602_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191604_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191604_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191607_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191607_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191609_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191618_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191618_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191623_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191623_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191629_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191629_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191630_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191630_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191631_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191631_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191669_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191669_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191687_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191687_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191704_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191704_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (47.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191716_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191716_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191744_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191744_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191758_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191758_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191760_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191760_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:42:24.97 +56:49:49.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191768_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191768_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191771_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191771_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191795_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191795_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191800_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191800_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191812_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191812_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191820_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191820_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191821_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191821_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191828_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191828_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191830_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191830_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191831_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191831_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191833_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191833_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191839_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191839_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191840_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191840_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191845_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191845_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191851_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191851_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191852_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191852_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191853_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191853_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191854_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191854_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191857_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191857_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191858_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191858_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (26.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191868_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191868_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191880_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191880_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191885_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191885_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191891_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191891_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191892_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191892_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191894_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191894_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191897_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191897_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191900_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191900_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191901_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191901_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191905_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191905_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191908_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191908_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191912_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191912_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191913_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191913_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191914_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191914_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191917_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191917_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191923_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191923_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191928_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191928_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191934_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191934_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191936_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191936_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191940_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191940_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191942_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191942_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191948_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191948_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191956_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191956_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191961_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191961_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191968_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191968_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191969_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191969_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191973_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191973_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191978_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191978_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191979_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191979_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:31:16.88 +57:14:10.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191981_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191981_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191988_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191988_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191991_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191991_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 191992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191993_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 191993_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192002_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192002_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192013_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192013_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192014_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192014_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192020_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192020_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192024_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192024_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192025_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192025_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192030_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192030_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192031_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192031_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192032_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192032_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192047_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192047_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (33.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192049_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192049_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192054_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192054_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192055_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192055_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192058_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192058_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192063_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192063_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192065_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192065_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192076_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192076_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192077_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192077_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192080_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192080_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192082_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192082_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192083_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192083_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (34.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192086_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192086_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192089_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192089_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:53:17.52 +57:48:15.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192092_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192092_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192100_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192100_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192101_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192101_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192102_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192102_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:41:10.55 +57:16:00.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192107_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192107_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192109_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192109_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192110_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192110_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192111_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192111_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192117_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192117_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192119_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192119_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192133_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192133_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192147_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192147_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192149_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192149_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192151_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192151_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192153_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192153_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192154_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192154_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192156_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192156_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192157_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192157_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192163_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192163_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:09:23.86 +58:04:10.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192181_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192181_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192183_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192183_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192192_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192192_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192193_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192193_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192194_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192194_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192200_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192200_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (29.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192202_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192202_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192205_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192205_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192209_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192209_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192210_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192210_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192211_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192211_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192214_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192214_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192220_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192220_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192222_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192222_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192224_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192224_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192226_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192226_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192228_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192228_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192229_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192229_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192232_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192232_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192235_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192235_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192250_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192250_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192257_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192257_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192265_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192265_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192266_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192266_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192271_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192271_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192272_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192272_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192281_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192281_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192285_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192285_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192286_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192286_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192300_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192300_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192309_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192309_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192315_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192315_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192320_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192320_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192332_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192332_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192333_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192333_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192340_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192340_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192343_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192343_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192348_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192348_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192351_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192351_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192356_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192356_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192361_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192361_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192367_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192367_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192369_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192369_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192389_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192389_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192398_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192398_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192400_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192400_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192420_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192420_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192425_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192425_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192429_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192429_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192435_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192435_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192438_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192438_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192441_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192441_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (31.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192442_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192442_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192469_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192469_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192475_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192475_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192478_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192478_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192492_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192493_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192495_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192495_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192497_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192497_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192506_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192506_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192510_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192511_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192511_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192515_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192516_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192520_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192520_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192521_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192524_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192524_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192531_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192531_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192536_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192536_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192541_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192541_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192543_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192543_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192545_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192545_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192546_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192546_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192565_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192565_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192570_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192570_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192571_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192571_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192594_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192594_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192612_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192612_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192633_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192633_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192639_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192639_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192647_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192647_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192651_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192651_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (31.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192656_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192656_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192659_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192659_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192670_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192670_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192672_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192672_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192674_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192674_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192676_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192676_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192681_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192681_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192684_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192684_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192686_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192686_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192690_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192690_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192691_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192699_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192699_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192700_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192700_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192701_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192701_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192706_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192709_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192709_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192710_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192710_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192712_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192712_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192714_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192714_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192715_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192715_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192720_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192720_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192721_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192721_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192725_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192725_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192732_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192732_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192733_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192733_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192734_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192734_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192738_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192738_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (40.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192739_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192739_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192740_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192740_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192742_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192742_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192747_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192747_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192749_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192749_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192758_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192758_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192759_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192759_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (30.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192765_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192765_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192772_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192772_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192774_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192774_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192779_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192779_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192780_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192780_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192786_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192786_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192788_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192788_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192797_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192797_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192806_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192806_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192810_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192810_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192812_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192812_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192815_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192815_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192826_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192826_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192829_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192829_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192837_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192837_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192838_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192838_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192844_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192844_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192846_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192846_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192847_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192848_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192848_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192849_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192849_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192850_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192850_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192853_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192853_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192856_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192856_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192861_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192861_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192863_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192863_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192864_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192864_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192866_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192866_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192871_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192871_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192879_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192879_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192882_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192882_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192890_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192890_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192893_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192893_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192896_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192896_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192899_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192906_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192906_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (32.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192908_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192908_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192909_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192909_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192916_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192916_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192918_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192918_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192920_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192920_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192925_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192925_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192932_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192932_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192938_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192938_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192941_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192941_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192942_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192942_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192946_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192946_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192947_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192947_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192949_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192949_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192955_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192955_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192957_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192957_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192963_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192963_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192966_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192966_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192967_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192967_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192971_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192971_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192972_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192972_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192980_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192980_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192982_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 192982_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192986_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192989_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 192992_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193003_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193003_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193006_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193006_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193015_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193015_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193018_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193018_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193023_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193023_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193024_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193024_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193027_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193027_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193034_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193034_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193035_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193035_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193036_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193039_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193039_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193042_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193042_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193043_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193043_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193046_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193046_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193050_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193050_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193057_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193057_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193064_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193067_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193067_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193071_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193071_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193078_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193078_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193082_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193082_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193083_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193083_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193091_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193093_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193093_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193095_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193100_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193100_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193106_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193106_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (27.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193108_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193108_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (27.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193113_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193113_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193116_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193121_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193121_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193127_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193127_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193128_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193128_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193132_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193132_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193134_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193138_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193138_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193143_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193143_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193144_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193144_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193145_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193145_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193148_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193148_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193149_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193149_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193150_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193150_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193153_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193153_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193159_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193159_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193160_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193160_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193162_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193162_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193164_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193164_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193167_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193167_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193169_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193169_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193172_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193172_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193176_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193176_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193179_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193179_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193183_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193183_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193187_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193187_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193191_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193191_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193197_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193197_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (36.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193199_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193199_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193204_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193204_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193207_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193207_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193221_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193221_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193231_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193231_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193236_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193236_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193237_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193241_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193243_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193243_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193247_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193247_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193249_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193249_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193256_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193256_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193259_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193259_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193264_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193264_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193269_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193269_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193270_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193270_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193274_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193274_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193275_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193275_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193278_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193278_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193280_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193280_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193289_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193289_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193296_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193296_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193298_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193298_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193300_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193300_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193312_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193312_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193326_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193335_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193335_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193339_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193339_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193346_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193346_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193353_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193353_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193358_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193358_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193361_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193361_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193370_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193370_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193371_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
Preparing report for the candidate 193371_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193384_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193384_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193393_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193393_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193408_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193408_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193422_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193422_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193423_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193423_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193455_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193455_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 193465_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 75591_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 140319_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170697_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 170697_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 00:15:50.30 +57:32:36.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 16337_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 16337_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
**** FOUND 23:21:42.50 +50:06:34.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32090_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073
The candidate 32090_fd_Cas-04-Q2b1x1_2026-08-22_03-13-15_20.00sec_-0.00C_LIGHT_0073 did not pass the final checks
Rejecting candidate due to large distance (41.6") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 18s
make_report_in_HTML.sh TOTAL: 5536s
Prepared the HTML report for the field Cas-04-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
23:35:00.69 +50:11:06.2
23:24:00.53 +54:33:47.5
23:34:35.47 +50:44:04.8
23:35:15.89 +55:34:27.5
23:45:25.38 +54:19:00.2
23:21:42.62 +50:06:35.8
00:15:49.03 +57:32:30.9
00:00:07.62 +51:20:28.5
00:15:00.49 +53:35:32.6
23:16:18.05 +55:26:09.5
00:23:16.42 +54:07:27.3
23:34:55.40 +53:37:35.0
23:24:46.04 +55:53:02.9
00:15:37.89 +51:47:05.9
23:37:30.27 +55:27:05.5
23:35:59.38 +55:24:07.8
23:52:24.98 +54:32:28.7
23:39:02.44 +55:35:25.1
23:17:57.18 +52:26:57.5
23:52:13.43 +52:40:04.3
23:42:54.02 +55:43:45.1
23:44:13.88 +53:16:51.4
23:23:13.88 +51:43:24.6
00:10:03.65 +55:10:39.2
23:47:10.97 +53:39:21.8
23:28:39.25 +53:12:34.2
00:01:43.90 +50:08:50.6
23:34:24.21 +52:49:52.3
00:14:51.47 +52:19:01.5
23:28:01.74 +55:38:43.8
23:46:01.99 +54:36:45.9
00:13:12.44 +52:24:26.5
00:12:11.75 +51:44:24.0
23:30:06.75 +51:01:46.3
00:00:05.85 +52:33:48.4
00:04:07.44 +51:25:23.5
23:26:07.11 +55:38:15.0
23:43:41.94 +52:00:43.3
23:27:50.92 +50:26:22.3
23:32:56.79 +53:38:43.0
23:37:40.52 +55:28:55.3
23:26:23.17 +55:21:03.6
00:07:27.59 +50:53:52.0
23:53:53.89 +53:23:45.0
23:37:29.90 +56:31:52.9
23:27:51.87 +57:08:15.5
00:06:13.32 +51:56:53.9
23:27:42.19 +53:31:02.2
23:17:13.79 +56:28:28.8
23:17:10.26 +55:35:40.3
23:39:36.71 +51:31:08.8
23:25:28.75 +54:50:22.6
23:43:34.82 +55:18:55.4
23:34:09.42 +55:46:32.9
23:34:58.59 +55:47:45.8
23:13:50.99 +55:57:40.5
23:22:19.17 +54:46:36.1
00:03:16.36 +54:09:44.4
23:10:42.41 +56:27:19.9
23:41:20.97 +51:48:13.8
23:11:21.01 +56:24:12.1
23:47:58.44 +52:38:59.4
23:17:18.61 +56:04:22.4
23:42:19.10 +55:47:52.7
23:33:47.93 +57:28:40.7
23:23:47.98 +53:18:18.0
23:44:26.33 +52:09:01.8
00:20:22.17 +51:49:02.5
23:26:04.73 +54:30:25.1
00:28:12.68 +54:30:52.4
23:23:13.03 +56:57:57.2
00:05:25.40 +52:54:34.1
23:33:51.73 +56:19:28.0
23:17:49.59 +51:39:57.4
23:14:00.65 +56:16:06.4
23:22:22.22 +51:21:59.3
00:30:57.41 +55:56:16.0
23:54:47.01 +49:59:46.1
23:15:31.82 +55:29:12.1
23:17:33.22 +56:09:22.6
23:29:09.84 +53:28:15.7
23:22:50.81 +51:55:37.3
23:14:39.08 +54:01:55.6
23:22:41.52 +50:08:52.2
00:10:41.97 +53:58:59.1
23:40:56.31 +56:21:53.4
23:52:43.95 +51:16:51.2
23:14:43.69 +55:59:17.7
23:27:03.30 +51:35:13.2
23:17:24.25 +53:56:33.4
23:21:31.46 +51:34:43.2
00:00:45.69 +52:08:01.9
23:27:04.54 +55:04:53.9
23:36:50.41 +55:44:36.5
23:14:10.81 +56:23:41.4
23:48:03.18 +49:59:47.6
23:52:37.41 +53:51:42.7
23:17:19.86 +55:48:34.8
23:21:37.01 +52:40:18.1
23:24:53.44 +51:36:44.3
23:41:49.02 +54:48:54.3
23:38:15.07 +53:10:00.6
23:15:34.86 +53:05:16.0
23:16:49.50 +56:44:36.6
23:55:32.65 +51:24:49.0
00:08:06.08 +51:46:32.5
23:20:42.93 +52:15:32.8
23:23:13.51 +55:06:38.9
23:18:01.86 +52:26:53.8
00:13:02.05 +53:50:13.4
23:26:51.69 +50:21:04.8
23:30:42.17 +51:38:08.2
23:33:46.95 +50:32:48.2
23:16:54.50 +55:48:01.6
23:19:09.98 +54:34:48.6
00:07:25.85 +52:06:06.5
23:28:15.83 +51:28:50.6
23:57:17.16 +54:23:56.1
23:39:31.96 +55:38:14.2
23:21:30.79 +50:33:07.4
23:57:57.45 +50:00:30.2
00:26:01.52 +49:49:08.2
23:24:06.39 +51:31:42.6
23:28:10.10 +53:34:41.6
00:09:04.02 +51:44:06.9
23:41:48.33 +51:06:34.3
00:10:11.06 +50:58:29.6
23:37:51.56 +55:18:45.1
23:41:14.11 +49:49:14.1
23:24:41.18 +50:40:04.3
00:16:43.69 +55:04:48.4
23:48:14.88 +49:50:27.4
00:16:58.68 +49:56:54.5
23:30:42.23 +58:00:32.4
23:17:20.32 +56:42:33.0
23:21:56.72 +51:25:13.0
23:21:22.07 +54:59:40.4
23:14:32.81 +57:06:02.1
00:05:32.26 +50:54:27.7
23:41:27.83 +55:38:04.4
00:29:14.27 +55:53:35.5
23:25:30.20 +56:41:11.7
23:27:35.60 +56:31:40.6
00:05:57.46 +52:01:29.6
00:13:15.18 +52:31:09.5
23:25:51.42 +52:56:18.2
00:25:38.30 +51:57:33.1
23:56:49.66 +50:03:02.6
23:22:06.89 +49:53:01.4
23:39:45.94 +51:01:25.7
23:53:42.64 +50:58:18.9
23:12:00.81 +56:27:21.2
00:07:16.61 +51:00:10.5
23:32:12.89 +57:11:42.5
23:21:09.71 +55:54:03.5
23:11:34.56 +56:00:12.8
00:23:21.01 +54:55:48.6
23:27:19.37 +56:40:17.5
23:12:59.22 +56:18:49.4
23:13:28.29 +56:57:07.3
00:24:45.52 +53:56:01.6
23:33:19.98 +56:17:51.8
23:17:13.98 +56:09:06.8
00:26:57.25 +51:56:51.5
00:11:25.43 +51:27:58.5
23:37:00.76 +55:33:52.6
23:43:57.52 +50:48:28.8
00:12:47.37 +49:45:30.1
23:48:48.78 +49:47:32.0
23:23:37.91 +52:10:26.6
23:32:50.17 +51:17:32.7
23:19:26.43 +55:24:32.2
00:30:44.10 +55:16:19.3
00:08:01.33 +52:54:48.5
23:18:15.39 +54:05:47.9
23:48:50.93 +52:53:26.7
23:18:00.09 +54:03:30.8
00:24:54.29 +53:42:17.4
23:57:04.14 +52:12:07.1
00:05:13.84 +51:50:45.1
23:24:14.45 +53:00:33.2
23:21:43.60 +55:58:25.2
23:30:29.36 +54:34:20.5
00:27:11.98 +54:05:42.0
00:05:10.94 +52:08:57.8
00:27:35.95 +51:54:37.9
00:18:16.28 +50:20:06.5
00:14:55.85 +52:36:26.6
00:07:14.12 +54:10:58.2
23:53:56.57 +50:54:38.7
00:09:57.80 +50:50:42.4
23:36:32.93 +49:50:56.6
00:03:48.58 +53:38:54.6
23:34:35.33 +52:37:11.9
23:30:12.41 +50:50:41.1
23:51:21.35 +49:51:40.4
23:19:19.45 +51:15:48.0
23:26:40.69 +52:55:03.1
23:14:03.80 +55:28:47.7
23:31:43.27 +51:03:17.0
00:07:47.15 +53:00:29.4
23:23:22.60 +51:40:38.1
23:55:21.24 +50:40:11.1
23:27:00.19 +54:16:26.7
23:34:14.12 +55:20:17.7
23:22:05.80 +53:17:47.3
23:13:13.49 +55:44:24.7
23:42:14.10 +53:08:23.2
23:40:46.26 +52:40:44.0
23:53:13.59 +50:51:15.3
23:30:30.78 +54:53:17.5
00:14:11.97 +51:14:39.1
23:17:56.32 +56:24:57.6
23:55:59.11 +52:04:39.5
23:36:21.73 +55:45:35.0
00:12:55.73 +51:32:02.4
23:17:45.15 +56:02:14.3
23:16:26.86 +55:52:30.9
23:55:40.56 +51:20:10.9
23:21:29.90 +53:08:53.6
23:34:13.01 +49:48:44.1
23:26:59.06 +52:45:09.1
23:20:52.72 +50:30:19.5
00:07:39.23 +50:26:56.5
00:13:00.67 +50:20:20.4
23:32:56.10 +50:39:59.2
23:17:33.59 +53:46:10.8
23:43:52.54 +51:14:18.6
23:49:20.50 +51:33:06.1
23:14:47.90 +57:31:28.9
23:21:51.60 +51:29:52.1
23:37:19.73 +55:38:16.1
23:32:22.09 +56:20:28.9
23:41:00.07 +52:48:21.7
23:32:59.80 +52:10:47.4
00:12:03.51 +57:04:15.6
23:24:23.16 +56:09:52.8
23:27:07.81 +50:41:41.7
23:27:35.41 +51:17:51.6
23:19:28.03 +49:32:04.5
23:23:20.83 +49:55:24.5
23:43:04.50 +51:10:43.8
00:13:09.78 +52:52:03.0
00:16:34.97 +51:26:36.1
23:26:55.30 +56:27:00.1
23:24:57.18 +56:11:24.6
00:13:03.03 +53:57:49.5
23:23:01.87 +49:50:17.6
23:15:49.86 +56:17:11.3
23:14:25.17 +56:23:21.9
23:18:33.24 +51:55:27.1
00:11:43.58 +53:03:48.3
00:23:47.71 +50:48:32.2
00:00:54.74 +50:41:25.2
23:31:21.08 +52:54:30.6
00:09:12.86 +53:00:00.4
23:43:04.70 +54:54:23.7
23:17:32.12 +55:39:03.6
23:17:22.54 +55:37:27.5
00:28:58.98 +53:42:04.1
00:01:26.42 +50:22:03.1
00:00:45.69 +51:03:39.9
23:30:56.17 +51:13:56.1
23:14:43.92 +53:06:03.5
23:21:55.22 +51:05:36.7
23:25:01.13 +56:45:07.0
23:37:56.15 +56:26:08.7
23:17:36.19 +50:30:27.5
23:33:43.67 +53:53:45.8
23:52:18.79 +50:33:05.4
23:34:13.53 +56:18:06.3
23:12:27.57 +56:09:43.7
23:48:21.25 +51:56:48.5
23:51:33.28 +50:53:06.4
23:22:24.22 +49:39:45.1
23:13:59.58 +56:34:36.6
23:22:05.22 +50:07:46.4
23:43:49.10 +49:48:53.3
00:11:32.61 +50:42:08.2
23:54:21.46 +50:47:55.7
23:38:10.23 +50:41:38.0
23:35:11.46 +51:47:21.8
23:56:55.48 +51:01:06.4
23:31:26.83 +50:23:06.7
23:25:12.43 +54:01:44.9
23:45:35.78 +54:51:42.9
23:44:13.10 +51:12:16.7
23:19:24.43 +56:40:31.3
23:52:42.36 +51:25:47.3
23:49:17.43 +52:48:58.4
23:28:45.64 +52:34:31.8
00:14:22.10 +52:18:11.0
23:14:00.70 +56:27:36.2
00:02:01.35 +52:54:05.5
23:25:23.20 +54:25:11.6
23:15:17.88 +54:16:36.7
23:36:06.17 +55:53:50.2
23:25:37.03 +56:43:28.1
00:24:26.44 +54:50:32.6
23:22:22.33 +56:30:16.3
23:16:09.77 +55:40:04.0
23:21:02.11 +55:24:46.2
########### 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:35:00.69 +50:11:06.2
23:24:00.53 +54:33:47.5
23:34:35.47 +50:44:04.8
23:35:15.89 +55:34:27.5
23:45:25.38 +54:19:00.2
23:21:42.62 +50:06:35.8
00:15:49.03 +57:32:30.9
00:00:07.62 +51:20:28.5
00:15:00.49 +53:35:32.6
23:16:18.05 +55:26:09.5
00:23:16.42 +54:07:27.3
23:34:55.40 +53:37:35.0
23:24:46.04 +55:53:02.9
00:15:37.89 +51:47:05.9
23:37:30.27 +55:27:05.5
23:35:59.38 +55:24:07.8
23:52:24.98 +54:32:28.7
23:39:02.44 +55:35:25.1
23:17:57.18 +52:26:57.5
23:52:13.43 +52:40:04.3
23:42:54.02 +55:43:45.1
23:44:13.88 +53:16:51.4
23:23:13.88 +51:43:24.6
00:10:03.65 +55:10:39.2
23:47:10.97 +53:39:21.8
23:28:39.25 +53:12:34.2
00:01:43.90 +50:08:50.6
23:34:24.21 +52:49:52.3
00:14:51.47 +52:19:01.5
23:28:01.74 +55:38:43.8
23:46:01.99 +54:36:45.9
00:13:12.44 +52:24:26.5
00:12:11.75 +51:44:24.0
23:30:06.75 +51:01:46.3
00:00:05.85 +52:33:48.4
00:04:07.44 +51:25:23.5
23:26:07.11 +55:38:15.0
23:43:41.94 +52:00:43.3
23:27:50.92 +50:26:22.3
23:32:56.79 +53:38:43.0
23:37:40.52 +55:28:55.3
23:26:23.17 +55:21:03.6
00:07:27.59 +50:53:52.0
23:53:53.89 +53:23:45.0
23:37:29.90 +56:31:52.9
23:27:51.87 +57:08:15.5
00:06:13.32 +51:56:53.9
23:27:42.19 +53:31:02.2
23:17:13.79 +56:28:28.8
23:17:10.26 +55:35:40.3
23:39:36.71 +51:31:08.8
23:25:28.75 +54:50:22.6
23:43:34.82 +55:18:55.4
23:34:09.42 +55:46:32.9
23:34:58.59 +55:47:45.8
23:13:50.99 +55:57:40.5
23:22:19.17 +54:46:36.1
00:03:16.36 +54:09:44.4
23:10:42.41 +56:27:19.9
23:41:20.97 +51:48:13.8
23:11:21.01 +56:24:12.1
23:47:58.44 +52:38:59.4
23:17:18.61 +56:04:22.4
23:42:19.10 +55:47:52.7
23:33:47.93 +57:28:40.7
23:23:47.98 +53:18:18.0
23:44:26.33 +52:09:01.8
00:20:22.17 +51:49:02.5
23:26:04.73 +54:30:25.1
00:28:12.68 +54:30:52.4
23:23:13.03 +56:57:57.2
00:05:25.40 +52:54:34.1
23:33:51.73 +56:19:28.0
23:17:49.59 +51:39:57.4
23:14:00.65 +56:16:06.4
23:22:22.22 +51:21:59.3
00:30:57.41 +55:56:16.0
23:54:47.01 +49:59:46.1
23:15:31.82 +55:29:12.1
23:17:33.22 +56:09:22.6
23:29:09.84 +53:28:15.7
23:22:50.81 +51:55:37.3
23:14:39.08 +54:01:55.6
23:22:41.52 +50:08:52.2
00:10:41.97 +53:58:59.1
23:40:56.31 +56:21:53.4
23:52:43.95 +51:16:51.2
23:14:43.69 +55:59:17.7
23:27:03.30 +51:35:13.2
23:17:24.25 +53:56:33.4
23:21:31.46 +51:34:43.2
00:00:45.69 +52:08:01.9
23:27:04.54 +55:04:53.9
23:36:50.41 +55:44:36.5
23:14:10.81 +56:23:41.4
23:48:03.18 +49:59:47.6
23:52:37.41 +53:51:42.7
23:17:19.86 +55:48:34.8
23:21:37.01 +52:40:18.1
23:24:53.44 +51:36:44.3
23:41:49.02 +54:48:54.3
23:38:15.07 +53:10:00.6
23:15:34.86 +53:05:16.0
23:16:49.50 +56:44:36.6
23:55:32.65 +51:24:49.0
00:08:06.08 +51:46:32.5
23:20:42.93 +52:15:32.8
23:23:13.51 +55:06:38.9
23:18:01.86 +52:26:53.8
00:13:02.05 +53:50:13.4
23:26:51.69 +50:21:04.8
23:30:42.17 +51:38:08.2
23:33:46.95 +50:32:48.2
23:16:54.50 +55:48:01.6
23:19:09.98 +54:34:48.6
00:07:25.85 +52:06:06.5
23:28:15.83 +51:28:50.6
23:57:17.16 +54:23:56.1
23:39:31.96 +55:38:14.2
23:21:30.79 +50:33:07.4
23:57:57.45 +50:00:30.2
00:26:01.52 +49:49:08.2
23:24:06.39 +51:31:42.6
23:28:10.10 +53:34:41.6
00:09:04.02 +51:44:06.9
23:41:48.33 +51:06:34.3
00:10:11.06 +50:58:29.6
23:37:51.56 +55:18:45.1
23:41:14.11 +49:49:14.1
23:24:41.18 +50:40:04.3
00:16:43.69 +55:04:48.4
23:48:14.88 +49:50:27.4
00:16:58.68 +49:56:54.5
23:30:42.23 +58:00:32.4
23:17:20.32 +56:42:33.0
23:21:56.72 +51:25:13.0
23:21:22.07 +54:59:40.4
23:14:32.81 +57:06:02.1
00:05:32.26 +50:54:27.7
23:41:27.83 +55:38:04.4
00:29:14.27 +55:53:35.5
23:25:30.20 +56:41:11.7
23:27:35.60 +56:31:40.6
00:05:57.46 +52:01:29.6
00:13:15.18 +52:31:09.5
23:25:51.42 +52:56:18.2
00:25:38.30 +51:57:33.1
23:56:49.66 +50:03:02.6
23:22:06.89 +49:53:01.4
23:39:45.94 +51:01:25.7
23:53:42.64 +50:58:18.9
23:12:00.81 +56:27:21.2
00:07:16.61 +51:00:10.5
23:32:12.89 +57:11:42.5
23:21:09.71 +55:54:03.5
23:11:34.56 +56:00:12.8
00:23:21.01 +54:55:48.6
23:27:19.37 +56:40:17.5
23:12:59.22 +56:18:49.4
23:13:28.29 +56:57:07.3
00:24:45.52 +53:56:01.6
23:33:19.98 +56:17:51.8
23:17:13.98 +56:09:06.8
00:26:57.25 +51:56:51.5
00:11:25.43 +51:27:58.5
23:37:00.76 +55:33:52.6
23:43:57.52 +50:48:28.8
00:12:47.37 +49:45:30.1
23:48:48.78 +49:47:32.0
23:23:37.91 +52:10:26.6
23:32:50.17 +51:17:32.7
23:19:26.43 +55:24:32.2
00:30:44.10 +55:16:19.3
00:08:01.33 +52:54:48.5
23:18:15.39 +54:05:47.9
23:48:50.93 +52:53:26.7
23:18:00.09 +54:03:30.8
00:24:54.29 +53:42:17.4
23:57:04.14 +52:12:07.1
00:05:13.84 +51:50:45.1
23:24:14.45 +53:00:33.2
23:21:43.60 +55:58:25.2
23:30:29.36 +54:34:20.5
00:27:11.98 +54:05:42.0
00:05:10.94 +52:08:57.8
00:27:35.95 +51:54:37.9
00:18:16.28 +50:20:06.5
00:14:55.85 +52:36:26.6
00:07:14.12 +54:10:58.2
23:53:56.57 +50:54:38.7
00:09:57.80 +50:50:42.4
23:36:32.93 +49:50:56.6
00:03:48.58 +53:38:54.6
23:34:35.33 +52:37:11.9
23:30:12.41 +50:50:41.1
23:51:21.35 +49:51:40.4
23:19:19.45 +51:15:48.0
23:26:40.69 +52:55:03.1
23:14:03.80 +55:28:47.7
23:31:43.27 +51:03:17.0
00:07:47.15 +53:00:29.4
23:23:22.60 +51:40:38.1
23:55:21.24 +50:40:11.1
23:27:00.19 +54:16:26.7
23:34:14.12 +55:20:17.7
23:22:05.80 +53:17:47.3
23:13:13.49 +55:44:24.7
23:42:14.10 +53:08:23.2
23:40:46.26 +52:40:44.0
23:53:13.59 +50:51:15.3
23:30:30.78 +54:53:17.5
00:14:11.97 +51:14:39.1
23:17:56.32 +56:24:57.6
23:55:59.11 +52:04:39.5
23:36:21.73 +55:45:35.0
00:12:55.73 +51:32:02.4
23:17:45.15 +56:02:14.3
23:16:26.86 +55:52:30.9
23:55:40.56 +51:20:10.9
23:21:29.90 +53:08:53.6
23:34:13.01 +49:48:44.1
23:26:59.06 +52:45:09.1
23:20:52.72 +50:30:19.5
00:07:39.23 +50:26:56.5
00:13:00.67 +50:20:20.4
23:32:56.10 +50:39:59.2
23:17:33.59 +53:46:10.8
23:43:52.54 +51:14:18.6
23:49:20.50 +51:33:06.1
23:14:47.90 +57:31:28.9
23:21:51.60 +51:29:52.1
23:37:19.73 +55:38:16.1
23:32:22.09 +56:20:28.9
23:41:00.07 +52:48:21.7
23:32:59.80 +52:10:47.4
00:12:03.51 +57:04:15.6
23:24:23.16 +56:09:52.8
23:27:07.81 +50:41:41.7
23:27:35.41 +51:17:51.6
23:19:28.03 +49:32:04.5
23:23:20.83 +49:55:24.5
23:43:04.50 +51:10:43.8
00:13:09.78 +52:52:03.0
00:16:34.97 +51:26:36.1
23:26:55.30 +56:27:00.1
23:24:57.18 +56:11:24.6
00:13:03.03 +53:57:49.5
23:23:01.87 +49:50:17.6
23:15:49.86 +56:17:11.3
23:14:25.17 +56:23:21.9
23:18:33.24 +51:55:27.1
00:11:43.58 +53:03:48.3
00:23:47.71 +50:48:32.2
00:00:54.74 +50:41:25.2
23:31:21.08 +52:54:30.6
00:09:12.86 +53:00:00.4
23:43:04.70 +54:54:23.7
23:17:32.12 +55:39:03.6
23:17:22.54 +55:37:27.5
00:28:58.98 +53:42:04.1
00:01:26.42 +50:22:03.1
00:00:45.69 +51:03:39.9
23:30:56.17 +51:13:56.1
23:14:43.92 +53:06:03.5
23:21:55.22 +51:05:36.7
23:25:01.13 +56:45:07.0
23:37:56.15 +56:26:08.7
23:17:36.19 +50:30:27.5
23:33:43.67 +53:53:45.8
23:52:18.79 +50:33:05.4
23:34:13.53 +56:18:06.3
23:12:27.57 +56:09:43.7
23:48:21.25 +51:56:48.5
23:51:33.28 +50:53:06.4
23:22:24.22 +49:39:45.1
23:13:59.58 +56:34:36.6
23:22:05.22 +50:07:46.4
23:43:49.10 +49:48:53.3
00:11:32.61 +50:42:08.2
23:54:21.46 +50:47:55.7
23:38:10.23 +50:41:38.0
23:35:11.46 +51:47:21.8
23:56:55.48 +51:01:06.4
23:31:26.83 +50:23:06.7
23:25:12.43 +54:01:44.9
23:45:35.78 +54:51:42.9
23:44:13.10 +51:12:16.7
23:19:24.43 +56:40:31.3
23:52:42.36 +51:25:47.3
23:49:17.43 +52:48:58.4
23:28:45.64 +52:34:31.8
00:14:22.10 +52:18:11.0
23:14:00.70 +56:27:36.2
00:02:01.35 +52:54:05.5
23:25:23.20 +54:25:11.6
23:15:17.88 +54:16:36.7
23:36:06.17 +55:53:50.2
23:25:37.03 +56:43:28.1
00:24:26.44 +54:50:32.6
23:22:22.33 +56:30:16.3
23:16:09.77 +55:40:04.0
23:21:02.11 +55:24:46.2
###################################################################################
23:35:00.69 +50:11:06.2 -- not an asteroid (will add it to exclusion list)
23:24:00.53 +54:33:47.5 -- not an asteroid (will add it to exclusion list)
23:34:35.47 +50:44:04.8 -- not an asteroid (will add it to exclusion list)
23:35:15.89 +55:34:27.5 -- not an asteroid (will add it to exclusion list)
23:45:25.38 +54:19:00.2 -- not an asteroid (will add it to exclusion list)
23:21:42.62 +50:06:35.8 -- not an asteroid (will add it to exclusion list)
00:15:49.03 +57:32:30.9 -- not an asteroid (will add it to exclusion list)
00:00:07.62 +51:20:28.5 -- not an asteroid (will add it to exclusion list)
00:15:00.49 +53:35:32.6 -- not an asteroid (will add it to exclusion list)
23:16:18.05 +55:26:09.5 -- not an asteroid (will add it to exclusion list)
00:23:16.42 +54:07:27.3 -- not an asteroid (will add it to exclusion list)
23:34:55.40 +53:37:35.0 -- not an asteroid (will add it to exclusion list)
23:24:46.04 +55:53:02.9 -- not an asteroid (will add it to exclusion list)
00:15:37.89 +51:47:05.9 -- not an asteroid (will add it to exclusion list)
23:37:30.27 +55:27:05.5 -- not an asteroid (will add it to exclusion list)
23:35:59.38 +55:24:07.8 -- not an asteroid (will add it to exclusion list)
23:52:24.98 +54:32:28.7 -- not an asteroid (will add it to exclusion list)
23:39:02.44 +55:35:25.1 -- not an asteroid (will add it to exclusion list)
23:17:57.18 +52:26:57.5 -- not an asteroid (will add it to exclusion list)
23:52:13.43 +52:40:04.3 -- not an asteroid (will add it to exclusion list)
23:42:54.02 +55:43:45.1 -- not an asteroid (will add it to exclusion list)
23:44:13.88 +53:16:51.4 -- not an asteroid (will add it to exclusion list)
23:23:13.88 +51:43:24.6 -- not an asteroid (will add it to exclusion list)
00:10:03.65 +55:10:39.2 -- not an asteroid (will add it to exclusion list)
23:47:10.97 +53:39:21.8 -- not an asteroid (will add it to exclusion list)
23:28:39.25 +53:12:34.2 -- not an asteroid (will add it to exclusion list)
00:01:43.90 +50:08:50.6 -- not an asteroid (will add it to exclusion list)
23:34:24.21 +52:49:52.3 -- not an asteroid (will add it to exclusion list)
00:14:51.47 +52:19:01.5 -- not an asteroid (will add it to exclusion list)
23:28:01.74 +55:38:43.8 -- not an asteroid (will add it to exclusion list)
23:46:01.99 +54:36:45.9 -- not an asteroid (will add it to exclusion list)
00:13:12.44 +52:24:26.5 -- not an asteroid (will add it to exclusion list)
00:12:11.75 +51:44:24.0 -- not an asteroid (will add it to exclusion list)
23:30:06.75 +51:01:46.3 -- not an asteroid (will add it to exclusion list)
00:00:05.85 +52:33:48.4 -- not an asteroid (will add it to exclusion list)
00:04:07.44 +51:25:23.5 -- not an asteroid (will add it to exclusion list)
23:26:07.11 +55:38:15.0 -- not an asteroid (will add it to exclusion list)
23:43:41.94 +52:00:43.3 -- not an asteroid (will add it to exclusion list)
23:27:50.92 +50:26:22.3 -- not an asteroid (will add it to exclusion list)
23:32:56.79 +53:38:43.0 -- not an asteroid (will add it to exclusion list)
23:37:40.52 +55:28:55.3 -- not an asteroid (will add it to exclusion list)
23:26:23.17 +55:21:03.6 -- not an asteroid (will add it to exclusion list)
00:07:27.59 +50:53:52.0 -- not an asteroid (will add it to exclusion list)
23:53:53.89 +53:23:45.0 -- not an asteroid (will add it to exclusion list)
23:37:29.90 +56:31:52.9 -- not an asteroid (will add it to exclusion list)
23:27:51.87 +57:08:15.5 -- not an asteroid (will add it to exclusion list)
00:06:13.32 +51:56:53.9 -- not an asteroid (will add it to exclusion list)
23:27:42.19 +53:31:02.2 -- not an asteroid (will add it to exclusion list)
23:17:13.79 +56:28:28.8 -- not an asteroid (will add it to exclusion list)
23:17:10.26 +55:35:40.3 -- not an asteroid (will add it to exclusion list)
23:39:36.71 +51:31:08.8 -- not an asteroid (will add it to exclusion list)
23:25:28.75 +54:50:22.6 -- not an asteroid (will add it to exclusion list)
23:43:34.82 +55:18:55.4 -- not an asteroid (will add it to exclusion list)
23:34:09.42 +55:46:32.9 -- not an asteroid (will add it to exclusion list)
23:34:58.59 +55:47:45.8 -- not an asteroid (will add it to exclusion list)
23:13:50.99 +55:57:40.5 -- not an asteroid (will add it to exclusion list)
23:22:19.17 +54:46:36.1 -- not an asteroid (will add it to exclusion list)
00:03:16.36 +54:09:44.4 -- not an asteroid (will add it to exclusion list)
23:10:42.41 +56:27:19.9 -- not an asteroid (will add it to exclusion list)
23:41:20.97 +51:48:13.8 -- not an asteroid (will add it to exclusion list)
23:11:21.01 +56:24:12.1 -- not an asteroid (will add it to exclusion list)
23:47:58.44 +52:38:59.4 -- not an asteroid (will add it to exclusion list)
23:17:18.61 +56:04:22.4 -- not an asteroid (will add it to exclusion list)
23:42:19.10 +55:47:52.7 -- not an asteroid (will add it to exclusion list)
23:33:47.93 +57:28:40.7 -- not an asteroid (will add it to exclusion list)
23:23:47.98 +53:18:18.0 -- not an asteroid (will add it to exclusion list)
23:44:26.33 +52:09:01.8 -- not an asteroid (will add it to exclusion list)
00:20:22.17 +51:49:02.5 -- not an asteroid (will add it to exclusion list)
23:26:04.73 +54:30:25.1 -- not an asteroid (will add it to exclusion list)
00:28:12.68 +54:30:52.4 -- not an asteroid (will add it to exclusion list)
23:23:13.03 +56:57:57.2 -- not an asteroid (will add it to exclusion list)
00:05:25.40 +52:54:34.1 -- not an asteroid (will add it to exclusion list)
23:33:51.73 +56:19:28.0 -- not an asteroid (will add it to exclusion list)
23:17:49.59 +51:39:57.4 -- not an asteroid (will add it to exclusion list)
23:14:00.65 +56:16:06.4 -- not an asteroid (will add it to exclusion list)
23:22:22.22 +51:21:59.3 -- not an asteroid (will add it to exclusion list)
00:30:57.41 +55:56:16.0 -- not an asteroid (will add it to exclusion list)
23:54:47.01 +49:59:46.1 -- not an asteroid (will add it to exclusion list)
23:15:31.82 +55:29:12.1 -- not an asteroid (will add it to exclusion list)
23:17:33.22 +56:09:22.6 -- not an asteroid (will add it to exclusion list)
23:29:09.84 +53:28:15.7 -- not an asteroid (will add it to exclusion list)
23:22:50.81 +51:55:37.3 -- not an asteroid (will add it to exclusion list)
23:14:39.08 +54:01:55.6 -- not an asteroid (will add it to exclusion list)
23:22:41.52 +50:08:52.2 -- not an asteroid (will add it to exclusion list)
00:10:41.97 +53:58:59.1 -- not an asteroid (will add it to exclusion list)
23:40:56.31 +56:21:53.4 -- not an asteroid (will add it to exclusion list)
23:52:43.95 +51:16:51.2 -- not an asteroid (will add it to exclusion list)
23:14:43.69 +55:59:17.7 -- not an asteroid (will add it to exclusion list)
23:27:03.30 +51:35:13.2 -- not an asteroid (will add it to exclusion list)
23:17:24.25 +53:56:33.4 -- not an asteroid (will add it to exclusion list)
23:21:31.46 +51:34:43.2 -- not an asteroid (will add it to exclusion list)
00:00:45.69 +52:08:01.9 -- not an asteroid (will add it to exclusion list)
23:27:04.54 +55:04:53.9 -- not an asteroid (will add it to exclusion list)
23:36:50.41 +55:44:36.5 -- not an asteroid (will add it to exclusion list)
23:14:10.81 +56:23:41.4 -- not an asteroid (will add it to exclusion list)
23:48:03.18 +49:59:47.6 -- not an asteroid (will add it to exclusion list)
23:52:37.41 +53:51:42.7 -- not an asteroid (will add it to exclusion list)
23:17:19.86 +55:48:34.8 -- not an asteroid (will add it to exclusion list)
23:21:37.01 +52:40:18.1 -- not an asteroid (will add it to exclusion list)
23:24:53.44 +51:36:44.3 -- not an asteroid (will add it to exclusion list)
23:41:49.02 +54:48:54.3 -- not an asteroid (will add it to exclusion list)
23:38:15.07 +53:10:00.6 -- not an asteroid (will add it to exclusion list)
23:15:34.86 +53:05:16.0 -- not an asteroid (will add it to exclusion list)
23:16:49.50 +56:44:36.6 -- not an asteroid (will add it to exclusion list)
23:55:32.65 +51:24:49.0 -- not an asteroid (will add it to exclusion list)
00:08:06.08 +51:46:32.5 -- not an asteroid (will add it to exclusion list)
23:20:42.93 +52:15:32.8 -- not an asteroid (will add it to exclusion list)
23:23:13.51 +55:06:38.9 -- not an asteroid (will add it to exclusion list)
23:18:01.86 +52:26:53.8 -- not an asteroid (will add it to exclusion list)
00:13:02.05 +53:50:13.4 -- not an asteroid (will add it to exclusion list)
23:26:51.69 +50:21:04.8 -- not an asteroid (will add it to exclusion list)
23:30:42.17 +51:38:08.2 -- not an asteroid (will add it to exclusion list)
23:33:46.95 +50:32:48.2 -- not an asteroid (will add it to exclusion list)
23:16:54.50 +55:48:01.6 -- not an asteroid (will add it to exclusion list)
23:19:09.98 +54:34:48.6 -- not an asteroid (will add it to exclusion list)
00:07:25.85 +52:06:06.5 -- not an asteroid (will add it to exclusion list)
23:28:15.83 +51:28:50.6 -- not an asteroid (will add it to exclusion list)
23:57:17.16 +54:23:56.1 -- not an asteroid (will add it to exclusion list)
23:39:31.96 +55:38:14.2 -- not an asteroid (will add it to exclusion list)
23:21:30.79 +50:33:07.4 -- not an asteroid (will add it to exclusion list)
23:57:57.45 +50:00:30.2 -- not an asteroid (will add it to exclusion list)
00:26:01.52 +49:49:08.2 -- not an asteroid (will add it to exclusion list)
23:24:06.39 +51:31:42.6 -- not an asteroid (will add it to exclusion list)
23:28:10.10 +53:34:41.6 -- not an asteroid (will add it to exclusion list)
00:09:04.02 +51:44:06.9 -- not an asteroid (will add it to exclusion list)
23:41:48.33 +51:06:34.3 -- not an asteroid (will add it to exclusion list)
00:10:11.06 +50:58:29.6 -- not an asteroid (will add it to exclusion list)
23:37:51.56 +55:18:45.1 -- not an asteroid (will add it to exclusion list)
23:41:14.11 +49:49:14.1 -- not an asteroid (will add it to exclusion list)
23:24:41.18 +50:40:04.3 -- not an asteroid (will add it to exclusion list)
00:16:43.69 +55:04:48.4 -- not an asteroid (will add it to exclusion list)
23:48:14.88 +49:50:27.4 -- not an asteroid (will add it to exclusion list)
00:16:58.68 +49:56:54.5 -- not an asteroid (will add it to exclusion list)
23:30:42.23 +58:00:32.4 -- not an asteroid (will add it to exclusion list)
23:17:20.32 +56:42:33.0 -- not an asteroid (will add it to exclusion list)
23:21:56.72 +51:25:13.0 -- not an asteroid (will add it to exclusion list)
23:21:22.07 +54:59:40.4 -- not an asteroid (will add it to exclusion list)
23:14:32.81 +57:06:02.1 -- not an asteroid (will add it to exclusion list)
00:05:32.26 +50:54:27.7 -- not an asteroid (will add it to exclusion list)
23:41:27.83 +55:38:04.4 -- not an asteroid (will add it to exclusion list)
00:29:14.27 +55:53:35.5 -- not an asteroid (will add it to exclusion list)
23:25:30.20 +56:41:11.7 -- not an asteroid (will add it to exclusion list)
23:27:35.60 +56:31:40.6 -- not an asteroid (will add it to exclusion list)
00:05:57.46 +52:01:29.6 -- not an asteroid (will add it to exclusion list)
00:13:15.18 +52:31:09.5 -- not an asteroid (will add it to exclusion list)
23:25:51.42 +52:56:18.2 -- not an asteroid (will add it to exclusion list)
00:25:38.30 +51:57:33.1 -- not an asteroid (will add it to exclusion list)
23:56:49.66 +50:03:02.6 -- not an asteroid (will add it to exclusion list)
23:22:06.89 +49:53:01.4 -- not an asteroid (will add it to exclusion list)
23:39:45.94 +51:01:25.7 -- not an asteroid (will add it to exclusion list)
23:53:42.64 +50:58:18.9 -- not an asteroid (will add it to exclusion list)
23:12:00.81 +56:27:21.2 -- not an asteroid (will add it to exclusion list)
00:07:16.61 +51:00:10.5 -- not an asteroid (will add it to exclusion list)
23:32:12.89 +57:11:42.5 -- not an asteroid (will add it to exclusion list)
23:21:09.71 +55:54:03.5 -- not an asteroid (will add it to exclusion list)
23:11:34.56 +56:00:12.8 -- not an asteroid (will add it to exclusion list)
00:23:21.01 +54:55:48.6 -- not an asteroid (will add it to exclusion list)
23:27:19.37 +56:40:17.5 -- not an asteroid (will add it to exclusion list)
23:12:59.22 +56:18:49.4 -- not an asteroid (will add it to exclusion list)
23:13:28.29 +56:57:07.3 -- not an asteroid (will add it to exclusion list)
00:24:45.52 +53:56:01.6 -- not an asteroid (will add it to exclusion list)
23:33:19.98 +56:17:51.8 -- not an asteroid (will add it to exclusion list)
23:17:13.98 +56:09:06.8 -- not an asteroid (will add it to exclusion list)
00:26:57.25 +51:56:51.5 -- not an asteroid (will add it to exclusion list)
00:11:25.43 +51:27:58.5 -- not an asteroid (will add it to exclusion list)
23:37:00.76 +55:33:52.6 -- not an asteroid (will add it to exclusion list)
23:43:57.52 +50:48:28.8 -- not an asteroid (will add it to exclusion list)
00:12:47.37 +49:45:30.1 -- not an asteroid (will add it to exclusion list)
23:48:48.78 +49:47:32.0 -- not an asteroid (will add it to exclusion list)
23:23:37.91 +52:10:26.6 -- not an asteroid (will add it to exclusion list)
23:32:50.17 +51:17:32.7 -- not an asteroid (will add it to exclusion list)
23:19:26.43 +55:24:32.2 -- not an asteroid (will add it to exclusion list)
00:30:44.10 +55:16:19.3 -- not an asteroid (will add it to exclusion list)
00:08:01.33 +52:54:48.5 -- not an asteroid (will add it to exclusion list)
23:18:15.39 +54:05:47.9 -- not an asteroid (will add it to exclusion list)
23:48:50.93 +52:53:26.7 -- not an asteroid (will add it to exclusion list)
23:18:00.09 +54:03:30.8 -- not an asteroid (will add it to exclusion list)
00:24:54.29 +53:42:17.4 -- not an asteroid (will add it to exclusion list)
23:57:04.14 +52:12:07.1 -- not an asteroid (will add it to exclusion list)
00:05:13.84 +51:50:45.1 -- not an asteroid (will add it to exclusion list)
23:24:14.45 +53:00:33.2 -- not an asteroid (will add it to exclusion list)
23:21:43.60 +55:58:25.2 -- not an asteroid (will add it to exclusion list)
23:30:29.36 +54:34:20.5 -- not an asteroid (will add it to exclusion list)
00:27:11.98 +54:05:42.0 -- not an asteroid (will add it to exclusion list)
00:05:10.94 +52:08:57.8 -- not an asteroid (will add it to exclusion list)
00:27:35.95 +51:54:37.9 -- not an asteroid (will add it to exclusion list)
00:18:16.28 +50:20:06.5 -- not an asteroid (will add it to exclusion list)
00:14:55.85 +52:36:26.6 -- not an asteroid (will add it to exclusion list)
00:07:14.12 +54:10:58.2 -- not an asteroid (will add it to exclusion list)
23:53:56.57 +50:54:38.7 -- not an asteroid (will add it to exclusion list)
00:09:57.80 +50:50:42.4 -- not an asteroid (will add it to exclusion list)
23:36:32.93 +49:50:56.6 -- not an asteroid (will add it to exclusion list)
00:03:48.58 +53:38:54.6 -- not an asteroid (will add it to exclusion list)
23:34:35.33 +52:37:11.9 -- not an asteroid (will add it to exclusion list)
23:30:12.41 +50:50:41.1 -- not an asteroid (will add it to exclusion list)
23:51:21.35 +49:51:40.4 -- not an asteroid (will add it to exclusion list)
23:19:19.45 +51:15:48.0 -- not an asteroid (will add it to exclusion list)
23:26:40.69 +52:55:03.1 -- not an asteroid (will add it to exclusion list)
23:14:03.80 +55:28:47.7 -- not an asteroid (will add it to exclusion list)
23:31:43.27 +51:03:17.0 -- not an asteroid (will add it to exclusion list)
00:07:47.15 +53:00:29.4 -- not an asteroid (will add it to exclusion list)
23:23:22.60 +51:40:38.1 -- not an asteroid (will add it to exclusion list)
23:55:21.24 +50:40:11.1 -- not an asteroid (will add it to exclusion list)
23:27:00.19 +54:16:26.7 -- not an asteroid (will add it to exclusion list)
23:34:14.12 +55:20:17.7 -- not an asteroid (will add it to exclusion list)
23:22:05.80 +53:17:47.3 -- not an asteroid (will add it to exclusion list)
23:13:13.49 +55:44:24.7 -- not an asteroid (will add it to exclusion list)
23:42:14.10 +53:08:23.2 -- not an asteroid (will add it to exclusion list)
23:40:46.26 +52:40:44.0 -- not an asteroid (will add it to exclusion list)
23:53:13.59 +50:51:15.3 -- not an asteroid (will add it to exclusion list)
23:30:30.78 +54:53:17.5 -- not an asteroid (will add it to exclusion list)
00:14:11.97 +51:14:39.1 -- not an asteroid (will add it to exclusion list)
23:17:56.32 +56:24:57.6 -- not an asteroid (will add it to exclusion list)
23:55:59.11 +52:04:39.5 -- not an asteroid (will add it to exclusion list)
23:36:21.73 +55:45:35.0 -- not an asteroid (will add it to exclusion list)
00:12:55.73 +51:32:02.4 -- not an asteroid (will add it to exclusion list)
23:17:45.15 +56:02:14.3 -- not an asteroid (will add it to exclusion list)
23:16:26.86 +55:52:30.9 -- not an asteroid (will add it to exclusion list)
23:55:40.56 +51:20:10.9 -- not an asteroid (will add it to exclusion list)
23:21:29.90 +53:08:53.6 -- not an asteroid (will add it to exclusion list)
23:34:13.01 +49:48:44.1 -- not an asteroid (will add it to exclusion list)
23:26:59.06 +52:45:09.1 -- not an asteroid (will add it to exclusion list)
23:20:52.72 +50:30:19.5 -- not an asteroid (will add it to exclusion list)
00:07:39.23 +50:26:56.5 -- not an asteroid (will add it to exclusion list)
00:13:00.67 +50:20:20.4 -- not an asteroid (will add it to exclusion list)
23:32:56.10 +50:39:59.2 -- not an asteroid (will add it to exclusion list)
23:17:33.59 +53:46:10.8 -- not an asteroid (will add it to exclusion list)
23:43:52.54 +51:14:18.6 -- not an asteroid (will add it to exclusion list)
23:49:20.50 +51:33:06.1 -- not an asteroid (will add it to exclusion list)
23:14:47.90 +57:31:28.9 -- not an asteroid (will add it to exclusion list)
23:21:51.60 +51:29:52.1 -- not an asteroid (will add it to exclusion list)
23:37:19.73 +55:38:16.1 -- not an asteroid (will add it to exclusion list)
23:32:22.09 +56:20:28.9 -- not an asteroid (will add it to exclusion list)
23:41:00.07 +52:48:21.7 -- not an asteroid (will add it to exclusion list)
23:32:59.80 +52:10:47.4 -- not an asteroid (will add it to exclusion list)
00:12:03.51 +57:04:15.6 -- not an asteroid (will add it to exclusion list)
23:24:23.16 +56:09:52.8 -- not an asteroid (will add it to exclusion list)
23:27:07.81 +50:41:41.7 -- not an asteroid (will add it to exclusion list)
23:27:35.41 +51:17:51.6 -- not an asteroid (will add it to exclusion list)
23:19:28.03 +49:32:04.5 -- not an asteroid (will add it to exclusion list)
23:23:20.83 +49:55:24.5 -- not an asteroid (will add it to exclusion list)
23:43:04.50 +51:10:43.8 -- not an asteroid (will add it to exclusion list)
00:13:09.78 +52:52:03.0 -- not an asteroid (will add it to exclusion list)
00:16:34.97 +51:26:36.1 -- not an asteroid (will add it to exclusion list)
23:26:55.30 +56:27:00.1 -- not an asteroid (will add it to exclusion list)
23:24:57.18 +56:11:24.6 -- not an asteroid (will add it to exclusion list)
00:13:03.03 +53:57:49.5 -- not an asteroid (will add it to exclusion list)
23:23:01.87 +49:50:17.6 -- not an asteroid (will add it to exclusion list)
23:15:49.86 +56:17:11.3 -- not an asteroid (will add it to exclusion list)
23:14:25.17 +56:23:21.9 -- not an asteroid (will add it to exclusion list)
23:18:33.24 +51:55:27.1 -- not an asteroid (will add it to exclusion list)
00:11:43.58 +53:03:48.3 -- not an asteroid (will add it to exclusion list)
00:23:47.71 +50:48:32.2 -- not an asteroid (will add it to exclusion list)
00:00:54.74 +50:41:25.2 -- not an asteroid (will add it to exclusion list)
23:31:21.08 +52:54:30.6 -- not an asteroid (will add it to exclusion list)
00:09:12.86 +53:00:00.4 -- not an asteroid (will add it to exclusion list)
23:43:04.70 +54:54:23.7 -- not an asteroid (will add it to exclusion list)
23:17:32.12 +55:39:03.6 -- not an asteroid (will add it to exclusion list)
23:17:22.54 +55:37:27.5 -- not an asteroid (will add it to exclusion list)
00:28:58.98 +53:42:04.1 -- not an asteroid (will add it to exclusion list)
00:01:26.42 +50:22:03.1 -- not an asteroid (will add it to exclusion list)
00:00:45.69 +51:03:39.9 -- not an asteroid (will add it to exclusion list)
23:30:56.17 +51:13:56.1 -- not an asteroid (will add it to exclusion list)
23:14:43.92 +53:06:03.5 -- not an asteroid (will add it to exclusion list)
23:21:55.22 +51:05:36.7 -- not an asteroid (will add it to exclusion list)
23:25:01.13 +56:45:07.0 -- not an asteroid (will add it to exclusion list)
23:37:56.15 +56:26:08.7 -- not an asteroid (will add it to exclusion list)
23:17:36.19 +50:30:27.5 -- not an asteroid (will add it to exclusion list)
23:33:43.67 +53:53:45.8 -- not an asteroid (will add it to exclusion list)
23:52:18.79 +50:33:05.4 -- not an asteroid (will add it to exclusion list)
23:34:13.53 +56:18:06.3 -- not an asteroid (will add it to exclusion list)
23:12:27.57 +56:09:43.7 -- not an asteroid (will add it to exclusion list)
23:48:21.25 +51:56:48.5 -- not an asteroid (will add it to exclusion list)
23:51:33.28 +50:53:06.4 -- not an asteroid (will add it to exclusion list)
23:22:24.22 +49:39:45.1 -- not an asteroid (will add it to exclusion list)
23:13:59.58 +56:34:36.6 -- not an asteroid (will add it to exclusion list)
23:22:05.22 +50:07:46.4 -- not an asteroid (will add it to exclusion list)
23:43:49.10 +49:48:53.3 -- not an asteroid (will add it to exclusion list)
00:11:32.61 +50:42:08.2 -- not an asteroid (will add it to exclusion list)
23:54:21.46 +50:47:55.7 -- not an asteroid (will add it to exclusion list)
23:38:10.23 +50:41:38.0 -- not an asteroid (will add it to exclusion list)
23:35:11.46 +51:47:21.8 -- not an asteroid (will add it to exclusion list)
23:56:55.48 +51:01:06.4 -- not an asteroid (will add it to exclusion list)
23:31:26.83 +50:23:06.7 -- not an asteroid (will add it to exclusion list)
23:25:12.43 +54:01:44.9 -- not an asteroid (will add it to exclusion list)
23:45:35.78 +54:51:42.9 -- not an asteroid (will add it to exclusion list)
23:44:13.10 +51:12:16.7 -- not an asteroid (will add it to exclusion list)
23:19:24.43 +56:40:31.3 -- not an asteroid (will add it to exclusion list)
23:52:42.36 +51:25:47.3 -- not an asteroid (will add it to exclusion list)
23:49:17.43 +52:48:58.4 -- not an asteroid (will add it to exclusion list)
23:28:45.64 +52:34:31.8 -- not an asteroid (will add it to exclusion list)
00:14:22.10 +52:18:11.0 -- not an asteroid (will add it to exclusion list)
23:14:00.70 +56:27:36.2 -- not an asteroid (will add it to exclusion list)
00:02:01.35 +52:54:05.5 -- not an asteroid (will add it to exclusion list)
23:25:23.20 +54:25:11.6 -- not an asteroid (will add it to exclusion list)
23:15:17.88 +54:16:36.7 -- not an asteroid (will add it to exclusion list)
23:36:06.17 +55:53:50.2 -- not an asteroid (will add it to exclusion list)
23:25:37.03 +56:43:28.1 -- not an asteroid (will add it to exclusion list)
00:24:26.44 +54:50:32.6 -- not an asteroid (will add it to exclusion list)
23:22:22.33 +56:30:16.3 -- not an asteroid (will add it to exclusion list)
23:16:09.77 +55:40:04.0 -- not an asteroid (will add it to exclusion list)
23:21:02.11 +55:24:46.2 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:05.85 +52:33:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:07.62 +51:20:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:45.69 +51:03:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:45.69 +52:08:01.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:54.74 +50:41:25.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:26.42 +50:22:03.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:43.90 +50:08:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:01.35 +52:54:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:16.36 +54:09:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:48.58 +53:38:54.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:07.44 +51:25:23.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:10.94 +52:08:57.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:13.84 +51:50:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:25.40 +52:54:34.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:32.26 +50:54:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:57.46 +52:01:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:13.32 +51:56:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:14.12 +54:10:58.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:16.61 +51:00:10.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:25.85 +52:06:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:27.59 +50:53:52.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:39.23 +50:26:56.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:47.15 +53:00:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:01.33 +52:54:48.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:06.08 +51:46:32.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:04.02 +51:44:06.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:12.86 +53:00:00.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:57.80 +50:50:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:03.65 +55:10:39.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:11.06 +50:58:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:41.97 +53:58:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:25.43 +51:27:58.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:32.61 +50:42:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:43.58 +53:03:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:03.51 +57:04:15.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:11.75 +51:44:24.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:47.37 +49:45:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:55.73 +51:32:02.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:00.67 +50:20:20.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:02.05 +53:50:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:03.03 +53:57:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:09.78 +52:52:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:12.44 +52:24:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:15.18 +52:31:09.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:11.97 +51:14:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:22.10 +52:18:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:51.47 +52:19:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:55.85 +52:36:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:00.49 +53:35:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:37.89 +51:47:05.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:49.03 +57:32:30.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:34.97 +51:26:36.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:43.69 +55:04:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:58.68 +49:56:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:16.28 +50:20:06.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:22.17 +51:49:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:16.42 +54:07:27.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:21.01 +54:55:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:47.71 +50:48:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:26.44 +54:50:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:45.52 +53:56:01.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:54.29 +53:42:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:38.30 +51:57:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:01.52 +49:49:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:57.25 +51:56:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:11.98 +54:05:42.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:35.95 +51:54:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:12.68 +54:30:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:58.98 +53:42:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:14.27 +55:53:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:44.10 +55:16:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:57.41 +55:56:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:42.41 +56:27:19.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:21.01 +56:24:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:34.56 +56:00:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:00.81 +56:27:21.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:27.57 +56:09:43.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:59.22 +56:18:49.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:13.49 +55:44:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:28.29 +56:57:07.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:50.99 +55:57:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:59.58 +56:34:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:00.65 +56:16:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:00.70 +56:27:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:03.80 +55:28:47.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:10.81 +56:23:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:25.17 +56:23:21.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:32.81 +57:06:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:39.08 +54:01:55.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:43.69 +55:59:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:43.92 +53:06:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:47.90 +57:31:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:17.88 +54:16:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:31.82 +55:29:12.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:34.86 +53:05:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:49.86 +56:17:11.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:09.77 +55:40:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:18.05 +55:26:09.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:26.86 +55:52:30.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:49.50 +56:44:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:54.50 +55:48:01.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:10.26 +55:35:40.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:13.79 +56:28:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:13.98 +56:09:06.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:18.61 +56:04:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:19.86 +55:48:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:20.32 +56:42:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:22.54 +55:37:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:24.25 +53:56:33.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:32.12 +55:39:03.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:33.22 +56:09:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:33.59 +53:46:10.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:36.19 +50:30:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:45.15 +56:02:14.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:49.59 +51:39:57.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:56.32 +56:24:57.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:57.18 +52:26:57.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:00.09 +54:03:30.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:01.86 +52:26:53.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:15.39 +54:05:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:33.24 +51:55:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:09.98 +54:34:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:19.45 +51:15:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:24.43 +56:40:31.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:26.43 +55:24:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:28.03 +49:32:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:42.93 +52:15:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:52.72 +50:30:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:02.11 +55:24:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:09.71 +55:54:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:22.07 +54:59:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:29.90 +53:08:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:30.79 +50:33:07.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:31.46 +51:34:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:37.01 +52:40:18.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:42.62 +50:06:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:43.60 +55:58:25.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:51.60 +51:29:52.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:55.22 +51:05:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:56.72 +51:25:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:05.22 +50:07:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:05.80 +53:17:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:06.89 +49:53:01.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:19.17 +54:46:36.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:22.22 +51:21:59.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:22.33 +56:30:16.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:24.22 +49:39:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:41.52 +50:08:52.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:50.81 +51:55:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:01.87 +49:50:17.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.03 +56:57:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.51 +55:06:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.88 +51:43:24.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:20.83 +49:55:24.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:22.60 +51:40:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:37.91 +52:10:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:47.98 +53:18:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:00.53 +54:33:47.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:06.39 +51:31:42.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:14.45 +53:00:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:23.16 +56:09:52.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:41.18 +50:40:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:46.04 +55:53:02.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:53.44 +51:36:44.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:57.18 +56:11:24.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:01.13 +56:45:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:12.43 +54:01:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:23.20 +54:25:11.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:28.75 +54:50:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:30.20 +56:41:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:37.03 +56:43:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:51.42 +52:56:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:04.73 +54:30:25.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:07.11 +55:38:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:23.17 +55:21:03.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:40.69 +52:55:03.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:51.69 +50:21:04.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:55.30 +56:27:00.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:59.06 +52:45:09.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:00.19 +54:16:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:03.30 +51:35:13.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:04.54 +55:04:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:07.81 +50:41:41.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:19.37 +56:40:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:35.41 +51:17:51.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:35.60 +56:31:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:42.19 +53:31:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:50.92 +50:26:22.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:51.87 +57:08:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:01.74 +55:38:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:10.10 +53:34:41.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:15.83 +51:28:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:39.25 +53:12:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:45.64 +52:34:31.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:09.84 +53:28:15.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:06.75 +51:01:46.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:12.41 +50:50:41.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:29.36 +54:34:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:30.78 +54:53:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:42.17 +51:38:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:42.23 +58:00:32.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:56.17 +51:13:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:21.08 +52:54:30.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:26.83 +50:23:06.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:43.27 +51:03:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:12.89 +57:11:42.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:22.09 +56:20:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:50.17 +51:17:32.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:56.10 +50:39:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:56.79 +53:38:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:59.80 +52:10:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:19.98 +56:17:51.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:43.67 +53:53:45.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:46.95 +50:32:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:47.93 +57:28:40.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:51.73 +56:19:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:09.42 +55:46:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:13.01 +49:48:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:13.53 +56:18:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:14.12 +55:20:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:24.21 +52:49:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:35.33 +52:37:11.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:35.47 +50:44:04.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:55.40 +53:37:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:58.59 +55:47:45.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:00.69 +50:11:06.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:11.46 +51:47:21.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:15.89 +55:34:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:59.38 +55:24:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:06.17 +55:53:50.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:21.73 +55:45:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:32.93 +49:50:56.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:50.41 +55:44:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:00.76 +55:33:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:19.73 +55:38:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:29.90 +56:31:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:30.27 +55:27:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:40.52 +55:28:55.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:51.56 +55:18:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:56.15 +56:26:08.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:10.23 +50:41:38.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:15.07 +53:10:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:02.44 +55:35:25.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:31.96 +55:38:14.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:36.71 +51:31:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:45.94 +51:01:25.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:46.26 +52:40:44.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:56.31 +56:21:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:00.07 +52:48:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:14.11 +49:49:14.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:20.97 +51:48:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:27.83 +55:38:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:48.33 +51:06:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:49.02 +54:48:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:14.10 +53:08:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:19.10 +55:47:52.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:54.02 +55:43:45.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:04.50 +51:10:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:04.70 +54:54:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:34.82 +55:18:55.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:41.94 +52:00:43.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:49.10 +49:48:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:52.54 +51:14:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:57.52 +50:48:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:13.10 +51:12:16.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:13.88 +53:16:51.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:26.33 +52:09:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:25.38 +54:19:00.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:35.78 +54:51:42.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:01.99 +54:36:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:10.97 +53:39:21.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:58.44 +52:38:59.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:03.18 +49:59:47.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:14.88 +49:50:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:21.25 +51:56:48.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:48.78 +49:47:32.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:50.93 +52:53:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:17.43 +52:48:58.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:20.50 +51:33:06.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:21.35 +49:51:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:33.28 +50:53:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:13.43 +52:40:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:18.79 +50:33:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:24.98 +54:32:28.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:37.41 +53:51:42.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:42.36 +51:25:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:43.95 +51:16:51.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:13.59 +50:51:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:42.64 +50:58:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:53.89 +53:23:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:56.57 +50:54:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:21.46 +50:47:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:47.01 +49:59:46.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:21.24 +50:40:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:32.65 +51:24:49.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:40.56 +51:20:10.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:59.11 +52:04:39.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:49.66 +50:03:02.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:55.48 +51:01:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:04.14 +52:12:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:17.16 +54:23:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:57.45 +50:00:30.2 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:00:05.85 +52:33:48.4 -- not a known variable star
00:00:07.62 +51:20:28.5 -- not a known variable star
00:00:45.69 +51:03:39.9 -- not a known variable star
00:00:45.69 +52:08:01.9 -- not a known variable star
00:00:54.74 +50:41:25.2 -- not a known variable star
00:01:26.42 +50:22:03.1 -- not a known variable star
00:01:43.90 +50:08:50.6 -- not a known variable star
00:02:01.35 +52:54:05.5 -- not a known variable star
00:03:16.36 +54:09:44.4 -- not a known variable star
00:03:48.58 +53:38:54.6 -- not a known variable star
00:04:07.44 +51:25:23.5 -- not a known variable star
00:05:10.94 +52:08:57.8 -- not a known variable star
00:05:13.84 +51:50:45.1 -- not a known variable star
00:05:25.40 +52:54:34.1 -- not a known variable star
00:05:32.26 +50:54:27.7 -- not a known variable star
00:05:57.46 +52:01:29.6 -- not a known variable star
00:06:13.32 +51:56:53.9 -- not a known variable star
00:07:14.12 +54:10:58.2 -- not a known variable star
00:07:16.61 +51:00:10.5 -- not a known variable star
00:07:25.85 +52:06:06.5 -- not a known variable star
00:07:27.59 +50:53:52.0 -- not a known variable star
00:07:39.23 +50:26:56.5 -- not a known variable star
00:07:47.15 +53:00:29.4 -- not a known variable star
00:08:01.33 +52:54:48.5 -- not a known variable star
00:08:06.08 +51:46:32.5 -- not a known variable star
00:09:04.02 +51:44:06.9 -- not a known variable star
00:09:12.86 +53:00:00.4 -- not a known variable star
00:09:57.80 +50:50:42.4 -- not a known variable star
00:10:03.65 +55:10:39.2 -- not a known variable star
00:10:11.06 +50:58:29.6 -- not a known variable star
00:10:41.97 +53:58:59.1 -- not a known variable star
00:11:25.43 +51:27:58.5 -- not a known variable star
00:11:32.61 +50:42:08.2 -- not a known variable star
00:11:43.58 +53:03:48.3 -- not a known variable star
00:12:03.51 +57:04:15.6 -- not a known variable star
00:12:11.75 +51:44:24.0 -- not a known variable star
00:12:47.37 +49:45:30.1 -- not a known variable star
00:12:55.73 +51:32:02.4 -- not a known variable star
00:13:00.67 +50:20:20.4 -- not a known variable star
00:13:02.05 +53:50:13.4 -- not a known variable star
00:13:03.03 +53:57:49.5 -- not a known variable star
00:13:09.78 +52:52:03.0 -- not a known variable star
00:13:12.44 +52:24:26.5 -- not a known variable star
00:13:15.18 +52:31:09.5 -- not a known variable star
00:14:11.97 +51:14:39.1 -- not a known variable star
00:14:22.10 +52:18:11.0 -- not a known variable star
00:14:51.47 +52:19:01.5 -- not a known variable star
00:14:55.85 +52:36:26.6 -- not a known variable star
00:15:00.49 +53:35:32.6 -- not a known variable star
00:15:37.89 +51:47:05.9 -- not a known variable star
00:15:49.03 +57:32:30.9 -- a known variable star
00:16:34.97 +51:26:36.1 -- not a known variable star
00:16:43.69 +55:04:48.4 -- not a known variable star
00:16:58.68 +49:56:54.5 -- not a known variable star
00:18:16.28 +50:20:06.5 -- not a known variable star
00:20:22.17 +51:49:02.5 -- not a known variable star
00:23:16.42 +54:07:27.3 -- not a known variable star
00:23:21.01 +54:55:48.6 -- not a known variable star
00:23:47.71 +50:48:32.2 -- not a known variable star
00:24:26.44 +54:50:32.6 -- not a known variable star
00:24:45.52 +53:56:01.6 -- not a known variable star
00:24:54.29 +53:42:17.4 -- not a known variable star
00:25:38.30 +51:57:33.1 -- not a known variable star
00:26:01.52 +49:49:08.2 -- not a known variable star
00:26:57.25 +51:56:51.5 -- not a known variable star
00:27:11.98 +54:05:42.0 -- not a known variable star
00:27:35.95 +51:54:37.9 -- not a known variable star
00:28:12.68 +54:30:52.4 -- not a known variable star
00:28:58.98 +53:42:04.1 -- not a known variable star
00:29:14.27 +55:53:35.5 -- a known variable star
00:30:44.10 +55:16:19.3 -- not a known variable star
00:30:57.41 +55:56:16.0 -- not a known variable star
23:10:42.41 +56:27:19.9 -- not a known variable star
23:11:21.01 +56:24:12.1 -- not a known variable star
23:11:34.56 +56:00:12.8 -- not a known variable star
23:12:00.81 +56:27:21.2 -- not a known variable star
23:12:27.57 +56:09:43.7 -- not a known variable star
23:12:59.22 +56:18:49.4 -- not a known variable star
23:13:13.49 +55:44:24.7 -- not a known variable star
23:13:28.29 +56:57:07.3 -- not a known variable star
23:13:50.99 +55:57:40.5 -- not a known variable star
23:13:59.58 +56:34:36.6 -- not a known variable star
23:14:00.65 +56:16:06.4 -- not a known variable star
23:14:00.70 +56:27:36.2 -- not a known variable star
23:14:03.80 +55:28:47.7 -- not a known variable star
23:14:10.81 +56:23:41.4 -- a known variable star
23:14:25.17 +56:23:21.9 -- not a known variable star
23:14:32.81 +57:06:02.1 -- not a known variable star
23:14:39.08 +54:01:55.6 -- not a known variable star
23:14:43.69 +55:59:17.7 -- not a known variable star
23:14:43.92 +53:06:03.5 -- not a known variable star
23:14:47.90 +57:31:28.9 -- not a known variable star
23:15:17.88 +54:16:36.7 -- not a known variable star
23:15:31.82 +55:29:12.1 -- a known variable star
23:15:34.86 +53:05:16.0 -- not a known variable star
23:15:49.86 +56:17:11.3 -- not a known variable star
23:16:09.77 +55:40:04.0 -- not a known variable star
23:16:18.05 +55:26:09.5 -- not a known variable star
23:16:26.86 +55:52:30.9 -- not a known variable star
23:16:49.50 +56:44:36.6 -- not a known variable star
23:16:54.50 +55:48:01.6 -- a known variable star
23:17:10.26 +55:35:40.3 -- not a known variable star
23:17:13.79 +56:28:28.8 -- not a known variable star
23:17:13.98 +56:09:06.8 -- not a known variable star
23:17:18.61 +56:04:22.4 -- not a known variable star
23:17:19.86 +55:48:34.8 -- not a known variable star
23:17:20.32 +56:42:33.0 -- not a known variable star
23:17:22.54 +55:37:27.5 -- not a known variable star
23:17:24.25 +53:56:33.4 -- a known variable star
23:17:32.12 +55:39:03.6 -- not a known variable star
23:17:33.22 +56:09:22.6 -- not a known variable star
23:17:33.59 +53:46:10.8 -- not a known variable star
23:17:36.19 +50:30:27.5 -- not a known variable star
23:17:45.15 +56:02:14.3 -- not a known variable star
23:17:49.59 +51:39:57.4 -- not a known variable star
23:17:56.32 +56:24:57.6 -- not a known variable star
23:17:57.18 +52:26:57.5 -- not a known variable star
23:18:00.09 +54:03:30.8 -- a known variable star
23:18:01.86 +52:26:53.8 -- a known variable star
23:18:15.39 +54:05:47.9 -- a known variable star
23:18:33.24 +51:55:27.1 -- not a known variable star
23:19:09.98 +54:34:48.6 -- not a known variable star
23:19:19.45 +51:15:48.0 -- not a known variable star
23:19:24.43 +56:40:31.3 -- not a known variable star
23:19:26.43 +55:24:32.2 -- not a known variable star
23:19:28.03 +49:32:04.5 -- not a known variable star
23:20:42.93 +52:15:32.8 -- not a known variable star
23:20:52.72 +50:30:19.5 -- not a known variable star
23:21:02.11 +55:24:46.2 -- not a known variable star
23:21:09.71 +55:54:03.5 -- a known variable star
23:21:22.07 +54:59:40.4 -- not a known variable star
23:21:29.90 +53:08:53.6 -- not a known variable star
23:21:30.79 +50:33:07.4 -- not a known variable star
23:21:31.46 +51:34:43.2 -- not a known variable star
23:21:37.01 +52:40:18.1 -- not a known variable star
23:21:42.62 +50:06:35.8 -- not a known variable star
23:21:43.60 +55:58:25.2 -- not a known variable star
23:21:51.60 +51:29:52.1 -- not a known variable star
23:21:55.22 +51:05:36.7 -- not a known variable star
23:21:56.72 +51:25:13.0 -- not a known variable star
23:22:05.22 +50:07:46.4 -- not a known variable star
23:22:05.80 +53:17:47.3 -- not a known variable star
23:22:06.89 +49:53:01.4 -- not a known variable star
23:22:19.17 +54:46:36.1 -- not a known variable star
23:22:22.22 +51:21:59.3 -- not a known variable star
23:22:22.33 +56:30:16.3 -- not a known variable star
23:22:24.22 +49:39:45.1 -- not a known variable star
23:22:41.52 +50:08:52.2 -- not a known variable star
23:22:50.81 +51:55:37.3 -- not a known variable star
23:23:01.87 +49:50:17.6 -- not a known variable star
23:23:13.03 +56:57:57.2 -- not a known variable star
23:23:13.51 +55:06:38.9 -- not a known variable star
23:23:13.88 +51:43:24.6 -- not a known variable star
23:23:20.83 +49:55:24.5 -- not a known variable star
23:23:22.60 +51:40:38.1 -- not a known variable star
23:23:37.91 +52:10:26.6 -- not a known variable star
23:23:47.98 +53:18:18.0 -- not a known variable star
23:24:00.53 +54:33:47.5 -- not a known variable star
23:24:06.39 +51:31:42.6 -- not a known variable star
23:24:14.45 +53:00:33.2 -- not a known variable star
23:24:23.16 +56:09:52.8 -- not a known variable star
23:24:41.18 +50:40:04.3 -- not a known variable star
23:24:46.04 +55:53:02.9 -- not a known variable star
23:24:53.44 +51:36:44.3 -- not a known variable star
23:24:57.18 +56:11:24.6 -- not a known variable star
23:25:01.13 +56:45:07.0 -- not a known variable star
23:25:12.43 +54:01:44.9 -- not a known variable star
23:25:23.20 +54:25:11.6 -- not a known variable star
23:25:28.75 +54:50:22.6 -- not a known variable star
23:25:30.20 +56:41:11.7 -- not a known variable star
23:25:37.03 +56:43:28.1 -- not a known variable star
23:25:51.42 +52:56:18.2 -- not a known variable star
23:26:04.73 +54:30:25.1 -- not a known variable star
23:26:07.11 +55:38:15.0 -- not a known variable star
23:26:23.17 +55:21:03.6 -- not a known variable star
23:26:40.69 +52:55:03.1 -- not a known variable star
23:26:51.69 +50:21:04.8 -- not a known variable star
23:26:55.30 +56:27:00.1 -- not a known variable star
23:26:59.06 +52:45:09.1 -- not a known variable star
23:27:00.19 +54:16:26.7 -- not a known variable star
23:27:03.30 +51:35:13.2 -- not a known variable star
23:27:04.54 +55:04:53.9 -- not a known variable star
23:27:07.81 +50:41:41.7 -- a known variable star
23:27:19.37 +56:40:17.5 -- not a known variable star
23:27:35.41 +51:17:51.6 -- not a known variable star
23:27:35.60 +56:31:40.6 -- not a known variable star
23:27:42.19 +53:31:02.2 -- not a known variable star
23:27:50.92 +50:26:22.3 -- not a known variable star
23:27:51.87 +57:08:15.5 -- not a known variable star
23:28:01.74 +55:38:43.8 -- not a known variable star
23:28:10.10 +53:34:41.6 -- not a known variable star
23:28:15.83 +51:28:50.6 -- not a known variable star
23:28:39.25 +53:12:34.2 -- not a known variable star
23:28:45.64 +52:34:31.8 -- not a known variable star
23:29:09.84 +53:28:15.7 -- not a known variable star
23:30:06.75 +51:01:46.3 -- not a known variable star
23:30:12.41 +50:50:41.1 -- not a known variable star
23:30:29.36 +54:34:20.5 -- not a known variable star
23:30:30.78 +54:53:17.5 -- not a known variable star
23:30:42.17 +51:38:08.2 -- not a known variable star
23:30:42.23 +58:00:32.4 -- not a known variable star
23:30:56.17 +51:13:56.1 -- not a known variable star
23:31:21.08 +52:54:30.6 -- not a known variable star
23:31:26.83 +50:23:06.7 -- not a known variable star
23:31:43.27 +51:03:17.0 -- not a known variable star
23:32:12.89 +57:11:42.5 -- not a known variable star
23:32:22.09 +56:20:28.9 -- not a known variable star
23:32:50.17 +51:17:32.7 -- not a known variable star
23:32:56.10 +50:39:59.2 -- not a known variable star
23:32:56.79 +53:38:43.0 -- not a known variable star
23:32:59.80 +52:10:47.4 -- not a known variable star
23:33:19.98 +56:17:51.8 -- not a known variable star
23:33:43.67 +53:53:45.8 -- not a known variable star
23:33:46.95 +50:32:48.2 -- not a known variable star
23:33:47.93 +57:28:40.7 -- a known variable star
23:33:51.73 +56:19:28.0 -- not a known variable star
23:34:09.42 +55:46:32.9 -- not a known variable star
23:34:13.01 +49:48:44.1 -- not a known variable star
23:34:13.53 +56:18:06.3 -- not a known variable star
23:34:14.12 +55:20:17.7 -- not a known variable star
23:34:24.21 +52:49:52.3 -- not a known variable star
23:34:35.33 +52:37:11.9 -- not a known variable star
23:34:35.47 +50:44:04.8 -- not a known variable star
23:34:55.40 +53:37:35.0 -- not a known variable star
23:34:58.59 +55:47:45.8 -- not a known variable star
23:35:00.69 +50:11:06.2 -- not a known variable star
23:35:11.46 +51:47:21.8 -- a known variable star
23:35:15.89 +55:34:27.5 -- a known variable star
23:35:59.38 +55:24:07.8 -- not a known variable star
23:36:06.17 +55:53:50.2 -- not a known variable star
23:36:21.73 +55:45:35.0 -- not a known variable star
23:36:32.93 +49:50:56.6 -- not a known variable star
23:36:50.41 +55:44:36.5 -- not a known variable star
23:37:00.76 +55:33:52.6 -- not a known variable star
23:37:19.73 +55:38:16.1 -- not a known variable star
23:37:29.90 +56:31:52.9 -- not a known variable star
23:37:30.27 +55:27:05.5 -- not a known variable star
23:37:40.52 +55:28:55.3 -- not a known variable star
23:37:51.56 +55:18:45.1 -- not a known variable star
23:37:56.15 +56:26:08.7 -- not a known variable star
23:38:10.23 +50:41:38.0 -- not a known variable star
23:38:15.07 +53:10:00.6 -- not a known variable star
23:39:02.44 +55:35:25.1 -- not a known variable star
23:39:31.96 +55:38:14.2 -- not a known variable star
23:39:36.71 +51:31:08.8 -- not a known variable star
23:39:45.94 +51:01:25.7 -- not a known variable star
23:40:46.26 +52:40:44.0 -- not a known variable star
23:40:56.31 +56:21:53.4 -- not a known variable star
23:41:00.07 +52:48:21.7 -- a known variable star
23:41:14.11 +49:49:14.1 -- not a known variable star
23:41:20.97 +51:48:13.8 -- not a known variable star
23:41:27.83 +55:38:04.4 -- not a known variable star
23:41:48.33 +51:06:34.3 -- not a known variable star
23:41:49.02 +54:48:54.3 -- not a known variable star
23:42:14.10 +53:08:23.2 -- not a known variable star
23:42:19.10 +55:47:52.7 -- not a known variable star
23:42:54.02 +55:43:45.1 -- not a known variable star
23:43:04.50 +51:10:43.8 -- not a known variable star
23:43:04.70 +54:54:23.7 -- a known variable star
23:43:34.82 +55:18:55.4 -- not a known variable star
23:43:41.94 +52:00:43.3 -- not a known variable star
23:43:49.10 +49:48:53.3 -- not a known variable star
23:43:52.54 +51:14:18.6 -- not a known variable star
23:43:57.52 +50:48:28.8 -- not a known variable star
23:44:13.10 +51:12:16.7 -- not a known variable star
23:44:13.88 +53:16:51.4 -- not a known variable star
23:44:26.33 +52:09:01.8 -- not a known variable star
23:45:25.38 +54:19:00.2 -- not a known variable star
23:45:35.78 +54:51:42.9 -- not a known variable star
23:46:01.99 +54:36:45.9 -- not a known variable star
23:47:10.97 +53:39:21.8 -- not a known variable star
23:47:58.44 +52:38:59.4 -- not a known variable star
23:48:03.18 +49:59:47.6 -- not a known variable star
23:48:14.88 +49:50:27.4 -- not a known variable star
23:48:21.25 +51:56:48.5 -- not a known variable star
23:48:48.78 +49:47:32.0 -- not a known variable star
23:48:50.93 +52:53:26.7 -- not a known variable star
23:49:17.43 +52:48:58.4 -- not a known variable star
23:49:20.50 +51:33:06.1 -- not a known variable star
23:51:21.35 +49:51:40.4 -- not a known variable star
23:51:33.28 +50:53:06.4 -- not a known variable star
23:52:13.43 +52:40:04.3 -- not a known variable star
23:52:18.79 +50:33:05.4 -- not a known variable star
23:52:24.98 +54:32:28.7 -- not a known variable star
23:52:37.41 +53:51:42.7 -- not a known variable star
23:52:42.36 +51:25:47.3 -- not a known variable star
23:52:43.95 +51:16:51.2 -- not a known variable star
23:53:13.59 +50:51:15.3 -- not a known variable star
23:53:42.64 +50:58:18.9 -- not a known variable star
23:53:53.89 +53:23:45.0 -- not a known variable star
23:53:56.57 +50:54:38.7 -- not a known variable star
23:54:21.46 +50:47:55.7 -- not a known variable star
23:54:47.01 +49:59:46.1 -- not a known variable star
23:55:21.24 +50:40:11.1 -- not a known variable star
23:55:32.65 +51:24:49.0 -- not a known variable star
23:55:40.56 +51:20:10.9 -- not a known variable star
23:55:59.11 +52:04:39.5 -- not a known variable star
23:56:49.66 +50:03:02.6 -- not a known variable star
23:56:55.48 +51:01:06.4 -- not a known variable star
23:57:04.14 +52:12:07.1 -- not a known variable star
23:57:17.16 +54:23:56.1 -- a known variable star
23:57:57.45 +50:00:30.2 -- not a known variable star
Found 285 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
302 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 302 (excluding asteroids and hot pixels, 285 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)2461274.84208006 -observatory V36
09:45:06.27 +15:19:26.8 Mercury (-1.7mag)
12:50:09.76 -07:46:13.8 Venus (-4.5mag)
06:29:49.76 +23:39:00.1 Mars (1.3mag)
08:55:29.25 +17:53:06.9 Jupiter (-1.8mag)
00:54:49.37 +03:01:33.4 Saturn (0.5mag)
04:13:02.20 +21:00:19.1 Uranus (5.7mag)
00:15:08.08 +00:06:16.9 Neptune (7.7mag)
20:26:50.70 -23:35:11.8 Pluto (14.5mag)
17:26:16.99 -28:32:09.5 Moon (-11.0mag)
-rw-r--r-- 1 apache apache 363 Aug 22 03:31 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461274.84208006:
08:55:33.20 +17:52:48.7 Io (6.1mag)
08:55:36.46 +17:52:34.4 Europa (6.3mag)
08:55:45.31 +17:51:53.9 Ganymede (5.6mag)
08:55:09.77 +17:54:38.4 Callisto (6.9mag)
08:52:57.48 +18:01:06.8 Himalia (15.7mag)
08:55:28.57 +17:53:10.9 Thebe (16.6mag)
08:52:36.71 +17:56:59.2 Elara (17.7mag)
08:59:36.86 +17:26:22.5 Pasiphae (17.9mag)
08:57:42.43 +18:06:41.8 Carme (19.0mag)
00:54:45.82 +03:01:58.8 Titan (8.4mag)
00:54:54.01 +03:01:24.1 Rhea (9.7mag)
00:55:24.81 +03:03:14.1 Iapetus (11.1mag)
00:54:57.28 +03:01:50.0 Hyperion (14.4mag)
00:53:54.16 +02:52:58.9 Phoebe (16.4mag)
-rw-r--r-- 1 apache apache 568 Aug 22 03:31 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461274.84208006:
20:11:52.09 -14:04:41.3 JWST
17:32:41.88 +35:45:21.4 Chandra
10:54:34.76 -59:10:44.6 XMM-Newton
-rw-r--r-- 1 apache apache 96 Aug 22 03:31 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461274.84208006 -observatory V36
03:28:14.52 +18:26:25.0 17.5mag P/1996 R2 (Lagerkvist)
17:59:54.59 -34:28:36.0 14.2mag P/2010 H2 (Vales)
07:06:29.56 -69:29:22.5 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
06:13:08.44 +33:18:25.8 17.7mag C/2017 K2 (PANSTARRS)
04:21:04.94 +42:24:15.0 17.5mag P/2021 N1 (ZTF)
22:26:44.63 +30:22:45.0 17.4mag C/2022 E2 (ATLAS)
06:56:53.92 +26:17:01.5 16.8mag C/2022 N2 (PANSTARRS)
10:34:41.64 +27:51:09.5 17.0mag C/2022 QE78 (ATLAS)
09:38:17.60 +05:17:59.6 18.0mag C/2022 R6 (PANSTARRS)
15:15:39.64 -12:52:39.3 18.0mag P/2023 B1 (PANSTARRS)
20:53:26.98 +64:04:24.5 18.0mag C/2023 H5 (Lemmon)
15:36:29.43 -14:13:54.3 14.6mag C/2023 R1 (PANSTARRS)
08:23:14.67 +32:00:42.6 15.5mag C/2024 E1 (Wierzchos)
15:05:42.23 +15:30:16.8 17.8mag C/2024 G6 (ATLAS)
18:46:52.30 +43:29:22.9 13.7mag C/2024 J3 (ATLAS)
20:49:25.95 +49:41:18.6 17.5mag C/2024 R4 (PANSTARRS)
05:25:45.11 -12:53:57.4 15.3mag C/2024 T5 (ATLAS)
07:04:36.20 +21:36:36.5 17.9mag C/2025 J1 (Borisov)
10:53:14.76 +19:57:32.2 17.1mag C/2025 V2 (Rankin)
13:07:23.07 +01:21:19.4 16.9mag C/2025 Y1 (ATLAS)
16:10:28.45 +76:17:30.1 16.5mag C/2026 A2 (Bok)
03:09:55.63 +46:20:58.9 17.3mag C/2026 B2 (Sun-Gao)
11:58:50.41 +09:55:35.8 17.4mag A/2026 E1
22:12:23.66 -32:17:54.5 7.1mag 10P/Tempel
11:37:42.69 -04:19:10.4 16.3mag 29P/Schwassmann-Wachmann
11:36:22.81 +00:01:44.6 17.4mag 63P/Wild
00:51:37.85 -06:06:06.5 15.4mag 65P/Gunn
06:06:44.91 +20:14:37.3 13.7mag 78P/Gehrels
20:25:50.61 -24:59:53.6 17.5mag 84P/Giclas
03:11:59.24 +14:32:11.3 16.9mag 88P/Howell
08:30:28.14 +25:35:19.8 16.4mag 93P/Lovas
04:47:31.30 +22:24:24.3 17.2mag 112P/Urata-Niijima
06:42:30.82 +28:18:02.2 16.1mag 114P/Wiseman-Skiff
09:51:36.84 +24:05:50.0 14.9mag 123P/West-Hartley
12:12:29.17 -15:35:58.0 17.3mag 124P/Mrkos
05:56:43.83 +21:01:46.4 16.0mag 128P/Shoemaker-Holt
06:51:55.51 +18:06:06.8 17.9mag 131P/Mueller
23:59:37.91 +03:06:03.9 17.4mag 139P/Vaisala-Oterma
03:09:38.75 -18:37:37.4 12.8mag 161P/Hartley-IRAS
08:03:33.76 +38:07:18.7 16.1mag 162P/Siding Spring
11:04:21.74 +29:57:17.5 12.2mag 169P/NEAT
03:06:09.45 +09:23:42.0 17.6mag 220P/McNaught
20:16:20.82 -51:48:43.8 18.0mag 259P/Garradd
04:03:13.44 +30:49:23.1 15.3mag 260P/McNaught
07:47:15.45 +37:05:21.3 17.3mag 295P/LINEAR
15:16:10.75 +01:33:23.9 17.8mag 391P/Kowalski
09:13:42.04 +17:40:07.1 17.9mag 450P/LONEOS
-rw-r--r-- 1 apache apache 2.3K Aug 22 03:31 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
21:28:47.85 +20:31:03.60 SN 2026sfn 2026-08-16.3 17.09
23:01:28.67 -61:00:39.00 SN 2026yib 2026-08-14.85 17.36
00:22:23.20 -32:16:02.70 SN 2026whu 2026-08-14.96 16.5
19:56:21.71 -37:24:19.90 ASASSN-26ew 2026-08-13.82 14.73
13:53:14.21 +00:26:52.00 SN 2026wkv 2026-08-10.12 15.83
05:21:07.61 +23:38:20.10 TCP J05210763+2338194 2026-08-10.59 9.34
01:28:20.49 +40:13:27.10 SN2026wpd 2026-08-9.34 16.37
23:47:50.87 +49:28:49.80 SN2026wjs 2026-08-9.35 17.12
16:03:20.92 +17:43:23.70 AT2026xau 2026-08-9.3 17.71
01:10:22.05 -09:34:08.50 SN2026weo 2026-08-7.46 15.76
00:56:54.35 -35:55:29.40 AT2026wdy 2026-08-5.05 16.08
22:08:07.63 -53:03:58.90 AT2026wek 2026-08-3.82 17.17
14:51:51.34 +66:13:24.60 ASASSN-26ev 2026-08-2.15 14.02
12:06:50.79 -36:16:06.20 SN2026wgm 2026-08-1.73 15.61
16:56:36.90 -59:29:26.00 ASASSN-26er 2026-07-25.82 15.09
01:21:27.83 -10:37:05.00 SN2026vbh 2026-07-25.61 15.97
21:17:31.59 +22:25:50.90 ASASSN-26eq 2026-07-24.37 15.13
18:53:36.89 +16:56:43.60 ASASSN-26ep 2026-07-23.47 -4.06
12:18:47.98 -30:48:47.50 ASASSN-26et 2026-07-22.76 13.98
13:00:47.82 +15:42:17.60 SN2026uwk 2026-07-21.75 16.38
18:52:31.11 -32:28:00.90 ASASSN-26en 2026-07-21.77 14.63
14:42:58.01 -62:32:59.10 ASASSN-26es 2026-07-20.79 15.36
20:12:45.57 -32:53:13.00 ASASSN-26em 2026-07-20.94 16.83
18:54:24.33 -46:11:51.70 ASASSN-26eu 2026-07-20.93 14.86
03:18:56.99 -80:55:10.40 AT2026ugi 2026-07-20.03 17.12
18:43:58.40 +24:22:41.80 ASASSN-26eo 2026-07-19.36 16.16
04:50:01.03 -02:22:33.80 ASASSN-26ej 2026-07-16.17 17.02
18:34:55.28 -31:41:00.90 ASASSN-26ek 2026-07-16.24 15.73
17:07:43.61 -44:21:53.50 ASASSN-26el 2026-07-15.86 16.01
14:45:08.35 +24:13:12.30 ASASSN-26ei 2026-07-16.17 16.46
10:00:46.44 -32:36:31.10 AT 2023mhb 2026-07-14.73 16.67
14:39:37.45 -11:22:36.20 AT 2026unl 2026-07-15.27 17.11
10:49:42.57 -11:25:55.80 ASASSN-26eh 2026-07-14.72 16.58
19:33:53.06 -07:15:00.80 ASASSN-22le 2026-07-14.15 15.5
02:45:40.52 -27:55:30.30 ASASSN-26ef 2026-07-12.35 15.86
23:26:43.80 +04:42:39.70 SN 2026qtn 2026-07-12.22 16.47
02:19:17.26 +28:57:15.40 ASASSN-26ec 2026-07-11.53 2.78
18:31:15.56 -05:34:31.50 AT2026stb 2026-07-11.28 -1.29
13:36:08.24 +23:29:05.00 AT2026pjf 2026-07-10.18 -0.72
17:33:39.82 +04:22:36.70 SN2026pir 2026-07-9.86 -0.66
11:21:41.26 -50:33:36.30 ASASSN-26ed 2026-07-8.8 -1.3
23:41:42.11 +26:29:49.10 AT2026qil 2026-07-9.3 16.15
20:21:30.50 -32:03:40.10 ASASSN-26ee 2026-07-7.22 15.53
19:37:44.09 -05:35:42.80 AT2026ryu 2026-07-7.17 14.88
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.67 +32:04:22.70 AT2026ovz 2026-06-14.6 15.52
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
-rw-r--r-- 1 apache apache 5.7K Aug 22 03:31 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
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
00:44:56.43 +41:57:41.6 PNV J00445643+4157416 2026-07-13.8026 17.98Cmag
00:42:55.36 +41:17:27.0 PNV J00425536+4117270 2026-07-20.1813 17.7mag
20:35:43.64 +61:31:32.9 TCP J20354364+6131329 2026-07-20.5443 14.4mag
21:17:31.48 +22:25:51.0 TCP J21173148+2225510 2026-07-23.5577 14.8mag
00:41:24.04 +40:49:02.8 PNV J00412404+4049028 2026-07-25.0157 18.7mag
00:43:04.26 +41:02:28.6 PNV J00430426+4102286 2026-07-26.1512 20mag
14:51:51.40 +66:13:24.0 TCP J14515140+6613240 2026-07-29.2561 13.5mag
00:43:06.15 +41:22:08.2 PNV J00430615+4122082 2026-07-30.0085 19.4mag
00:41:33.23 +41:10:12.2 PNV J00413323+4110122 2026-08-02.8913 17.1mag
05:21:07.63 +23:38:19.4 TCP J05210763+2338194 2026-08-06.4109 11.2mag
22:57:17.96 +47:07:41.8 TCP J22571796+4707418 2026-08-09.3289 14.3mag
09:13:38.17 +76:28:18.1 PSN J09133817+7628181 2026-08-09.8037 15.4mag
00:43:17.29 +41:26:48.6 PNV J00431729+4126486 2026-08-14.0920 16.8mag
00:42:52.82 +41:10:58.6 PNV J00425282+4110586 2026-08-17.7723 19.9mag
00:42:52.83 +41:10:59.6 PNV J00425283+4110596 2026-08-18.6119 19.3mag
18:25:12.76 -22:25:29.3 TCP J18251276-2225293 2026-08-19.1062 9.4mag
18:03:09.04 +12:18:14.0 TCP J18030904+1218140 2026-08-19.5199 14.9mag
-rw-r--r-- 1 apache apache 190K Aug 22 03:31 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
08:44:08.771 +29:07:45.05 AT 2026xfr 2026-01-14.38 20.4
23:28:59.311 -21:41:17.71 AT 2026xfq 2026-07-19.57 21.15
20:34:55.430 -31:12:10.98 AT 2026xfp 2026-07-14.44 20
13:01:30.092 +38:12:35.50 AT 2026xfo 2026-06-23.28 20.85
23:22:05.758 +18:57:29.94 AT 2026xfn 2026-07-25.52 21.28
10:13:35.246 -20:37:42.73 AT 2026xfm 2026-01-27.58 21
21:57:25.287 +03:48:20.98 AT 2026xfl 2026-07-16.55 21.68
14:26:07.382 +33:39:52.18 AT 2026xfk 2026-06-13.34 20.9
02:09:31.559 -03:10:04.80 AT 2026xfj 2026-01-17.24 21.98
20:17:01.562 -20:06:27.94 AT 2026xfi 2026-05-20.56 20.93
21:08:09.912 -21:12:24.85 AT 2026xfh 2026-06-19.58 20.9
20:08:20.135 -25:53:36.34 AT 2026xfg 2026-07-19.45 20.74
14:51:25.078 +41:07:07.07 AT 2026xff 2026-06-13.34 21.62
22:33:15.210 +12:04:33.49 AT 2026xfe 2026-06-21.53 20.23
13:52:05.795 +29:21:47.19 AT 2026xfd 2026-04-24.32 20.92
13:30:27.613 +10:38:39.93 AT 2026xfc 2026-04-20.32 21.07
13:40:18.442 +39:30:10.71 AT 2026xfb 2026-05-24.29 20.6
20:02:32.611 -29:31:03.47 AT 2026xfa 2026-06-16.52 19.85
21:35:00.881 +03:50:25.49 AT 2026xez 2026-07-16.55 21.5
08:33:56.550 +06:59:43.01 AT 2026xey 2026-01-24.36 22.17
-rw-r--r-- 1 apache apache 87K Aug 22 03:31 tns_transients_list.txt
