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_031613_TTUQ2b1x1_966823_xFrhn4Pq
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.3414 2461274.8414 12.18 23:29:29.97 +49:37:15.3
109.57309 -11.11365 galactic And Second-epoch detections are separated by 1.9" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:29.97 +49:37:15.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:29:29.97 +49:37:15.3: 15.38 +/- 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:29:29.97 +49:37:15.3: 14.77 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.38 +/- 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.3414* 23 29 29.97 +49 37 15.3 12.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.8414,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 10.60 23:21:42.74 +50:06:34.6
108.53299 -10.23687 galactic And Second-epoch detections are separated by 2.5" and 7.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:21:42.74 +50:06:34.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:21:42.74 +50:06:34.6: 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.74 +50:06:34.6: 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.3414* 23 21 42.74 +50 06 34.6 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
target,2461274.8414,10.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 10.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.3414 2461274.8414 11.39 00:15:49.44 +57:32:33.9
118.14918 -4.99790 galactic Cas Second-epoch detections are separated by 2.6" and 7.5 pix
The object was found in VSX11" 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.44 +57:32:33.9: 12.60 +/- 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.44 +57:32:33.9: 12.70 +/- 0.05 detection
Forced photometry reference-image weighted average: 12.62 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 15 49.44 +57 32 33.9 11.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
FN Cas,2461274.8414,11.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
FN Cas 20260822.3414 11.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.3414 2461274.8414 11.46 23:34:54.46 +52:08:21.4
111.18128 -8.97779 galactic Cas Second-epoch detections are separated by 6.5" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:54.46 +52:08:21.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:34:54.46 +52:08:21.4: 13.50 +/- 0.06 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:34:54.46 +52:08:21.4: 13.44 +/- 0.10 detection
Forced photometry reference-image weighted average: 13.48 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 34 54.46 +52 08 21.4 11.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,11.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 11.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 11.60 00:00:07.71 +51:20:32.3
114.81766 -10.71927 galactic Cas Second-epoch detections are separated by 5.0" and 7.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: VOTx414464 | 00:00:07.71 +51:20:32.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 00:00:07.71 +51:20:32.3: 14.52 +/- 0.14 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.71 +51:20:32.3: 14.92 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.52 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 00 07.71 +51 20 32.3 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx414464,2461274.8414,11.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: VOTx414464 20260822.3414 11.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.3414 2461274.8414 12.01 23:32:44.09 +53:36:12.7
111.30714 -7.48246 galactic Cas Second-epoch detections are separated by 4.1" 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 | ATO J353.1680+53.6064 | 23:32:44.09 +53:36:12.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) J-Ks=0.507+/- (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:44.09 +53:36:12.7: 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:32:44.09 +53:36:12.7: 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.3414* 23 32 44.09 +53 36 12.7 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J353.1680+53.6064,2461274.8414,12.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 J353.1680+53.6064 20260822.3414 12.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.3414 2461274.8414 14.23 23:16:32.99 +54:49:21.6
109.46642 -5.54916 galactic Cas Second-epoch detections are separated by 6.4" 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 | ATO J349.1232+54.8178 | 23:16:32.99 +54:49:21.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:16:32.99 +54:49:21.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:32.99 +54:49:21.6: 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.3414* 23 16 32.99 +54 49 21.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
ATO J349.1232+54.8178,2461274.8414,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
ATO J349.1232+54.8178 20260822.3414 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.3414 2461274.8414 14.29 00:25:19.84 +55:36:44.6
119.22283 -7.07123 galactic Cas Second-epoch detections are separated by 5.6" and 7.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:25:19.84 +55:36:44.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:25:19.84 +55:36:44.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 00:25:19.84 +55:36:44.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.3414* 00 25 19.84 +55 36 44.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.8414,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.3414 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.3414 2461274.8414 14.41 23:45:23.48 +50:07:59.0
112.22289 -11.36036 galactic Cas Second-epoch detections are separated by 5.3" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:23.48 +50:07:59.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:45:23.48 +50:07:59.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:45:23.48 +50:07:59.0: 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.3414* 23 45 23.48 +50 07 59.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.8414,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.3414 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.3414 2461274.8414 14.33 23:32:19.52 +54:37:52.5
111.56289 -6.48478 galactic Cas Second-epoch detections are separated by 6.8" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:32:19.52 +54:37:52.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:32:19.52 +54:37:52.5: 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:19.52 +54:37:52.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.3414* 23 32 19.52 +54 37 52.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.20 23:43:16.32 +53:14:40.0
112.72443 -8.27098 galactic Cas Second-epoch detections are separated by 5.0" and 7.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:43:16.32 +53:14:40.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:43:16.32 +53:14:40.0: 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:43:16.32 +53:14:40.0: 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.3414* 23 43 16.32 +53 14 40.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.8414,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.3414 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.3414 2461274.8414 14.35 23:16:46.59 +53:53:20.6
109.15983 -6.43219 galactic Cas Second-epoch detections are separated by 6.3" 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 | target | 23:16:46.59 +53:53:20.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:46.59 +53:53:20.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:16:46.59 +53:53:20.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.3414* 23 16 46.59 +53 53 20.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.8414,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.3414 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.3414 2461274.8414 14.34 23:14:19.90 +56:28:34.6
109.77659 -3.89485 galactic Cas Second-epoch detections are separated by 7.4" and 6.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:14:19.90 +56:28:34.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:19.90 +56:28:34.6: 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:19.90 +56:28:34.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.3414* 23 14 19.90 +56 28 34.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.8414,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.3414 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.3414 2461274.8414 14.22 23:53:10.37 +53:00:57.2
114.12377 -8.85652 galactic Cas Second-epoch detections are separated by 2.9" and 7.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:10.37 +53:00: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:53:10.37 +53:00:57.2: 15.20 +/- 0.23 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:53:10.37 +53:00:57.2: 15.05 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.20 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 53 10.37 +53 00 57.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.8414,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.3414 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.3414 2461274.8414 14.22 00:29:16.52 +53:48:56.1
119.62413 -8.91376 galactic Cas Second-epoch detections are separated by 3.2" and 7.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:29:16.52 +53:48:56.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:29:16.52 +53:48:56.1: 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:29:16.52 +53:48:56.1: 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.3414* 00 29 16.52 +53 48 56.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.8414,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.3414 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.3414 2461274.8414 14.36 23:43:41.74 +53:56:59.9
112.97270 -7.60670 galactic Cas Second-epoch detections are separated by 7.1" and 7.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:41.74 +53:56:59.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:43:41.74 +53:56:59.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 23:43:41.74 +53:56:59.9: 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.3414* 23 43 41.74 +53 56 59.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.8414,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.3414 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.3414 2461274.8414 14.43 23:47:56.17 +50:14:16.4
112.65193 -11.36208 galactic Cas Second-epoch detections are separated by 8.7" and 7.6 pix
The object was found in VSX 6" ZTF J234756.19+501422.2
Type: BY
# Max. Min./Amp. JD0 Period
16.420 r Y 0.086 r 2458464.76040 4.495411000000
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:47:56.17 +50:14:16.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:47:56.17 +50:14:16.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.3414* 23 47 56.17 +50 14 16.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
ZTF J234756.19+501422.2,2461274.8414,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
ZTF J234756.19+501422.2 20260822.3414 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.3414 2461274.8414 14.35 23:22:35.41 +56:22:51.3
110.81424 -4.38612 galactic Cas Second-epoch detections are separated by 2.8" 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 | ATO J350.6523+56.3723 | 23:22:35.41 +56:22:51.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:22:35.41 +56:22:51.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:22:35.41 +56:22:51.3: 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.3414* 23 22 35.41 +56 22 51.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 J350.6523+56.3723,2461274.8414,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
ATO J350.6523+56.3723 20260822.3414 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.3414 2461274.8414 14.24 00:03:51.22 +51:49:58.3
115.49174 -10.35016 galactic Cas Second-epoch detections are separated by 2.6" and 7.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:03:51.22 +51:49:58.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:03:51.22 +51:49:58.3: 15.54 +/- 0.33 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:03:51.22 +51:49:58.3: 15.00 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.54 +/- 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.3414* 00 03 51.22 +51 49 58.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.8414,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.3414 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.3414 2461274.8414 14.33 23:48:15.24 +50:33:25.1
112.78250 -11.06547 galactic Cas Second-epoch detections are separated by 4.1" and 7.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:15.24 +50:33: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:48:15.24 +50:33:25.1: 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:48:15.24 +50:33:25.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.3414* 23 48 15.24 +50 33 25.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.21 23:46:01.92 +54:36:44.3
113.47658 -7.05426 galactic Cas Second-epoch detections are separated by 7.7" and 7.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:46:01.92 +54: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:46:01.92 +54:36:44.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:46:01.92 +54:36:44.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.3414* 23 46 01.92 +54 36 44.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.8414,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.3414 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.3414 2461274.8414 14.12 23:23:09.30 +53:47:07.2
110.01149 -6.85705 galactic Cas Second-epoch detections are separated by 7.9" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:09.30 +53:47:07.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:09.30 +53:47:07.2: 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:23:09.30 +53:47:07.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.3414* 23 23 09.30 +53 47 07.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.8414,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.3414 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.3414 2461274.8414 14.41 00:04:10.54 +53:29:36.3
115.85262 -8.72745 galactic Cas Second-epoch detections are separated by 3.8" and 7.5 pix
The object was found in VSX19" Gaia DR3 396210050163206016
Type: ROT
# Max. Min./Amp. JD0 Period
14.600 G 14.640 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 00:04:10.54 +53:29:36.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:04:10.54 +53:29:36.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.3414* 00 04 10.54 +53 29 36.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
Gaia DR3 396210050163206016,2461274.8414,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 396210050163206016 20260822.3414 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.3414 2461274.8414 14.21 23:28:37.49 +53:47:15.7
110.78145 -7.11897 galactic Cas Second-epoch detections are separated by 8.0" and 7.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:28:37.49 +53:47: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:28:37.49 +53:47:15.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:28:37.49 +53:47:15.7: 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.3414* 23 28 37.49 +53 47 15.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.8414,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.3414 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.3414 2461274.8414 14.42 00:03:29.32 +53:34:29.9
115.76647 -8.62836 galactic Cas Second-epoch detections are separated by 6.6" and 7.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:03:29.32 +53:34:29.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:03:29.32 +53:34:29.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:03:29.32 +53:34:29.9: 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.3414* 00 03 29.32 +53 34 29.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.8414,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
target 20260822.3414 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.3414 2461274.8414 14.26 23:46:07.83 +52:16:11.1
112.89218 -9.32434 galactic Cas Second-epoch detections are separated by 7.0" 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 | 23:46:07.83 +52:16:11.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:46:07.83 +52:16:11.1: 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:46:07.83 +52:16:11.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.3414* 23 46 07.83 +52 16 11.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.8414,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.3414 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.3414 2461274.8414 14.13 23:45:43.67 +53:35:11.7
113.17096 -8.03523 galactic Cas Second-epoch detections are separated by 6.1" and 7.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:45:43.67 +53:35:11.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:45:43.67 +53:35:11.7: 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:45:43.67 +53:35:11.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.3414* 23 45 43.67 +53 35 11.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.8414,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.3414 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.3414 2461274.8414 14.29 23:32:06.07 +56:48:05.2
112.19314 -4.40701 galactic Cas Second-epoch detections are separated by 5.8" 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 | DocumentRef: VOTx3824380 | 23:32:06.07 +56:48:05.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:32:06.07 +56:48:05.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:32:06.07 +56:48:05.2: 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.3414* 23 32 06.07 +56 48 05.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
DocumentRef: VOTx3824380,2461274.8414,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: VOTx3824380 20260822.3414 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.3414 2461274.8414 14.22 23:56:49.41 +50:59:53.3
114.22895 -10.94841 galactic Cas Second-epoch detections are separated by 5.1" and 7.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: VOTx3608685 | 23:56:49.41 +50:59:53.3 (user input) | (VSX @ VizieR) | (VSX @ VizieR) | (position from user input) J-Ks=0.451+/-0.198 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:56:49.41 +50:59:53.3: 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:56:49.41 +50:59:53.3: 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.3414* 23 56 49.41 +50 59 53.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
DocumentRef: VOTx3608685,2461274.8414,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
DocumentRef: VOTx3608685 20260822.3414 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.3414 2461274.8414 14.19 23:32:03.08 +54:01:00.9
111.33663 -7.05795 galactic Cas Second-epoch detections are separated by 2.5" and 6.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:03.08 +54:01:00.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:32:03.08 +54:01:00.9: 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:32:03.08 +54:01:00.9: 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.3414* 23 32 03.08 +54 01 00.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.8414,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.3414 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.3414 2461274.8414 14.19 23:32:10.67 +52:27:49.1
110.87703 -8.54311 galactic Cas Second-epoch detections are separated by 2.9" 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 | ATO J353.0401+52.4645 | 23:32:10.67 +52:27:49.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:32:10.67 +52:27:49.1: 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:32:10.67 +52:27:49.1: 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.3414* 23 32 10.67 +52 27 49.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
ATO J353.0401+52.4645,2461274.8414,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
ATO J353.0401+52.4645 20260822.3414 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.3414 2461274.8414 14.21 23:14:31.07 +55:22:29.6
109.39586 -4.92909 galactic Cas Second-epoch detections are separated by 1.7" and 7.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:14:31.07 +55:22: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 23:14:31.07 +55:22:29.6: 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:14:31.07 +55:22:29.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.3414* 23 14 31.07 +55 22 29.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.8414,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.3414 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.3414 2461274.8414 14.38 00:05:09.84 +52:39:12.8
115.84504 -9.58030 galactic Cas Second-epoch detections are separated by 6.2" and 7.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:05:09.84 +52:39:12.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 00:05:09.84 +52:39:12.8: 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 00:05:09.84 +52:39:12.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.3414* 00 05 09.84 +52 39 12.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.8414,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.3414 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.3414 2461274.8414 14.26 23:39:36.44 +51:31:04.7
111.70564 -9.78127 galactic Cas Second-epoch detections are separated by 5.3" and 7.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:39:36.44 +51:31:04.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:39:36.44 +51:31:04.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:39:36.44 +51:31:04.7: 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.3414* 23 39 36.44 +51 31 04.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.8414,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.3414 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.3414 2461274.8414 14.29 23:44:14.23 +53:16:50.7
112.87479 -8.27371 galactic Cas Second-epoch detections are separated by 2.5" and 7.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:14.23 +53:16:50.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:14.23 +53:16:50.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:14.23 +53:16:50.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.3414* 23 44 14.23 +53 16 50.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.8414,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.3414 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.3414 2461274.8414 14.35 00:08:08.63 +52:36:24.0
116.28824 -9.70571 galactic Cas Second-epoch detections are separated by 5.4" and 7.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:08:08.63 +52:36:24.0 (user input) | T | P | (position from user input) J-Ks=0.844+/-0.081 (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:08:08.63 +52:36:24.0: 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:08:08.63 +52:36:24.0: 15.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 08 08.63 +52 36 24.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.8414,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.3414 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.3414 2461274.8414 14.13 23:42:58.53 +50:44:45.4
112.00849 -10.66805 galactic Cas Second-epoch detections are separated by 4.5" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:58.53 +50:44:45.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:42:58.53 +50:44:45.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:42:58.53 +50:44:45.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.3414* 23 42 58.53 +50 44 45.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.8414,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.3414 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.3414 2461274.8414 14.36 00:22:06.58 +55:34:33.6
118.76307 -7.05818 galactic Cas Second-epoch detections are separated by 3.1" and 7.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:22:06.58 +55:34:33.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:22:06.58 +55:34:33.6: 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:22:06.58 +55:34:33.6: 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.3414* 00 22 06.58 +55 34 33.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.8414,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.3414 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.3414 2461274.8414 14.18 23:14:38.03 +57:34:53.5
110.22017 -2.88134 galactic Cas Second-epoch detections are separated by 3.0" 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 | 23:14:38.03 +57:34:53.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:14:38.03 +57:34:53.5: 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:14:38.03 +57:34:53.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.3414* 23 14 38.03 +57 34 53.5 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 14.12 23:57:13.90 +51:50:34.6
114.47515 -10.13652 galactic Cas Second-epoch detections are separated by 3.3" and 7.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:57:13.90 +51:50:34.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:57:13.90 +51:50:34.6: 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:57:13.90 +51:50:34.6: 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.3414* 23 57 13.90 +51 50 34.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.8414,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.3414 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.3414 2461274.8414 14.22 23:46:42.52 +51:44:29.6
112.84415 -9.85787 galactic Cas Second-epoch detections are separated by 3.7" and 7.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:46:42.52 +51:44: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 23:46:42.52 +51:44:29.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 23:46:42.52 +51:44:29.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.3414* 23 46 42.52 +51 44 29.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.8414,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.3414 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.3414 2461274.8414 14.34 23:14:21.80 +56:45:14.8
109.88274 -3.63796 galactic Cas Second-epoch detections are separated by 0.6" and 7.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:14:21.80 +56:45:14.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:14:21.80 +56:45:14.8: 15.35 +/- 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:21.80 +56:45:14.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.3414* 23 14 21.80 +56 45 14.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.8414,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.3414 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.3414 2461274.8414 14.32 00:04:54.67 +50:30:18.5
115.40766 -11.68564 galactic Cas Second-epoch detections are separated by 4.9" and 7.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:04:54.67 +50:30:18.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:54.67 +50:30:18.5: 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:04:54.67 +50:30:18.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.3414* 00 04 54.67 +50 30 18.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.8414,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.3414 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.3414 2461274.8414 14.06 23:27:40.60 +53:31:39.7
110.56368 -7.32060 galactic Cas Second-epoch detections are separated by 4.7" and 7.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:40.60 +53:31:39.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:40.60 +53:31:39.7: 14.93 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:27:40.60 +53:31:39.7: 14.92 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.93 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 27 40.60 +53 31 39.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.8414,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.3414 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.3414 2461274.8414 14.10 23:18:10.73 +56:56:38.8
110.43890 -3.64834 galactic Cas Second-epoch detections are separated by 8.3" and 7.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:18:10.73 +56:56:38.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:18:10.73 +56:56:38.8: 15.35 +/- 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:10.73 +56:56:38.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.3414* 23 18 10.73 +56 56 38.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.8414,14.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.26 23:51:14.86 +51:03:18.7
113.37219 -10.69592 galactic Cas Second-epoch detections are separated by 7.3" and 7.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:51:14.86 +51:03:18.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:51:14.86 +51:03:18.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:51:14.86 +51:03:18.7: 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.3414* 23 51 14.86 +51 03 18.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.8414,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.3414 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.3414 2461274.8414 14.16 23:40:56.61 +56:21:53.9
113.23790 -5.17419 galactic Cas Second-epoch detections are separated by 2.8" and 7.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 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.61 +56:21:53.9: 15.07 +/- 0.21 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.61 +56:21:53.9: 15.06 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.07 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 40 56.61 +56 21 53.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 1997804797952790144,2461274.8414,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 1997804797952790144 20260822.3414 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.3414 2461274.8414 14.26 23:29:49.37 +53:55:42.4
110.99506 -7.04100 galactic Cas Second-epoch detections are separated by 5.1" 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 | 23:29:49.37 +53:55: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 23:29:49.37 +53:55:42.4: 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:29:49.37 +53:55:42.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.3414* 23 29 49.37 +53 55 42.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.8414,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.3414 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.3414 2461274.8414 14.20 23:53:54.47 +53:23:43.6
114.31865 -8.51147 galactic Cas Second-epoch detections are separated by 3.5" and 7.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 1945488179277218304 | 23:53:55.99 +53:23:01.4 (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:53:54.47 +53:23:43.6: 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:53:54.47 +53:23:43.6: 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.3414* 23 53 54.47 +53 23 43.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
Gaia DR3 1945488179277218304,2461274.8414,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
Gaia DR3 1945488179277218304 20260822.3414 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.3414 2461274.8414 14.16 23:32:52.68 +53:44:56.8
111.37184 -7.35008 galactic Cas Second-epoch detections are separated by 5.8" 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 | ATO J353.2058+53.7612 | 23:32:51.39 +53:45:34.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:32:52.68 +53:44:56.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:32:52.68 +53:44:56.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.3414* 23 32 52.68 +53 44 56.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
ATO J353.2058+53.7612,2461274.8414,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
ATO J353.2058+53.7612 20260822.3414 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.3414 2461274.8414 14.22 00:07:27.37 +50:53:53.2
115.88381 -11.37077 galactic Cas Second-epoch detections are separated by 8.9" and 7.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:07:27.37 +50:53:53.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:07:27.37 +50:53:53.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:07:27.37 +50:53:53.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.3414* 00 07 27.37 +50 53 53.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.8414,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.3414 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.3414 2461274.8414 14.12 23:19:44.60 +56:11:03.8
110.37445 -4.43542 galactic Cas Second-epoch detections are separated by 3.1" 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 | 23:19:44.60 +56:11:03.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:19:44.60 +56:11:03.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:19:44.60 +56:11:03.8: 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.3414* 23 19 44.60 +56 11 03.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.8414,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.3414 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.3414 2461274.8414 14.12 23:28:02.60 +55:38:41.1
111.29464 -5.33138 galactic Cas Second-epoch detections are separated by 3.6" and 7.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:28:02.60 +55:38:41.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:28:02.60 +55:38:41.1: 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:28:02.60 +55:38:41.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.3414* 23 28 02.60 +55 38 41.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.8414,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.3414 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.3414 2461274.8414 14.12 00:10:19.91 +51:21:36.9
116.41609 -10.99070 galactic Cas Second-epoch detections are separated by 7.9" and 7.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:10:19.91 +51:21:36.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:10:19.91 +51:21:36.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:10:19.91 +51:21:36.9: 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.3414* 00 10 19.91 +51 21 36.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 14.16 00:08:56.57 +52:27:44.6
116.38518 -9.86836 galactic Cas Second-epoch detections are separated by 4.2" and 7.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:56.57 +52:27:44.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:08:56.57 +52:27:44.6: 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:08:56.57 +52:27:44.6: 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.3414* 00 08 56.57 +52 27 44.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.8414,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.3414 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.3414 2461274.8414 14.21 23:50:41.11 +50:27:38.6
113.14097 -11.25250 galactic Cas Second-epoch detections are separated by 2.5" and 7.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:50:41.11 +50:27:38.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:50:41.11 +50:27:38.6: 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:50:41.11 +50:27:38.6: 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.3414* 23 50 41.11 +50 27 38.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.8414,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.3414 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.3414 2461274.8414 14.05 23:31:16.87 +51:15:22.6
110.36797 -9.64956 galactic Cas Second-epoch detections are separated by 8.2" and 7.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:31:16.87 +51:15: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:31:16.87 +51:15:22.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 23:31:16.87 +51:15:22.6: 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.3414* 23 31 16.87 +51 15 22.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.8414,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.3414 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.3414 2461274.8414 14.27 00:05:42.71 +50:40:43.5
115.56742 -11.53800 galactic Cas Second-epoch detections are separated by 1.1" and 7.6 pix
The object was found in VSX19" Gaia DR3 395477603620972544
Type: ROT
# Max. Min./Amp. JD0 Period
15.090 G 15.130 G 8.231500000000 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 00:05:42.71 +50:40:43.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 00:05:42.71 +50:40:43.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.3414* 00 05 42.71 +50 40 43.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 395477603620972544,2461274.8414,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
Gaia DR3 395477603620972544 20260822.3414 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.3414 2461274.8414 14.13 23:15:57.58 +56:35:13.7
110.02656 -3.87326 galactic Cas Second-epoch detections are separated by 2.7" 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 | 23:15:57.58 +56:35:13.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:57.58 +56:35:13.7: 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:15:57.58 +56:35:13.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.3414* 23 15 57.58 +56 35 13.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.8414,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.3414 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.3414 2461274.8414 14.08 23:59:31.01 +54:09:43.4
115.30143 -7.93867 galactic Cas Second-epoch detections are separated by 3.0" and 7.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:59:31.01 +54:09:43.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:59:31.01 +54:09:43.4: 15.69 +/- 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:59:31.01 +54:09:43.4: 15.14 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.69 +/- 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.3414* 23 59 31.01 +54 09 43.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.8414,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.3414 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.3414 2461274.8414 14.15 23:56:35.62 +53:30:25.1
114.73782 -8.48997 galactic Cas Second-epoch detections are separated by 8.9" and 7.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:56:35.62 +53: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:56:35.62 +53:30:25.1: 15.61 +/- 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:56:35.62 +53:30:25.1: 15.01 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.61 +/- 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.3414* 23 56 35.62 +53 30 25.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.8414,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.3414 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.3414 2461274.8414 14.19 00:04:43.27 +51:19:46.0
115.53175 -10.86982 galactic Cas Second-epoch detections are separated by 2.1" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:43.27 +51:19:46.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:04:43.27 +51:19:46.0: 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:04:43.27 +51:19:46.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.3414* 00 04 43.27 +51 19 46.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.8414,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.3414 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.3414 2461274.8414 14.29 00:03:42.47 +51:10:37.1
115.34426 -10.99024 galactic Cas Second-epoch detections are separated by 5.6" and 7.3 pix
The object was found in VSX24" ZTF J000342.77+511101.2
Type: BY
# Max. Min./Amp. JD0 Period
16.873 r Y 0.067 r 2458270.92130 1.548432600000
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:03:42.47 +51:10:37.1: 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 00:03:42.47 +51:10:37.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.3414* 00 03 42.47 +51 10 37.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
ZTF J000342.77+511101.2,2461274.8414,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
ZTF J000342.77+511101.2 20260822.3414 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.3414 2461274.8414 14.17 00:13:35.89 +52:59:14.9
117.17512 -9.46080 galactic Cas Second-epoch detections are separated by 8.0" and 7.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:13:35.89 +52:59:14.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:13:35.89 +52:59:14.9: 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:13:35.89 +52:59:14.9: 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.3414* 00 13 35.89 +52 59 14.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.8414,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.3414 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.3414 2461274.8414 14.11 23:53:57.85 +51:34:47.9
113.91495 -10.28274 galactic Cas Second-epoch detections are separated by 6.2" and 7.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:53:57.85 +51:34:47.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:57.85 +51:34:47.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 23:53:57.85 +51:34:47.9: 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.3414* 23 53 57.85 +51 34 47.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 13.97 23:27:49.24 +56:49:27.4
111.64191 -4.20334 galactic Cas Second-epoch detections are separated by 7.2" and 7.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:27:49.24 +56:49: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:27:49.24 +56:49:27.4: 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:27:49.24 +56:49:27.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.3414* 23 27 49.24 +56 49 27.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.8414,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
target 20260822.3414 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.3414 2461274.8414 14.18 00:12:06.51 +52:49:27.0
116.92495 -9.58826 galactic Cas Second-epoch detections are separated by 4.5" and 7.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:12:06.51 +52:49:27.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:06.51 +52:49:27.0: 15.56 +/- 0.33 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:12:06.51 +52:49:27.0: 15.00 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.56 +/- 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.3414* 00 12 06.51 +52 49 27.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.8414,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.3414 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.3414 2461274.8414 13.96 23:27:07.82 +56:39:13.1
111.49727 -4.33476 galactic Cas Second-epoch detections are separated by 8.6" and 7.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:07.82 +56:39:13.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:27:07.82 +56:39:13.1: 15.33 +/- 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:27:07.82 +56:39:13.1: 14.78 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.33 +/- 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.3414* 23 27 07.82 +56 39 13.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
target,2461274.8414,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.3414 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.3414 2461274.8414 14.00 23:52:03.54 +52:58:06.0
113.94763 -8.86449 galactic Cas Second-epoch detections are separated by 8.1" and 7.3 pix
The object was found in VSX11" Gaia DR3 1945338473895124736
Type: ROT
# Max. Min./Amp. JD0 Period
15.890 G 15.920 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:52:03.54 +52:58:06.0: 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:52:03.54 +52:58:06.0: 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.3414* 23 52 03.54 +52 58 06.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
Gaia DR3 1945338473895124736,2461274.8414,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 1945338473895124736 20260822.3414 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.3414 2461274.8414 14.19 00:03:15.67 +54:09:51.9
115.84473 -8.04306 galactic Cas Second-epoch detections are separated by 1.9" and 7.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:03:15.67 +54:09:51.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:03:15.67 +54:09:51.9: 15.34 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:03:15.67 +54:09:51.9: 15.04 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.34 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 03 15.67 +54 09 51.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.8414,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.3414 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.3414 2461274.8414 13.89 23:17:33.23 +56:09:21.6
110.07832 -4.35485 galactic Cas Second-epoch detections are separated by 4.0" and 7.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 1997177079892670336 | 23:17:30.28 +56:08:42.4 (Gaia DR3) | E (local) | 6.931300000000 (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:17:33.23 +56:09:21.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.23 +56:09:21.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.3414* 23 17 33.23 +56 09 21.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
Gaia DR3 1997177079892670336,2461274.8414,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
Gaia DR3 1997177079892670336 20260822.3414 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.3414 2461274.8414 14.11 00:07:29.71 +51:05:34.7
115.92435 -11.17991 galactic Cas Second-epoch detections are separated by 0.8" and 7.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 395329719307674240 | 00:07:31.09 +51:06:18.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 00:07:29.71 +51:05:34.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:07:29.71 +51:05:34.7: 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.3414* 00 07 29.71 +51 05 34.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 395329719307674240,2461274.8414,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
Gaia DR3 395329719307674240 20260822.3414 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.3414 2461274.8414 14.28 00:22:49.35 +53:31:12.0
118.63143 -9.11264 galactic Cas Second-epoch detections are separated by 5.7" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:49.35 +53:31:12.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:22:49.35 +53:31:12.0: 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:22:49.35 +53:31:12.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.3414* 00 22 49.35 +53 31 12.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.8414,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.3414 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.3414 2461274.8414 13.97 23:23:21.75 +57:09:34.2
111.17632 -3.68831 galactic Cas Second-epoch detections are separated by 5.9" 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 | DocumentRef: VOTx1638605 | 23:23:21.75 +57:09:34.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:23:21.75 +57:09:34.2: 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:23:21.75 +57:09:34.2: 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.3414* 23 23 21.75 +57 09 34.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: VOTx1638605,2461274.8414,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: VOTx1638605 20260822.3414 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.3414 2461274.8414 14.12 23:32:21.84 +56:20:21.3
112.08750 -4.85850 galactic Cas Second-epoch detections are separated by 3.5" and 6.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:21.84 +56:20:21.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:32:21.84 +56:20:21.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:32:21.84 +56:20:21.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.3414* 23 32 21.84 +56 20 21.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
target,2461274.8414,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.3414 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.3414 2461274.8414 14.03 00:08:06.07 +51:46:30.8
116.13824 -10.52397 galactic Cas Second-epoch detections are separated by 5.7" and 7.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:08:06.07 +51:46:30.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 00:08:06.07 +51:46:30.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 00:08:06.07 +51:46:30.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.3414* 00 08 06.07 +51 46 30.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.8414,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.3414 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.3414 2461274.8414 13.94 23:27:58.34 +57:50:03.6
111.98319 -3.25221 galactic Cas Second-epoch detections are separated by 8.6" and 7.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:58.34 +57:50: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:27:58.34 +57:50:03.6: 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:27:58.34 +57:50:03.6: 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.3414* 23 27 58.34 +57 50 03.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.8414,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.3414 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.3414 2461274.8414 14.01 23:16:49.00 +56:44:36.0
110.19294 -3.76982 galactic Cas Second-epoch detections are separated by 2.8" and 7.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.00 +56:44:36.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:49.00 +56:44:36.0: 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.00 +56:44:36.0: 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.3414* 23 16 49.00 +56 44 36.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
target,2461274.8414,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.3414 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.3414 2461274.8414 14.07 00:05:25.10 +52:54:41.6
115.93058 -9.33347 galactic Cas Second-epoch detections are separated by 5.7" and 7.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:05:25.10 +52:54: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 00:05:25.10 +52:54:41.6: 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:05:25.10 +52:54:41.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.3414* 00 05 25.10 +52 54 41.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.8414,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.3414 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.3414 2461274.8414 13.97 00:03:44.07 +50:50:17.0
115.28369 -11.32393 galactic Cas Second-epoch detections are separated by 6.2" and 7.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:03:44.07 +50:50:17.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:03:44.07 +50:50:17.0: 15.80 +/- 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:44.07 +50:50:17.0: 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.3414* 00 03 44.07 +50 50 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
target,2461274.8414,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
target 20260822.3414 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.3414 2461274.8414 14.01 23:23:13.51 +56:57:50.2
111.09310 -3.86635 galactic Cas Second-epoch detections are separated by 8.7" and 7.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.51 +56:57: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:23:13.51 +56:57:50.2: 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:23:13.51 +56:57:50.2: 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.3414* 23 23 13.51 +56 57 50.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.8414,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.3414 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.3414 2461274.8414 14.10 23:58:50.68 +54:12:44.4
115.21454 -7.86947 galactic Cas Second-epoch detections are separated by 1.0" and 7.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 J359.7265+54.2052 | 23:58:50.68 +54:12:44.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:58:50.68 +54:12:44.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 23:58:50.68 +54:12:44.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.3414* 23 58 50.68 +54 12 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
ATO J359.7265+54.2052,2461274.8414,14.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.7265+54.2052 20260822.3414 14.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.04 23:34:06.86 +54:09:21.7
111.66949 -7.01623 galactic Cas Second-epoch detections are separated by 7.0" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:06.86 +54:09:21.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:06.86 +54:09: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:34:06.86 +54:09:21.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.3414* 23 34 06.86 +54 09 21.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.8414,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.3414 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.3414 2461274.8414 14.04 00:09:16.55 +53:22:03.5
116.58740 -8.98393 galactic Cas Second-epoch detections are separated by 4.2" and 7.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:09:16.55 +53:22:03.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:09:16.55 +53:22:03.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:09:16.55 +53:22:03.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.3414* 00 09 16.55 +53 22 03.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.8414,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.3414 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.3414 2461274.8414 13.98 23:22:22.34 +51:21:56.1
109.06986 -9.09308 galactic And Second-epoch detections are separated by 8.6" 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 | Gaia DR3 1991541945358078592 | 23:22:25.61 +51:21:43.6 (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:22:22.34 +51:21:56.1: 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.34 +51:21:56.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.3414* 23 22 22.34 +51 21 56.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
Gaia DR3 1991541945358078592,2461274.8414,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 1991541945358078592 20260822.3414 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.3414 2461274.8414 14.01 23:40:56.86 +54:14:01.2
112.65735 -7.22587 galactic Cas Second-epoch detections are separated by 6.2" and 6.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:40:56.86 +54:14:01.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:40:56.86 +54:14:01.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:40:56.86 +54:14:01.2: 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.3414* 23 40 56.86 +54 14 01.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.8414,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.3414 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.3414 2461274.8414 14.07 23:48:01.71 +49:59:48.2
112.60547 -11.59937 galactic Cas Second-epoch detections are separated by 4.2" and 7.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:01.71 +49:59:48.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:48:01.71 +49:59:48.2: 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:48:01.71 +49:59:48.2: 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.3414* 23 48 01.71 +49 59 48.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.8414,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.3414 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.3414 2461274.8414 13.91 23:17:49.65 +51:39:55.5
108.50550 -8.56503 galactic And Second-epoch detections are separated by 6.1" and 7.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J349.4612+51.6677 | 23:17:49.65 +51:39:55.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 23:17:49.65 +51:39:55.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:17:49.65 +51:39:55.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.3414* 23 17 49.65 +51 39 55.5 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 J349.4612+51.6677,2461274.8414,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 J349.4612+51.6677 20260822.3414 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.3414 2461274.8414 13.93 00:17:10.10 +50:18:51.7
117.34688 -12.18539 galactic Cas Second-epoch detections are separated by 3.6" and 7.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:17:10.10 +50:18:51.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 00:17:10.10 +50:18:51.7: 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:17:10.10 +50:18:51.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.3414* 00 17 10.10 +50 18 51.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.8414,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.3414 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.3414 2461274.8414 13.89 23:27:41.87 +53:31:05.3
110.56359 -7.33066 galactic Cas Second-epoch detections are separated by 3.8" 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 | 23:27:41.87 +53:31:05.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:41.87 +53:31:05.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:27:41.87 +53:31:05.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.3414* 23 27 41.87 +53 31 05.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.8414,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.3414 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.3414 2461274.8414 14.01 23:57:58.05 +50:00:24.8
114.19577 -11.95569 galactic Cas Second-epoch detections are separated by 2.3" and 7.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:57:58.05 +50:00:24.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:57:58.05 +50:00:24.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:57:58.05 +50:00:24.8: 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.3414* 23 57 58.05 +50 00 24.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.8414,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.3414 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.3414 2461274.8414 14.04 00:00:45.62 +52:08:08.6
115.07610 -9.96135 galactic Cas Second-epoch detections are separated by 7.0" and 7.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:45.62 +52:08:08.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:00:45.62 +52:08:08.6: 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:00:45.62 +52:08:08.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.3414* 00 00 45.62 +52 08 08.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.8414,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.3414 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.3414 2461274.8414 13.99 00:17:18.55 +50:49:48.3
117.44081 -11.67743 galactic Cas Second-epoch detections are separated by 1.8" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:17:18.55 +50:49:48.3 (user input) | T | P | (position from user input) SpType: F7 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:17:18.55 +50:49:48.3: 15.16 +/- 0.25 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:17:18.55 +50:49:48.3: 14.91 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.16 +/- 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.3414* 00 17 18.55 +50 49 48.3 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 14.01 23:30:46.14 +55:32:54.9
111.63167 -5.54330 galactic Cas Second-epoch detections are separated by 4.7" 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 | 23:30:46.14 +55:32:54.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:30:46.14 +55:32:54.9: 15.43 +/- 0.34 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:30:46.14 +55:32:54.9: 14.99 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.43 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 30 46.14 +55 32 54.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.8414,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.3414 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.3414 2461274.8414 13.96 00:20:11.77 +56:00:27.7
118.54545 -6.59774 galactic Cas Second-epoch detections are separated by 2.4" and 7.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:20:11.77 +56:00:27.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 00:20:11.77 +56:00:27.7: 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:20:11.77 +56:00:27.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.3414* 00 20 11.77 +56 00 27.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.8414,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.3414 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.3414 2461274.8414 14.12 23:23:07.72 +52:03:07.7
109.41747 -8.48721 galactic And Second-epoch detections are separated by 5.6" 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 | DocumentRef: VOTx2964285 | 23:23:07.72 +52:03:07.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:23:07.72 +52:03:07.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:23:07.72 +52:03:07.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.3414* 23 23 07.72 +52 03 07.7 14.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
DocumentRef: VOTx2964285,2461274.8414,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
DocumentRef: VOTx2964285 20260822.3414 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.3414 2461274.8414 14.02 23:49:39.37 +51:05:46.5
113.13510 -10.59652 galactic Cas Second-epoch detections are separated by 8.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 | 23:49:39.37 +51:05:46.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:49:39.37 +51:05:46.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 23:49:39.37 +51:05:46.5: 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.3414* 23 49 39.37 +51 05 46.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.8414,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.3414 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.3414 2461274.8414 14.05 00:15:17.11 +53:44:11.7
117.53724 -8.75606 galactic Cas Second-epoch detections are separated by 2.8" and 7.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:17.11 +53:44:11.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 00:15:17.11 +53:44:11.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 00:15:17.11 +53:44:11.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.3414* 00 15 17.11 +53 44 11.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.8414,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.3414 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.3414 2461274.8414 13.97 23:14:37.48 +56:41:29.6
109.89321 -3.70930 galactic Cas Second-epoch detections are separated by 7.5" 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 | Gaia DR3 2009253978172989696 | 23:14:36.85 +56:42:07.4 (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:14:37.48 +56:41:29.6: 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:14:37.48 +56:41:29.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.3414* 23 14 37.48 +56 41 29.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
Gaia DR3 2009253978172989696,2461274.8414,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
Gaia DR3 2009253978172989696 20260822.3414 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.3414 2461274.8414 13.98 00:24:08.78 +50:22:31.0
118.48506 -12.26068 galactic Cas Second-epoch detections are separated by 5.5" and 7.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:24:08.78 +50:22:31.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:24:08.78 +50:22:31.0: 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:08.78 +50:22:31.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.3414* 00 24 08.78 +50 22 31.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
target,2461274.8414,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.3414 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.3414 2461274.8414 14.04 00:10:42.07 +53:58:57.0
116.89885 -8.41138 galactic Cas Second-epoch detections are separated by 1.0" and 7.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:10:42.07 +53:58:57.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:10:42.07 +53:58:57.0: 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:10:42.07 +53:58:57.0: 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.3414* 00 10 42.07 +53 58 57.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
target,2461274.8414,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.3414 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.3414 2461274.8414 13.88 23:26:51.29 +50:21:09.2
109.40313 -10.28413 galactic And Second-epoch detections are separated by 6.3" and 7.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.7300+50.3490 | 23:26:51.29 +50:21:09.2 (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.29 +50:21:09.2: 15.45 +/- 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:26:51.29 +50:21:09.2: 14.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.45 +/- 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.3414* 23 26 51.29 +50 21 09.2 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.8414,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
ATO J351.7300+50.3490 20260822.3414 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.3414 2461274.8414 14.10 23:30:06.75 +51:01:43.6
110.11933 -9.80862 galactic Cas Second-epoch detections are separated by 3.2" and 7.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:06.75 +51:01:43.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:30:06.75 +51:01:43.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:30:06.75 +51:01:43.6: 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.3414* 23 30 06.75 +51 01 43.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.8414,14.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.84 23:28:15.12 +51:28:51.5
109.98473 -9.28747 galactic Cas Second-epoch detections are separated by 5.9" and 7.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:28:15.12 +51:28: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 23:28:15.12 +51:28:51.5: 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.12 +51:28:51.5: 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.3414* 23 28 15.12 +51 28 51.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.8414,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.3414 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.3414 2461274.8414 14.03 00:26:19.09 +55:49:26.5
119.38354 -6.87456 galactic Cas Second-epoch detections are separated by 5.7" and 7.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:26:19.09 +55:49: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:26:19.09 +55:49:26.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 00:26:19.09 +55:49:26.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.3414* 00 26 19.09 +55 49 26.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.8414,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.3414 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.3414 2461274.8414 13.84 23:41:14.04 +49:49:36.9
111.48255 -11.47773 galactic Cas Second-epoch detections are separated by 5.6" and 7.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: VOTx3803400 | 23:41:14.04 +49:49:36.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:41:14.04 +49:49:36.9: 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.04 +49:49:36.9: 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.3414* 23 41 14.04 +49 49 36.9 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3803400,2461274.8414,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
DocumentRef: VOTx3803400 20260822.3414 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.3414 2461274.8414 13.71 23:46:36.23 +53:17:01.6
113.22121 -8.36118 galactic Cas Second-epoch detections are separated by 1.5" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:46:36.23 +53:17:01.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:46:36.23 +53:17:01.6: 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:46:36.23 +53:17:01.6: 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.3414* 23 46 36.23 +53 17 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
target,2461274.8414,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.3414 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.3414 2461274.8414 13.93 23:17:23.23 +53:56:34.4
109.26371 -6.41416 galactic Cas Second-epoch detections are separated by 3.1" and 7.0 pix
The object was found in VSX25" 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:23.23 +53:56:34.4: 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:23.23 +53:56:34.4: 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.3414* 23 17 23.23 +53 56 34.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1995953426527758208,2461274.8414,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1995953426527758208 20260822.3414 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.3414 2461274.8414 14.02 23:30:40.99 +51:38:18.3
110.39837 -9.25737 galactic Cas Second-epoch detections are separated by 7.7" and 7.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:30:40.99 +51:38:18.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:40.99 +51:38:18.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:30:40.99 +51:38:18.3: 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.3414* 23 30 40.99 +51 38 18.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.8414,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.3414 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.3414 2461274.8414 13.88 23:43:08.28 +54:27:23.6
113.02741 -7.09648 galactic Cas Second-epoch detections are separated by 2.3" and 7.3 pix
The object was found in VSX22" Gaia DR3 1994175447507020032
Type:
# Max. Min./Amp. JD0 Period
15.090 G 15.130 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:43:08.28 +54:27:23.6: 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:43:08.28 +54:27:23.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.3414* 23 43 08.28 +54 27 23.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1994175447507020032,2461274.8414,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
Gaia DR3 1994175447507020032 20260822.3414 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.3414 2461274.8414 13.88 23:15:32.01 +55:29:11.5
109.57137 -4.87770 galactic Cas Second-epoch detections are separated by 5.9" and 6.9 pix
The object was found in VSX 9" 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:32.01 +55:29:11.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:15:32.01 +55:29:11.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.3414* 23 15 32.01 +55 29 11.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
Gaia DR3 1997079601312812032,2461274.8414,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
Gaia DR3 1997079601312812032 20260822.3414 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.3414 2461274.8414 13.91 23:52:37.64 +53:51:51.1
114.23875 -8.01196 galactic Cas Second-epoch detections are separated by 8.4" and 7.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: VOTx3842776 | 23:52:37.64 +53:51:51.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:52:37.64 +53:51:51.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 23:52:37.64 +53:51:51.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.3414* 23 52 37.64 +53 51 51.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: VOTx3842776,2461274.8414,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
DocumentRef: VOTx3842776 20260822.3414 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.3414 2461274.8414 13.86 23:55:32.82 +51:24:52.5
114.12194 -10.49858 galactic Cas Second-epoch detections are separated by 0.9" and 7.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: VOTx3841726 | 23:55:32.82 +51:24:52.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:55:32.82 +51:24:52.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 23:55:32.82 +51:24:52.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.3414* 23 55 32.82 +51 24 52.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: VOTx3841726,2461274.8414,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: VOTx3841726 20260822.3414 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.3414 2461274.8414 13.79 23:50:29.86 +53:22:50.3
113.81495 -8.40894 galactic Cas Second-epoch detections are separated by 4.8" and 7.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:50:29.86 +53:22:50.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:50:29.86 +53:22:50.3: 14.86 +/- 0.18 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:50:29.86 +53:22:50.3: 15.13 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.86 +/- 0.18
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 50 29.86 +53 22 50.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.8414,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.3414 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.3414 2461274.8414 13.89 23:41:48.59 +51:06:39.4
111.92825 -10.26713 galactic Cas Second-epoch detections are separated by 5.4" 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 | target | 23:41:48.59 +51:06:39.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:48.59 +51:06:39.4: 15.66 +/- 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:41:48.59 +51:06:39.4: 15.03 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.66 +/- 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.3414* 23 41 48.59 +51 06 39.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.8414,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.3414 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.3414 2461274.8414 13.79 23:15:41.40 +52:13:42.3
108.40051 -7.92109 galactic And Second-epoch detections are separated by 1.3" 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 | 23:15:41.40 +52:13:42.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:41.40 +52:13:42.3: 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:41.40 +52:13:42.3: 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.3414* 23 15 41.40 +52 13 42.3 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.8414,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.3414 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.3414 2461274.8414 13.88 23:30:40.76 +54:19:12.6
111.23787 -6.70771 galactic Cas Second-epoch detections are separated by 5.0" 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 | 23:30:40.76 +54:19:12.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:30:40.76 +54:19:12.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:30:40.76 +54:19:12.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.3414* 23 30 40.76 +54 19 12.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 13.92 00:13:02.17 +53:50:14.5
117.21967 -8.60793 galactic Cas Second-epoch detections are separated by 6.0" and 7.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:02.17 +53:50:14.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:02.17 +53:50:14.5: 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:13:02.17 +53:50:14.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.3414* 00 13 02.17 +53 50 14.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.8414,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.3414 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.3414 2461274.8414 13.85 23:14:33.27 +57:05:59.1
110.03383 -3.32587 galactic Cas Second-epoch detections are separated by 7.3" 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 | 23:14:33.27 +57:05: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 23:14:33.27 +57:05:59.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:33.27 +57:05:59.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.3414* 23 14 33.27 +57 05 59.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.8414,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 13.89 23:45:02.68 +50:35:00.8
112.28712 -10.91088 galactic Cas Second-epoch detections are separated by 3.5" and 7.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:45:02.68 +50:35:00.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:45:02.68 +50:35:00.8: 15.05 +/- 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:45:02.68 +50:35:00.8: 14.88 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.05 +/- 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.3414* 23 45 02.68 +50 35 00.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.8414,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.3414 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.3414 2461274.8414 13.81 23:21:56.34 +51:25:10.8
109.02429 -9.01912 galactic And Second-epoch detections are separated by 8.0" and 7.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:21:56.34 +51:25:10.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:21:56.34 +51:25:10.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:21:56.34 +51:25:10.8: 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.3414* 23 21 56.34 +51 25 10.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.8414,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 13.81 23:58:27.60 +52:16:15.8
114.75360 -9.75744 galactic Cas Second-epoch detections are separated by 6.7" and 7.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:58:27.60 +52:16:15.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:58:27.60 +52:16:15.8: 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:58:27.60 +52:16:15.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.3414* 23 58 27.60 +52 16 15.8 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 13.89 00:18:54.23 +51:50:01.8
117.82708 -10.71515 galactic Cas Second-epoch detections are separated by 5.3" and 7.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 J004.7126+51.8274 | 00:18:54.23 +51:50:01.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 00:18:54.23 +51:50: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 00:18:54.23 +51:50:01.8: 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.3414* 00 18 54.23 +51 50 01.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J004.7126+51.8274,2461274.8414,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 J004.7126+51.8274 20260822.3414 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.3414 2461274.8414 13.73 23:45:25.99 +54:37:38.3
113.39593 -7.01777 galactic Cas Second-epoch detections are separated by 7.3" and 7.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:45:25.99 +54:37:38.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:45:25.99 +54:37:38.3: 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:45:25.99 +54:37:38.3: 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.3414* 23 45 25.99 +54 37 38.3 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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
target 20260822.3414 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.3414 2461274.8414 13.99 23:37:01.45 +49:45:09.2
110.79608 -11.35765 galactic And Second-epoch detections are separated by 7.5" and 7.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 1943690821359753472 | 23:37:04.66 +49:45:13.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:37:01.45 +49:45:09.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:37:01.45 +49:45:09.2: 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.3414* 23 37 01.45 +49 45 09.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
Gaia DR3 1943690821359753472,2461274.8414,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
Gaia DR3 1943690821359753472 20260822.3414 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.3414 2461274.8414 13.79 23:22:50.94 +51:55:48.4
109.33471 -8.58744 galactic And Second-epoch detections are separated by 4.3" 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 | target | 23:22:50.94 +51:55: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 23:22:50.94 +51:55:48.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 23:22:50.94 +51:55:48.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.3414* 23 22 50.94 +51 55 48.4 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.8414,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.3414 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.3414 2461274.8414 13.75 23:54:22.54 +51:29:59.1
113.96010 -10.37524 galactic Cas Second-epoch detections are separated by 6.5" and 7.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:54:22.54 +51:29: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 23:54:22.54 +51:29:59.1: 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:54:22.54 +51:29:59.1: 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.3414* 23 54 22.54 +51 29 59.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.8414,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.80 00:09:04.15 +51:44:04.5
116.28149 -10.58924 galactic Cas Second-epoch detections are separated by 7.1" and 7.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:04.15 +51:44: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 00:09:04.15 +51:44:04.5: 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.15 +51:44:04.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.3414* 00 09 04.15 +51 44 04.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.8414,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.3414 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.3414 2461274.8414 13.89 23:45:38.77 +51:01:03.5
112.49439 -10.51593 galactic Cas Second-epoch detections are separated by 3.2" and 7.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:45:38.77 +51:01:03.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:45:38.77 +51:01:03.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:45:38.77 +51:01:03.5: 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.3414* 23 45 38.77 +51 01 03.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.8414,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.3414 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.3414 2461274.8414 13.85 23:18:52.43 +54:59:00.9
109.83759 -5.51754 galactic Cas Second-epoch detections are separated by 7.0" 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 | target | 23:18:52.43 +54:59:00.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:18:52.43 +54:59:00.9: 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:18:52.43 +54:59:00.9: 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.3414* 23 18 52.43 +54 59 00.9 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 13.88 00:02:20.16 +54:17:37.2
115.73539 -7.89056 galactic Cas Second-epoch detections are separated by 1.9" and 7.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ZTF J000223.08+541740.1 | 00:02:23.38 +54:17:23.5 (Gaia DR3) | EW (local) | 0.530873600000 (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:02:20.16 +54:17:37.2: 15.18 +/- 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:02:20.16 +54:17:37.2: 15.14 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.18 +/- 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.3414* 00 02 20.16 +54 17 37.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
ZTF J000223.08+541740.1,2461274.8414,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
ZTF J000223.08+541740.1 20260822.3414 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.3414 2461274.8414 13.77 00:02:46.70 +51:31:11.0
115.26517 -10.62622 galactic Cas Second-epoch detections are separated by 7.3" and 7.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: VOTx583117 | 00:02:46.70 +51:31: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:02:46.70 +51:31:11.0: 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:02:46.70 +51:31:11.0: 15.02 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.02 +/- 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.3414* 00 02 46.70 +51 31 11.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
DocumentRef: VOTx583117,2461274.8414,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
DocumentRef: VOTx583117 20260822.3414 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.3414 2461274.8414 13.67 23:14:05.90 +55:29:19.6
109.38230 -4.80130 galactic Cas Second-epoch detections are separated by 3.5" and 7.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 J348.5326+55.4819 | 23:14:05.90 +55:29:19.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:14:05.90 +55:29:19.6: 14.54 +/- 0.16 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:14:05.90 +55:29:19.6: 14.74 +/- 0.33 detection
Forced photometry reference-image weighted average: 14.58 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 14 05.90 +55 29 19.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
ATO J348.5326+55.4819,2461274.8414,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J348.5326+55.4819 20260822.3414 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.70 23:27:03.80 +49:50:11.8
109.26411 -10.78276 galactic And Second-epoch detections are separated by 5.3" and 7.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:03.80 +49:50:11.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:27:03.80 +49:50:11.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:27:03.80 +49:50:11.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.3414* 23 27 03.80 +49 50 11.8 13.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.77 23:57:16.88 +54:23:51.7
115.02818 -7.64086 galactic Cas Second-epoch detections are separated by 3.9" and 7.4 pix
The object was found in VSX18" Gaia DR3 1993606244081527168
Type: E
# Max. Min./Amp. JD0 Period
16.910 G 17.180 G 1.462400000000 F
NOTE: the measured mag 13.77 is inconsistent with the record above (maximum 16.91), and the brighter VSX variable Gaia DR3 1993606244081529472 at 23" may be the actual counterpart.
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:16.88 +54:23:51.7: 15.49 +/- 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:57:16.88 +54:23:51.7: 15.06 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.49 +/- 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.3414* 23 57 16.88 +54 23 51.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
Gaia DR3 1993606244081527168,2461274.8414,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
Gaia DR3 1993606244081527168 20260822.3414 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.3414 2461274.8414 13.62 23:17:33.82 +53:32:22.2
109.14323 -6.80027 galactic Cas Second-epoch detections are separated by 8.2" 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: VOTx664252 | 23:17:33.82 +53:32:22.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:17:33.82 +53:32:22.2: 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:33.82 +53:32:22.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.3414* 23 17 33.82 +53 32 22.2 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx664252,2461274.8414,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: VOTx664252 20260822.3414 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.3414 2461274.8414 13.66 23:24:12.68 +57:04:12.5
111.25539 -3.81093 galactic Cas Second-epoch detections are separated by 1.2" and 7.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: VOTx1066234 | 23:24:12.68 +57:04:12.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:24:12.68 +57:04:12.5: 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:24:12.68 +57:04:12.5: 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.3414* 23 24 12.68 +57 04 12.5 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx1066234,2461274.8414,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1066234 20260822.3414 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.64 00:25:26.06 +54:36:46.7
119.13502 -8.06696 galactic Cas Second-epoch detections are separated by 6.8" and 7.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:25:26.06 +54:36:46.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 00:25:26.06 +54:36:46.7: 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:25:26.06 +54:36:46.7: 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.3414* 00 25 26.06 +54 36 46.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
target,2461274.8414,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.3414 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.3414 2461274.8414 13.77 23:20:50.41 +55:51:37.3
110.40629 -4.79245 galactic Cas Second-epoch detections are separated by 6.0" and 7.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:20:50.41 +55:51: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:20:50.41 +55:51:37.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 23:20:50.41 +55:51:37.3: 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.3414* 23 20 50.41 +55 51 37.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.8414,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.3414 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.3414 2461274.8414 13.78 00:30:57.48 +55:56:08.1
120.04627 -6.82138 galactic Cas Second-epoch detections are separated by 6.3" 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 | DocumentRef: VOTx967536 | 00:30:57.48 +55:56:08.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:30:57.48 +55:56:08.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 00:30:57.48 +55:56:08.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.3414* 00 30 57.48 +55 56 08.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
DocumentRef: VOTx967536,2461274.8414,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
DocumentRef: VOTx967536 20260822.3414 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.3414 2461274.8414 13.87 00:00:55.76 +53:32:19.1
115.38215 -8.59109 galactic Cas Second-epoch detections are separated by 6.1" and 7.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:00:55.76 +53:32:19.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:00:55.76 +53:32:19.1: 15.79 +/- 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:55.76 +53:32:19.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.3414* 00 00 55.76 +53 32 19.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.8414,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.3414 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.3414 2461274.8414 13.65 00:20:05.82 +56:06:38.9
118.54428 -6.49371 galactic Cas Second-epoch detections are separated by 7.3" 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:20:05.82 +56: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 00:20:05.82 +56:06:38.9: 15.56 +/- 0.34 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:20:05.82 +56:06:38.9: 15.01 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.56 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 20 05.82 +56 06 38.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.8414,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.79 00:29:31.47 +54:18:13.1
119.70365 -8.43070 galactic Cas Second-epoch detections are separated by 6.3" and 7.2 pix
The object was found in VSX 9" Gaia DR3 419585014537592448
Type: ROT
# Max. Min./Amp. JD0 Period
16.160 G 16.200 G 6.808700000000 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 00:29:31.47 +54:18:13.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:29:31.47 +54:18:13.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.3414* 00 29 31.47 +54 18 13.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 419585014537592448,2461274.8414,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 419585014537592448 20260822.3414 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.3414 2461274.8414 13.72 23:19:03.26 +50:34:01.5
108.29195 -9.66000 galactic And Second-epoch detections are separated by 7.0" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:03.26 +50:34:01.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:03.26 +50:34:01.5: 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:19:03.26 +50:34:01.5: 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.3414* 23 19 03.26 +50 34 01.5 13.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.64 23:58:00.09 +54:14:36.2
115.09928 -7.81370 galactic Cas Second-epoch detections are separated by 0.7" and 7.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:58:00.09 +54:14:36.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:58:00.09 +54:14:36.2: 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:58:00.09 +54:14:36.2: 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.3414* 23 58 00.09 +54 14 36.2 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 13.75 23:50:08.86 +50:52:22.0
113.15687 -10.83203 galactic Cas Second-epoch detections are separated by 7.2" 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 | 23:50:08.86 +50:52:22.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:50:08.86 +50:52:22.0: 15.47 +/- 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:50:08.86 +50:52:22.0: 15.02 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.47 +/- 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.3414* 23 50 08.86 +50 52 22.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.63 00:23:13.73 +56:00:14.0
118.96888 -6.65065 galactic Cas Second-epoch detections are separated by 7.0" and 8.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:23:13.73 +56:00:14.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:23:13.73 +56:00:14.0: 15.00 +/- 0.19 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:23:13.73 +56:00:14.0: 15.09 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.00 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 23 13.73 +56 00 14.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.8414,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.3414 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.3414 2461274.8414 13.71 00:01:04.96 +53:29:22.4
115.39500 -8.64370 galactic Cas Second-epoch detections are separated by 5.9" and 7.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: VOTx1249855 | 00:01:04.96 +53:29:22.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 00:01:04.96 +53:29:22.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:01:04.96 +53:29:22.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.3414* 00 01 04.96 +53 29 22.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: VOTx1249855,2461274.8414,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
DocumentRef: VOTx1249855 20260822.3414 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.3414 2461274.8414 13.66 00:07:46.98 +54:40:43.2
116.59078 -7.65471 galactic Cas Second-epoch detections are separated by 0.8" and 7.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 J001.9389+54.6881 | 00:07:46.98 +54:40:43.2 (user input) | IRR (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:46.98 +54:40:43.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 00:07:46.98 +54:40:43.2: 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.3414* 00 07 46.98 +54 40 43.2 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.9389+54.6881,2461274.8414,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.9389+54.6881 20260822.3414 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.66 23:29:51.74 +53:53:21.4
110.98829 -7.08002 galactic Cas Second-epoch detections are separated by 8.1" and 7.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: VOTx1269680 | 23:29:51.74 +53:53:21.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 23:29:51.74 +53:53:21.4: 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:29:51.74 +53:53:21.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.3414* 23 29 51.74 +53 53 21.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: VOTx1269680,2461274.8414,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1269680 20260822.3414 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.54 23:35:59.28 +53:20:20.0
111.69453 -7.87867 galactic Cas Second-epoch detections are separated by 4.0" 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 | target | 23:35:59.28 +53:20:20.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:35:59.28 +53:20:20.0: 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:35:59.28 +53:20:20.0: 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.3414* 23 35 59.28 +53 20 20.0 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 13.62 00:20:15.23 +53:28:42.0
118.24229 -9.10923 galactic Cas Second-epoch detections are separated by 4.3" and 7.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: VOTx1303150 | 00:20:15.23 +53:28:42.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 00:20:15.23 +53:28:42.0: 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:20:15.23 +53:28:42.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.3414* 00 20 15.23 +53 28 42.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
DocumentRef: VOTx1303150,2461274.8414,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: VOTx1303150 20260822.3414 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.3414 2461274.8414 13.53 23:56:51.73 +51:51:53.0
114.42322 -10.10312 galactic Cas Second-epoch detections are separated by 5.3" and 7.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:56:51.73 +51:51:53.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:56:51.73 +51:51:53.0: 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:56:51.73 +51:51:53.0: 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.3414* 23 56 51.73 +51 51 53.0 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.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.3414 13.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.3414 2461274.8414 13.69 23:41:28.09 +55:38:06.9
113.11109 -5.89665 galactic Cas Second-epoch detections are separated by 5.6" and 7.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: VOTx1372219 | 23:41:28.09 +55:38:06.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:41:28.09 +55:38:06.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 23:41:28.09 +55:38:06.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.3414* 23 41 28.09 +55 38 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
DocumentRef: VOTx1372219,2461274.8414,13.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1372219 20260822.3414 13.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.56 00:19:42.47 +50:07:36.4
117.73399 -12.42446 galactic Cas Second-epoch detections are separated by 8.9" and 7.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:19:42.47 +50:07:36.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:19:42.47 +50:07:36.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:19:42.47 +50:07:36.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.3414* 00 19 42.47 +50 07 36.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.8414,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.3414 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.3414 2461274.8414 13.45 23:25:30.43 +56:41:11.0
111.29637 -4.23156 galactic Cas Second-epoch detections are separated by 3.4" and 7.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:25:30.43 +56:41:11.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:25:30.43 +56:41: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 23:25:30.43 +56:41:11.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.3414* 23 25 30.43 +56 41 11.0 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.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.3414 13.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.3414 2461274.8414 13.40 23:20:39.52 +54:42:07.1
109.98106 -5.87100 galactic Cas Second-epoch detections are separated by 7.1" 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 | 23:20:39.52 +54:42: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:20:39.52 +54:42:07.1: 15.27 +/- 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:20:39.52 +54:42:07.1: 14.86 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.27 +/- 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.3414* 23 20 39.52 +54 42 07.1 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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
target 20260822.3414 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.3414 2461274.8414 13.15 00:25:38.27 +51:57:37.6
118.89212 -10.70882 galactic Cas Second-epoch detections are separated by 4.8" and 7.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J006.4274+51.9581 | 00:25:38.27 +51:57:37.6 (user input) | CBF (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:25:38.27 +51:57:37.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:25:38.27 +51:57:37.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.3414* 00 25 38.27 +51 57 37.6 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J006.4274+51.9581,2461274.8414,13.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J006.4274+51.9581 20260822.3414 13.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.08 00:26:14.34 +55:46:35.7
119.36770 -6.92068 galactic Cas Second-epoch detections are separated by 3.0" and 7.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:26:14.34 +55:46:35.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 00:26:14.34 +55:46:35.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 00:26:14.34 +55:46:35.7: 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.3414* 00 26 14.34 +55 46 35.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
target,2461274.8414,13.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.07 23:12:57.41 +55:27:59.3
109.22325 -4.76218 galactic Cas Second-epoch detections are separated by 7.2" and 6.3 pix
The object was found in VSX14" ZTF J231256.89+552746.2
Type: BY
# Max. Min./Amp. JD0 Period
17.664 r Y 0.059 r 2458312.92640 0.895689800000
ATTENTION: measured mag 13.07 is 4.5 mag brighter than the VSX record maximum brightness 17.61 - 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:12:57.41 +55:27:59.3: 14.25 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:12:57.41 +55:27:59.3: 14.84 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 14.25 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 12 57.41 +55 27 59.3 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J231256.89+552746.2,2461274.8414,13.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
ZTF J231256.89+552746.2 20260822.3414 13.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.3414 2461274.8414 13.06 23:39:45.44 +51:01:24.4
111.58873 -10.26278 galactic Cas Second-epoch detections are separated by 2.3" and 7.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:39:45.44 +51:01:24.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:39:45.44 +51:01:24.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 23:39:45.44 +51:01:24.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.3414* 23 39 45.44 +51 01 24.4 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.97 23:17:59.42 +54:10:03.1
109.42743 -6.23578 galactic Cas Second-epoch detections are separated by 3.8" 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 | 23:17:59.42 +54:10: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 23:17:59.42 +54:10:03.1: 15.07 +/- 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:17:59.42 +54:10:03.1: 14.91 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.07 +/- 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.3414* 23 17 59.42 +54 10 03.1 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.8414,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.91 23:15:57.75 +54:49:29.8
109.38799 -5.51652 galactic Cas Second-epoch detections are separated by 4.3" and 7.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:57.75 +54:49:29.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:15:57.75 +54:49:29.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:15:57.75 +54:49:29.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.3414* 23 15 57.75 +54 49 29.8 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.86 23:45:29.79 +53:49:35.1
113.19917 -7.79459 galactic Cas Second-epoch detections are separated by 6.7" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:45:29.79 +53:49:35.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:45:29.79 +53:49:35.1: 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:45:29.79 +53:49:35.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.3414* 23 45 29.79 +53 49 35.1 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.82 23:12:00.82 +56:27:27.7
109.47171 -3.79339 galactic Cas Second-epoch detections are separated by 4.4" and 7.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: VOTx2134522 | 23:12:00.82 +56:27: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 23:12:00.82 +56:27:27.7: 15.22 +/- 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.82 +56:27:27.7: 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.3414* 23 12 00.82 +56 27 27.7 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2134522,2461274.8414,12.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2134522 20260822.3414 12.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.78 23:27:45.51 +55:44:30.1
111.28745 -5.22670 galactic Cas Second-epoch detections are separated by 5.6" 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 | DocumentRef: VOTx2184454 | 23:27:45.51 +55:44:30.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:27:45.51 +55:44:30.1: 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:27:45.51 +55:44:30.1: 14.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 27 45.51 +55 44 30.1 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2184454,2461274.8414,12.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2184454 20260822.3414 12.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.89 23:29:19.38 +54:25:59.6
111.08443 -6.53873 galactic Cas Second-epoch detections are separated by 7.1" 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 | 23:29:19.38 +54:25:59.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:29:19.38 +54:25:59.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:29:19.38 +54:25:59.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.3414* 23 29 19.38 +54 25 59.6 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.94 23:53:43.24 +50:58:21.1
113.73808 -10.86601 galactic Cas Second-epoch detections are separated by 7.5" and 7.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: VOTx2188669 | 23:53:43.24 +50:58:21.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:53:43.24 +50:58:21.1: 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:43.24 +50:58:21.1: 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.3414* 23 53 43.24 +50 58 21.1 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2188669,2461274.8414,12.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: VOTx2188669 20260822.3414 12.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.3414 2461274.8414 12.75 00:07:16.78 +51:00:16.6
115.87473 -11.26106 galactic Cas Second-epoch detections are separated by 1.8" and 7.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:07:16.78 +51:00:16.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:07:16.78 +51:00:16.6: 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:07:16.78 +51:00:16.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.3414* 00 07 16.78 +51 00 16.6 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.66 00:23:20.28 +54:55:57.7
118.86569 -7.71705 galactic Cas Second-epoch detections are separated by 3.6" and 7.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:23:20.28 +54:55:57.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 00:23:20.28 +54:55:57.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 00:23:20.28 +54:55:57.7: 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.3414* 00 23 20.28 +54 55 57.7 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.57 23:40:07.91 +51:56:11.6
111.90250 -9.40162 galactic Cas Second-epoch detections are separated by 8.6" and 7.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:40:07.91 +51:56:11.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:40:07.91 +51:56:11.6: 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:40:07.91 +51:56:11.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.3414* 23 40 07.91 +51 56 11.6 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 12.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 11.74 23:23:22.94 +56:38:57.9
111.00789 -4.16993 galactic Cas Second-epoch detections are separated by 5.1" and 6.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:23:22.94 +56:38:57.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:22.94 +56:38:57.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:23:22.94 +56:38:57.9: 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.3414* 23 23 22.94 +56 38 57.9 11.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,11.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 11.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 12.55 23:12:59.40 +56:18:49.8
109.54354 -3.97729 galactic Cas Second-epoch detections are separated by 8.7" and 7.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 J348.2419+56.3061 | 23:12:59.40 +56:18:49.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:12:59.40 +56:18:49.8: 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.40 +56:18:49.8: 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.3414* 23 12 59.40 +56 18 49.8 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J348.2419+56.3061,2461274.8414,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.3414 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.3414 2461274.8414 12.73 23:20:01.55 +49:31:29.5
108.06650 -10.69019 galactic And Second-epoch detections are separated by 7.7" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:20:01.55 +49:31:29.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:01.55 +49:31:29.5: 15.09 +/- 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:20:01.55 +49:31:29.5: 14.80 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.09 +/- 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.3414* 23 20 01.55 +49 31 29.5 12.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,12.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 13.01 23:32:51.48 +54:47:21.1
111.68470 -6.35746 galactic Cas Second-epoch detections are separated by 4.6" and 7.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: VOTx2691574 | 23:32:51.48 +54:47:21.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:32:51.48 +54:47:21.1: 15.10 +/- 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:32:51.48 +54:47:21.1: 14.96 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.10 +/- 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.3414* 23 32 51.48 +54 47 21.1 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
DocumentRef: VOTx2691574,2461274.8414,13.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: VOTx2691574 20260822.3414 13.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.3414 2461274.8414 13.18 23:25:40.67 +53:22:58.3
110.23252 -7.36109 galactic Cas Second-epoch detections are separated by 6.2" 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 | DocumentRef: VOTx2953672 | 23:25:40.67 +53:22:58.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:25:40.67 +53:22:58.3: 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:25:40.67 +53:22:58.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.3414* 23 25 40.67 +53 22 58.3 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2953672,2461274.8414,13.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
DocumentRef: VOTx2953672 20260822.3414 13.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.3414 2461274.8414 13.37 23:56:49.38 +50:03:02.2
114.02170 -11.87390 galactic Cas Second-epoch detections are separated by 5.0" and 7.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: VOTx2999739 | 23:56:49.38 +50:03:02.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:56:49.38 +50:03:02.2: 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.38 +50:03:02.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.3414* 23 56 49.38 +50 03 02.2 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: VOTx2999739,2461274.8414,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
DocumentRef: VOTx2999739 20260822.3414 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.3414 2461274.8414 13.57 00:12:47.58 +49:45:34.5
116.55306 -12.63293 galactic Cas Second-epoch detections are separated by 2.1" and 7.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:12:47.58 +49:45:34.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:12:47.58 +49:45:34.5: 15.63 +/- 0.34 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.58 +49:45:34.5: 14.99 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.63 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 12 47.58 +49 45 34.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.8414,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.3414 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.3414 2461274.8414 13.61 23:48:47.93 +49:47:28.5
112.67646 -11.82910 galactic Cas Second-epoch detections are separated by 4.4" and 7.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: VOTx3003679 | 23:48:47.93 +49:47:28.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:47.93 +49:47:28.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:47.93 +49:47:28.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.3414* 23 48 47.93 +49 47 28.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
DocumentRef: VOTx3003679,2461274.8414,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
DocumentRef: VOTx3003679 20260822.3414 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.3414 2461274.8414 13.60 23:17:14.26 +56:09:07.2
110.03563 -4.34291 galactic Cas Second-epoch detections are separated by 2.9" 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 | DocumentRef: VOTx3189678 | 23:17:14.26 +56:09:07.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:17:14.26 +56:09:07.2: 15.35 +/- 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:14.26 +56:09:07.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.3414* 23 17 14.26 +56 09 07.2 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3189678,2461274.8414,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: VOTx3189678 20260822.3414 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.3414 2461274.8414 13.64 23:21:44.64 +54:27:13.8
110.04392 -6.15805 galactic Cas Second-epoch detections are separated by 5.8" and 7.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 J350.4284+54.4611 | 23:21:44.64 +54:27:13.8 (user input) | NSINE (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:44.64 +54:27:13.8: 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:21:44.64 +54:27:13.8: 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.3414* 23 21 44.64 +54 27 13.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
ATO J350.4284+54.4611,2461274.8414,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
ATO J350.4284+54.4611 20260822.3414 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.3414 2461274.8414 13.62 23:43:57.31 +50:48:34.4
112.17759 -10.64770 galactic Cas Second-epoch detections are separated by 7.4" and 7.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:43:57.31 +50:48:34.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:57.31 +50:48:34.4: 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.31 +50:48:34.4: 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.3414* 23 43 57.31 +50 48 34.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.8414,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.3414 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.3414 2461274.8414 13.70 00:19:37.41 +50:48:31.5
117.80809 -11.74622 galactic Cas Second-epoch detections are separated by 8.1" and 8.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:19:37.41 +50:48:31.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:19:37.41 +50:48:31.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:19:37.41 +50:48:31.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.3414* 00 19 37.41 +50 48 31.5 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.72 23:27:29.73 +54:49:53.3
110.95927 -6.07715 galactic Cas Second-epoch detections are separated by 2.1" and 7.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:29.73 +54:49: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:27:29.73 +54:49:53.3: 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:27:29.73 +54:49:53.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.3414* 23 27 29.73 +54 49 53.3 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.79 00:14:58.08 +54:13:21.4
117.56035 -8.26833 galactic Cas Second-epoch detections are separated by 3.5" and 7.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:14:58.08 +54:13:21.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:14:58.08 +54:13:21.4: 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 00:14:58.08 +54:13:21.4: 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.3414* 00 14 58.08 +54 13 21.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.8414,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.3414 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.3414 2461274.8414 13.70 23:13:13.59 +55:44:21.5
109.36042 -4.52302 galactic Cas Second-epoch detections are separated by 3.2" 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 | ATO J348.3153+55.7412 | 23:13:13.59 +55:44:21.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 23:13:13.59 +55:44:21.5: 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:13.59 +55:44:21.5: 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.3414* 23 13 13.59 +55 44 21.5 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J348.3153+55.7412,2461274.8414,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J348.3153+55.7412 20260822.3414 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.75 23:10:20.72 +57:28:17.8
109.64437 -2.76870 galactic Cas Second-epoch detections are separated by 3.3" and 7.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:10:20.72 +57:28:17.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:10:20.72 +57:28:17.8: 15.22 +/- 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:10:20.72 +57:28:17.8: 14.61 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 10 20.72 +57 28 17.8 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 13.89 00:06:00.89 +51:25:00.3
115.75000 -10.82048 galactic Cas Second-epoch detections are separated by 6.5" and 7.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:06:00.89 +51:25:00.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:06:00.89 +51:25:00.3: 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:06:00.89 +51:25:00.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.3414* 00 06 00.89 +51 25 00.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.8414,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.3414 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.3414 2461274.8414 13.77 23:19:26.91 +55:24:29.3
110.06408 -5.14860 galactic Cas Second-epoch detections are separated by 7.9" and 6.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: VOTx3542298 | 23:19:26.91 +55:24:29.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:19:26.91 +55:24:29.3: 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.91 +55:24:29.3: 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.3414* 23 19 26.91 +55 24 29.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
DocumentRef: VOTx3542298,2461274.8414,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
DocumentRef: VOTx3542298 20260822.3414 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.3414 2461274.8414 13.77 00:22:28.01 +50:43:42.9
118.25421 -11.87985 galactic Cas Second-epoch detections are separated by 5.2" and 7.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: VOTx3572221 | 00:22:28.01 +50:43:42.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 00:22:28.01 +50:43:42.9: 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:22:28.01 +50:43:42.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.3414* 00 22 28.01 +50 43 42.9 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx3572221,2461274.8414,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
DocumentRef: VOTx3572221 20260822.3414 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.3414 2461274.8414 13.85 23:57:03.71 +52:12:03.8
114.52633 -9.78102 galactic Cas Second-epoch detections are separated by 2.4" and 7.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: VOTx3608676 | 23:57:03.71 +52:12:03.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:57:03.71 +52:12:03.8: 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:03.71 +52:12:03.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.3414* 23 57 03.71 +52 12 03.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
DocumentRef: VOTx3608676,2461274.8414,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
DocumentRef: VOTx3608676 20260822.3414 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.3414 2461274.8414 13.88 23:53:56.97 +50:54:38.3
113.75964 -10.93443 galactic Cas Second-epoch detections are separated by 2.5" and 7.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: VOTx3634190 | 23:53:56.97 +50:54:38.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:53:56.97 +50:54:38.3: 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:53:56.97 +50:54:38.3: 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.3414* 23 53 56.97 +50 54 38.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
DocumentRef: VOTx3634190,2461274.8414,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: VOTx3634190 20260822.3414 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.3414 2461274.8414 13.94 23:17:56.52 +56:24:55.7
110.22112 -4.13136 galactic Cas Second-epoch detections are separated by 4.0" 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 | DocumentRef: VOTx3626800 | 23:17:56.52 +56:24:55.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:17:56.52 +56:24:55.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:17:56.52 +56:24:55.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.3414* 23 17 56.52 +56 24 55.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: VOTx3626800,2461274.8414,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: VOTx3626800 20260822.3414 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.3414 2461274.8414 13.89 23:27:37.67 +55:29:26.3
111.18935 -5.45872 galactic Cas Second-epoch detections are separated by 5.3" and 7.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:27:37.67 +55:29:26.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:37.67 +55:29:26.3: 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:27:37.67 +55:29:26.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.3414* 23 27 37.67 +55 29 26.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.8414,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.3414 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.3414 2461274.8414 13.95 00:05:13.90 +51:50:43.2
115.70677 -10.37703 galactic Cas Second-epoch detections are separated by 8.8" and 7.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: VOTx3658006 | 00:05:13.90 +51:50:43.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:05:13.90 +51:50:43.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 00:05:13.90 +51:50:43.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.3414* 00 05 13.90 +51 50 43.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: VOTx3658006,2461274.8414,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: VOTx3658006 20260822.3414 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.3414 2461274.8414 13.96 23:26:59.99 +54:16:27.2
110.71050 -6.58168 galactic Cas Second-epoch detections are separated by 7.4" and 7.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: VOTx3663492 | 23:26:59.99 +54:16:27.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:26:59.99 +54:16:27.2: 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:26:59.99 +54:16:27.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.3414* 23 26 59.99 +54 16 27.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: VOTx3663492,2461274.8414,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: VOTx3663492 20260822.3414 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.3414 2461274.8414 14.00 23:51:39.63 +50:16:05.2
113.24878 -11.47638 galactic Cas Second-epoch detections are separated by 3.3" and 7.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:51:39.63 +50:16:05.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:51:39.63 +50:16:05.2: 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:51:39.63 +50:16:05.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.3414* 23 51 39.63 +50 16 05.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.8414,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.3414 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.3414 2461274.8414 13.84 23:48:52.01 +52:53:34.7
113.45658 -8.82379 galactic Cas Second-epoch detections are separated by 5.3" and 7.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 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:52.01 +52:53:34.7: 15.41 +/- 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:48:52.01 +52:53:34.7: 15.13 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.41 +/- 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.3414* 23 48 52.01 +52 53 34.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.8414,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
ATO J357.2195+52.8965 20260822.3414 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.3414 2461274.8414 13.94 23:46:20.17 +51:20:04.0
112.68279 -10.23715 galactic Cas Second-epoch detections are separated by 5.0" and 7.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: VOTx3676358 | 23:46:20.17 +51:20:04.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:46:20.17 +51:20:04.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:46:20.17 +51:20:04.0: 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.3414* 23 46 20.17 +51 20 04.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: VOTx3676358,2461274.8414,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: VOTx3676358 20260822.3414 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.3414 2461274.8414 13.88 23:18:16.06 +54:05:41.0
109.43967 -6.31826 galactic Cas Second-epoch detections are separated by 3.7" and 7.0 pix
The object was found in VSX 6" 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:16.06 +54:05:41.0: 15.20 +/- 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:18:16.06 +54:05:41.0: 14.76 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.20 +/- 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.3414* 23 18 16.06 +54 05 41.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
Gaia DR3 1995967754538602368,2461274.8414,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
Gaia DR3 1995967754538602368 20260822.3414 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.3414 2461274.8414 14.02 23:55:29.98 +51:30:59.5
114.13729 -10.39749 galactic Cas Second-epoch detections are separated by 1.4" and 7.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 1944109937147790592 | 23:55:31.61 +51:30:30.6 (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:55:29.98 +51:30:59.5: 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:55:29.98 +51:30:59.5: 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.3414* 23 55 29.98 +51 30 59.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 1944109937147790592,2461274.8414,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 1944109937147790592 20260822.3414 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.3414 2461274.8414 13.96 23:19:19.85 +51:15:48.2
108.58259 -9.02400 galactic And Second-epoch detections are separated by 4.4" and 7.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 1991528609478611200 | 23:19:17.87 +51:16:31.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE J-Ks=0.398+/-0.138 (G)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:19:19.85 +51:15:48.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:19:19.85 +51:15:48.2: 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.3414* 23 19 19.85 +51 15 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
Gaia DR3 1991528609478611200,2461274.8414,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
Gaia DR3 1991528609478611200 20260822.3414 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.3414 2461274.8414 14.11 23:19:14.01 +52:17:58.3
108.93737 -8.04895 galactic And Second-epoch detections are separated by 4.5" and 7.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:14.01 +52:17:58.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:14.01 +52:17:58.3: 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:19:14.01 +52:17:58.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.3414* 23 19 14.01 +52 17 58.3 14.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.8414,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.3414 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.3414 2461274.8414 14.00 23:23:12.95 +54:50:22.9
110.37677 -5.86711 galactic Cas Second-epoch detections are separated by 3.4" and 7.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:12.95 +54:50:22.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:12.95 +54:50:22.9: 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:12.95 +54:50:22.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.3414* 23 23 12.95 +54 50 22.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.8414,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.3414 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.3414 2461274.8414 13.95 00:16:44.21 +54:00:39.1
117.79002 -8.51408 galactic Cas Second-epoch detections are separated by 6.2" and 7.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: VOTx3728620 | 00:16:44.21 +54:00: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:16:44.21 +54:00:39.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:16:44.21 +54:00:39.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.3414* 00 16 44.21 +54 00 39.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: VOTx3728620,2461274.8414,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: VOTx3728620 20260822.3414 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.3414 2461274.8414 14.06 23:19:22.81 +54:27:13.9
109.71972 -6.03926 galactic Cas Second-epoch detections are separated by 7.0" and 7.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:22.81 +54:27:13.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:19:22.81 +54:27:13.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:19:22.81 +54:27:13.9: 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.3414* 23 19 22.81 +54 27 13.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 14.01 23:39:08.18 +51:12:37.7
111.54675 -10.05597 galactic Cas Second-epoch detections are separated by 5.3" and 7.1 pix
The object was found in VSX 5" Gaia DR3 1944569571669567616
Type: RS
# Max. Min./Amp. JD0 Period
16.570 G 16.750 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:39:08.18 +51:12:37.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:39:08.18 +51:12:37.7: 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.3414* 23 39 08.18 +51 12 37.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
Gaia DR3 1944569571669567616,2461274.8414,14.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1944569571669567616 20260822.3414 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.3414 2461274.8414 13.99 00:18:16.38 +50:20:06.6
117.52849 -12.18831 galactic Cas Second-epoch detections are separated by 6.1" and 7.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: VOTx3798581 | 00:18:16.38 +50:20:06.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 00:18:16.38 +50:20:06.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:18:16.38 +50:20:06.6: 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.3414* 00 18 16.38 +50 20 06.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: VOTx3798581,2461274.8414,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: VOTx3798581 20260822.3414 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.3414 2461274.8414 14.08 23:15:40.09 +52:17:13.7
108.41898 -7.86519 galactic And Second-epoch detections are separated by 5.7" and 7.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: VOTx3853392 | 23:15:40.09 +52:17:13.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:15:40.09 +52:17:13.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:15:40.09 +52:17:13.7: 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.3414* 23 15 40.09 +52 17 13.7 14.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
DocumentRef: VOTx3853392,2461274.8414,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
DocumentRef: VOTx3853392 20260822.3414 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.3414 2461274.8414 13.99 23:55:59.04 +52:04:39.6
114.33555 -9.86609 galactic Cas Second-epoch detections are separated by 5.9" and 7.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: VOTx3887293 | 23:55:59.04 +52:04:39.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:55:59.04 +52:04:39.6: 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.04 +52:04:39.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.3414* 23 55 59.04 +52 04 39.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: VOTx3887293,2461274.8414,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: VOTx3887293 20260822.3414 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.3414 2461274.8414 14.24 23:30:31.11 +54:53:22.7
111.39290 -6.15898 galactic Cas Second-epoch detections are separated by 7.0" 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 | 23:30:31.11 +54:53:22.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:30:31.11 +54:53:22.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:30:31.11 +54:53:22.7: 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.3414* 23 30 31.11 +54 53 22.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.8414,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.3414 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.3414 2461274.8414 14.04 23:42:14.12 +53:08:22.6
112.54501 -8.33082 galactic Cas Second-epoch detections are separated by 2.6" and 8.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:14.12 +53:08: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:42:14.12 +53:08:22.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 23:42:14.12 +53:08:22.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.3414* 23 42 14.12 +53 08 22.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.8414,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.3414 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.3414 2461274.8414 14.23 23:26:52.38 +52:05:31.3
109.97982 -8.64029 galactic Cas Second-epoch detections are separated by 5.4" and 7.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 J351.7136+52.0917 | 23:26:52.38 +52:05:31.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:26:52.38 +52:05:31.3: 15.54 +/- 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:26:52.38 +52:05:31.3: 14.77 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.12 +/- 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.3414* 23 26 52.38 +52 05 31.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
ATO J351.7136+52.0917,2461274.8414,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
ATO J351.7136+52.0917 20260822.3414 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.3414 2461274.8414 14.06 23:33:46.45 +54:02:56.0
111.58940 -7.10368 galactic Cas Second-epoch detections are separated by 3.5" and 6.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:46.45 +54:02:56.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:46.45 +54:02:56.0: 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:33:46.45 +54:02:56.0: 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.3414* 23 33 46.45 +54 02 56.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.8414,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.3414 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.3414 2461274.8414 14.22 23:28:40.35 +52:21:28.3
110.33010 -8.47710 galactic Cas Second-epoch detections are separated by 3.6" and 7.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:28:40.35 +52:21:28.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:28:40.35 +52:21:28.3: 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:28:40.35 +52:21:28.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.3414* 23 28 40.35 +52 21 28.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.8414,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.3414 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.3414 2461274.8414 14.29 23:40:25.77 +51:36:38.1
111.85624 -9.72765 galactic Cas Second-epoch detections are separated by 3.8" 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 | DocumentRef: VOTx3988960 | 23:40:25.77 +51:36:38.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:40:25.77 +51:36:38.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:40:25.77 +51:36:38.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.3414* 23 40 25.77 +51 36 38.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: VOTx3988960,2461274.8414,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: VOTx3988960 20260822.3414 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.3414 2461274.8414 14.11 23:31:43.53 +51:03:14.4
110.37187 -9.86346 galactic Cas Second-epoch detections are separated by 6.4" and 7.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:43.53 +51:03:14.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:31:43.53 +51:03:14.4: 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.53 +51:03:14.4: 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.3414* 23 31 43.53 +51 03 14.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.8414,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.3414 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.3414 2461274.8414 14.13 23:45:24.33 +54:30:54.7
113.36324 -7.12516 galactic Cas Second-epoch detections are separated by 8.8" 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 | 23:45:24.33 +54:30:54.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:45:24.33 +54:30:54.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:45:24.33 +54:30:54.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.3414* 23 45 24.33 +54 30 54.7 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 13.99 23:29:10.55 +56:37:30.6
111.75567 -4.45098 galactic Cas Second-epoch detections are separated by 5.4" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:10.55 +56:37: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:29:10.55 +56:37:30.6: 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:29:10.55 +56:37:30.6: 14.67 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 23 29 10.55 +56 37 30.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.8414,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.3414 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.3414 2461274.8414 14.17 23:56:57.38 +51:38:21.3
114.38886 -10.32651 galactic Cas Second-epoch detections are separated by 5.9" 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 | DocumentRef: VOTx4009606 | 23:56:57.38 +51:38:21.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:56:57.38 +51:38:21.3: 15.48 +/- 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:56:57.38 +51:38:21.3: 15.12 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.48 +/- 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.3414* 23 56 57.38 +51 38 21.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
DocumentRef: VOTx4009606,2461274.8414,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
DocumentRef: VOTx4009606 20260822.3414 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.3414 2461274.8414 14.07 23:32:40.34 +56:50:03.2
112.27779 -4.39935 galactic Cas Second-epoch detections are separated by 5.6" 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 | 23:32:40.34 +56:50:03.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:40.34 +56:50:03.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:32:40.34 +56:50:03.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.3414* 23 32 40.34 +56 50 03.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.8414,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.3414 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.3414 2461274.8414 14.21 23:54:22.33 +50:47:56.9
113.80040 -11.05805 galactic Cas Second-epoch detections are separated by 7.0" and 7.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: VOTx4018929 | 23:54:22.33 +50:47:56.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:54:22.33 +50:47:56.9: 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:22.33 +50:47:56.9: 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.3414* 23 54 22.33 +50 47 56.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: VOTx4018929,2461274.8414,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: VOTx4018929 20260822.3414 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.3414 2461274.8414 14.07 23:14:04.18 +56:21:23.9
109.69877 -3.99282 galactic Cas Second-epoch detections are separated by 3.5" and 7.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: VOTx4024094 | 23:14:04.18 +56:21:23.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:14:04.18 +56:21:23.9: 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:04.18 +56:21:23.9: 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.3414* 23 14 04.18 +56 21 23.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx4024094,2461274.8414,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
DocumentRef: VOTx4024094 20260822.3414 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.3414 2461274.8414 14.23 23:34:13.82 +56:18:02.1
112.32375 -4.97269 galactic Cas Second-epoch detections are separated by 3.7" and 7.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: VOTx4049974 | 23:34:13.82 +56:18:02.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:34:13.82 +56:18:02.1: 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.82 +56:18:02.1: 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.3414* 23 34 13.82 +56 18 02.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
DocumentRef: VOTx4049974,2461274.8414,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: VOTx4049974 20260822.3414 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.3414 2461274.8414 14.32 23:19:09.50 +56:44:16.5
110.49200 -3.88845 galactic Cas Second-epoch detections are separated by 6.1" and 7.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: VOTx4046441 | 23:19:09.50 +56:44:16.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:19:09.50 +56:44:16.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:19:09.50 +56:44:16.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.3414* 23 19 09.50 +56 44 16.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
DocumentRef: VOTx4046441,2461274.8414,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: VOTx4046441 20260822.3414 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.3414 2461274.8414 14.17 00:14:12.21 +51:14:39.4
117.00716 -11.19863 galactic Cas Second-epoch detections are separated by 4.4" and 7.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:14:12.21 +51:14:39.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:14:12.21 +51:14:39.4: 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:12.21 +51:14:39.4: 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.3414* 00 14 12.21 +51 14 39.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.8414,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.3414 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.3414 2461274.8414 14.07 23:28:19.61 +53:31:54.8
110.65734 -7.34750 galactic Cas Second-epoch detections are separated by 5.6" and 8.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:19.61 +53:31:54.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:19.61 +53:31:54.8: 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:19.61 +53:31:54.8: 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.3414* 23 28 19.61 +53 31 54.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.8414,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.3414 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.3414 2461274.8414 14.31 23:20:08.25 +49:57:27.5
108.23830 -10.29134 galactic And Second-epoch detections are separated by 7.2" and 7.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:20:08.25 +49:57: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:20:08.25 +49:57:27.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:20:08.25 +49:57:27.5: 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.3414* 23 20 08.25 +49 57 27.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.8414,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.3414 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.3414 2461274.8414 14.22 00:15:46.91 +51:08:54.9
117.24264 -11.32886 galactic Cas Second-epoch detections are separated by 2.3" and 7.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: VOTx4089550 | 00:15:46.91 +51:08:54.9 (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:15:46.91 +51:08:54.9: 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:15:46.91 +51:08:54.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.3414* 00 15 46.91 +51 08 54.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: VOTx4089550,2461274.8414,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
DocumentRef: VOTx4089550 20260822.3414 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.3414 2461274.8414 14.20 23:37:55.93 +56:26:09.0
112.85555 -4.99105 galactic Cas Second-epoch detections are separated by 2.5" and 7.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: VOTx4085315 | 23:37:55.93 +56:26:09.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:37:55.93 +56:26:09.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:37:55.93 +56:26:09.0: 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.3414* 23 37 55.93 +56 26 09.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
DocumentRef: VOTx4085315,2461274.8414,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: VOTx4085315 20260822.3414 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.3414 2461274.8414 14.28 23:44:34.09 +55:20:20.6
113.45870 -6.29798 galactic Cas Second-epoch detections are separated by 3.8" and 6.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:34.09 +55:20:20.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:44:34.09 +55:20:20.6: 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:44:34.09 +55:20:20.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.3414* 23 44 34.09 +55 20 20.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.8414,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.3414 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.3414 2461274.8414 14.12 23:15:00.47 +55:26:12.5
109.48356 -4.89690 galactic Cas Second-epoch detections are separated by 7.1" 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 | DocumentRef: VOTx4117283 | 23:15:00.47 +55:26:12.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:15:00.47 +55:26:12.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:15:00.47 +55:26:12.5: 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.3414* 23 15 00.47 +55 26 12.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
DocumentRef: VOTx4117283,2461274.8414,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
DocumentRef: VOTx4117283 20260822.3414 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.3414 2461274.8414 14.23 23:13:59.72 +56:34:34.3
109.77014 -3.78488 galactic Cas Second-epoch detections are separated by 4.2" and 7.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: VOTx4147836 | 23:13:59.72 +56:34:34.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:13:59.72 +56:34:34.3: 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:59.72 +56:34:34.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.3414* 23 13 59.72 +56 34 34.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
DocumentRef: VOTx4147836,2461274.8414,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: VOTx4147836 20260822.3414 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.3414 2461274.8414 14.28 23:23:20.81 +49:55:24.7
108.71905 -10.50158 galactic And Second-epoch detections are separated by 2.7" and 7.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: VOTx336081 | 23:23:20.81 +49:55:24.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:23:20.81 +49:55:24.7: 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.81 +49:55:24.7: 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.3414* 23 23 20.81 +49 55 24.7 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
DocumentRef: VOTx336081,2461274.8414,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
DocumentRef: VOTx336081 20260822.3414 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.3414 2461274.8414 14.12 00:07:46.54 +53:00:37.9
116.30233 -9.29827 galactic Cas Second-epoch detections are separated by 2.6" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:46.54 +53:00: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:07:46.54 +53:00:37.9: 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 00:07:46.54 +53:00:37.9: 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.3414* 00 07 46.54 +53 00 37.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461274.8414,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.3414 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.3414 2461274.8414 14.21 00:16:43.41 +52:48:43.9
117.62294 -9.70134 galactic Cas Second-epoch detections are separated by 8.4" and 7.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 419200700864991232 | 00:16:43.84 +52:47:57.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:16:43.41 +52:48:43.9: 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:16:43.41 +52:48:43.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.3414* 00 16 43.41 +52 48 43.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 419200700864991232,2461274.8414,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
Gaia DR3 419200700864991232 20260822.3414 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.3414 2461274.8414 14.33 23:39:55.79 +51:47:05.1
111.82955 -9.53888 galactic Cas Second-epoch detections are separated by 7.4" and 7.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:55.79 +51:47:05.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:55.79 +51:47:05.1: 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:39:55.79 +51:47:05.1: 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.3414* 23 39 55.79 +51 47 05.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.30 23:16:14.45 +55:12:26.1
109.56404 -5.17443 galactic Cas Second-epoch detections are separated by 6.7" 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 | 23:16:14.45 +55:12:26.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:16:14.45 +55:12:26.1: 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:14.45 +55:12:26.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.3414* 23 16 14.45 +55 12 26.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.8414,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.3414 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.3414 2461274.8414 14.39 23:39:09.88 +50:57:48.1
111.48066 -10.29441 galactic Cas Second-epoch detections are separated by 2.8" and 7.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:39:09.88 +50:57:48.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:09.88 +50:57:48.1: 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 23:39:09.88 +50:57:48.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.3414* 23 39 09.88 +50 57 48.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.8414,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.3414 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.3414 2461274.8414 14.28 23:44:02.40 +50:40:34.5
112.15513 -10.77985 galactic Cas Second-epoch detections are separated by 7.8" and 7.2 pix
The object was found in VSX24" Gaia DR3 1943834513786847744
Type: ROT
# Max. Min./Amp. JD0 Period
14.210 G 14.230 G 1.585600000000 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:44:02.40 +50:40:34.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 23:44:02.40 +50:40:34.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.3414* 23 44 02.40 +50 40 34.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 1943834513786847744,2461274.8414,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 1943834513786847744 20260822.3414 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.3414 2461274.8414 14.35 23:32:27.80 +55:10:17.5
111.74642 -5.97585 galactic Cas Second-epoch detections are separated by 2.3" and 7.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:27.80 +55:10: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:32:27.80 +55:10: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:32:27.80 +55:10:17.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.3414* 23 32 27.80 +55 10 17.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.8414,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.3414 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.3414 2461274.8414 14.36 23:25:22.78 +54:25:09.9
110.53341 -6.36754 galactic Cas Second-epoch detections are separated by 3.4" and 7.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 J351.3584+54.4267 | 23:25:22.78 +54:25:09.9 (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:22.78 +54:25:09.9: 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:22.78 +54:25:09.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.3414* 23 25 22.78 +54 25 09.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
ATO J351.3584+54.4267,2461274.8414,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
ATO J351.3584+54.4267 20260822.3414 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.3414 2461274.8414 14.26 23:22:05.49 +50:07:46.9
108.59800 -10.23895 galactic And Second-epoch detections are separated by 8.9" 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 | 23:22:05.49 +50:07:46.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:22:05.49 +50:07:46.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:22:05.49 +50:07:46.9: 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.3414* 23 22 05.49 +50 07 46.9 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.8414,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.3414 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.3414 2461274.8414 14.11 23:32:02.31 +51:29:10.2
110.55378 -9.46722 galactic Cas Second-epoch detections are separated by 3.4" and 7.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 J353.0142+51.4941 | 23:32:02.31 +51:29:10.2 (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:32:02.31 +51:29:10.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:32:02.31 +51:29:10.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.3414* 23 32 02.31 +51 29 10.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
ATO J353.0142+51.4941,2461274.8414,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
ATO J353.0142+51.4941 20260822.3414 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.3414 2461274.8414 14.38 23:51:24.01 +53:36:25.8
114.00053 -8.22024 galactic Cas Second-epoch detections are separated by 6.9" and 7.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 J357.8327+53.6141 | 23:51:24.01 +53:36:25.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) J-Ks=0.799+/- (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:51:24.01 +53:36:25.8: 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 23:51:24.01 +53:36:25.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.3414* 23 51 24.01 +53 36 25.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
ATO J357.8327+53.6141,2461274.8414,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
ATO J357.8327+53.6141 20260822.3414 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.3414 2461274.8414 14.22 00:14:15.94 +51:38:24.2
117.07600 -10.80854 galactic Cas Second-epoch detections are separated by 4.6" and 7.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: VOTx246789 | 00:14:15.94 +51:38:24.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:14:15.94 +51:38:24.2: 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:14:15.94 +51:38:24.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.3414* 00 14 15.94 +51 38 24.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
DocumentRef: VOTx246789,2461274.8414,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
DocumentRef: VOTx246789 20260822.3414 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.3414 2461274.8414 14.35 23:19:11.20 +49:46:33.1
108.02739 -10.40740 galactic And Second-epoch detections are separated by 7.8" and 7.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 J349.7823+49.7684 | 23:19:11.20 +49:46:33.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:19:11.20 +49:46:33.1: 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:19:11.20 +49:46:33.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.3414* 23 19 11.20 +49 46 33.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
ATO J349.7823+49.7684,2461274.8414,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
ATO J349.7823+49.7684 20260822.3414 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.3414 2461274.8414 14.32 23:26:08.38 +54:33:35.2
110.68452 -6.27098 galactic Cas Second-epoch detections are separated by 3.0" 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 | DocumentRef: VOTx277784 | 23:26:08.38 +54:33:35.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:26:08.38 +54:33:35.2: 15.27 +/- 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:08.38 +54:33:35.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.3414* 23 26 08.38 +54 33 35.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
DocumentRef: VOTx277784,2461274.8414,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: VOTx277784 20260822.3414 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.3414 2461274.8414 14.16 23:27:28.85 +54:50:53.7
110.96267 -6.06058 galactic Cas Second-epoch detections are separated by 1.3" 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 | ATO J351.8904+54.8483 | 23:27:28.85 +54:50:53.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:27:28.85 +54:50:53.7: 15.35 +/- 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:28.85 +54:50:53.7: 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.3414* 23 27 28.85 +54 50 53.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
ATO J351.8904+54.8483,2461274.8414,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
ATO J351.8904+54.8483 20260822.3414 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.3414 2461274.8414 14.27 00:20:07.24 +55:23:46.8
118.45970 -7.20324 galactic Cas Second-epoch detections are separated by 8.4" and 7.4 pix
The object was found in VSX24" Gaia DR3 419888857701285504
Type: VAR
# Max. Min./Amp. JD0 Period
13.030 G 13.140 G 0.025187400000 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 00:20:07.24 +55:23:46.8: 15.52 +/- 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:20:07.24 +55:23:46.8: 14.96 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.52 +/- 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.3414* 00 20 07.24 +55 23 46.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
Gaia DR3 419888857701285504,2461274.8414,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
Gaia DR3 419888857701285504 20260822.3414 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.3414 2461274.8414 14.19 23:26:19.55 +55:50:52.0
111.13030 -5.06149 galactic Cas Second-epoch detections are separated by 7.7" and 7.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:26:19.55 +55:50: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 23:26:19.55 +55:50:52.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:26:19.55 +55:50:52.0: 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.3414* 23 26 19.55 +55 50 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.8414,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.3414 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.3414 2461274.8414 14.32 23:33:42.98 +53:53:38.6
111.53467 -7.24893 galactic Cas Second-epoch detections are separated by 4.5" and 7.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: VOTx357807 | 23:33:42.98 +53:53:38.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:33:42.98 +53:53:38.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 23:33:42.98 +53:53:38.6: 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.3414* 23 33 42.98 +53 53 38.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
DocumentRef: VOTx357807,2461274.8414,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: VOTx357807 20260822.3414 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.3414 2461274.8414 14.09 23:20:42.74 +52:39:38.0
109.27767 -7.78926 galactic And Second-epoch detections are separated by 1.9" 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 | 23:20:42.74 +52:39: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:20:42.74 +52:39:38.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:20:42.74 +52:39:38.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.3414* 23 20 42.74 +52 39 38.0 14.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.8414,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.3414 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.3414 2461274.8414 14.31 23:22:56.11 +53:23:03.4
109.84422 -7.22358 galactic Cas Second-epoch detections are separated by 7.1" and 7.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: VOTx404661 | 23:22:56.11 +53:23:03.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 23:22:56.11 +53:23:03.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:56.11 +53:23:03.4: 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.3414* 23 22 56.11 +53 23 03.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
DocumentRef: VOTx404661,2461274.8414,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: VOTx404661 20260822.3414 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.3414 2461274.8414 14.35 00:24:44.60 +53:17:26.5
118.89454 -9.37166 galactic Cas Second-epoch detections are separated by 7.2" and 7.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 419469497101020288 | 00:24:47.43 +53:16:47.8 (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:24:44.60 +53:17:26.5: 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:24:44.60 +53:17:26.5: 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.3414* 00 24 44.60 +53 17 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
Gaia DR3 419469497101020288,2461274.8414,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
Gaia DR3 419469497101020288 20260822.3414 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.3414 2461274.8414 14.19 23:55:41.04 +51:20:12.0
114.12586 -10.57929 galactic Cas Second-epoch detections are separated by 8.8" and 7.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:41.04 +51:20:12.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:55:41.04 +51:20:12.0: 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:55:41.04 +51:20:12.0: 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.3414* 23 55 41.04 +51 20 12.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.8414,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.3414 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.3414 2461274.8414 14.38 23:26:49.98 +50:38:35.5
109.49610 -10.00825 galactic And Second-epoch detections are separated by 7.6" 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 | 23:26:49.98 +50:38:35.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:26:49.98 +50:38:35.5: 15.47 +/- 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:26:49.98 +50:38:35.5: 14.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.47 +/- 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.3414* 23 26 49.98 +50 38 35.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.8414,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.3414 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.3414 2461274.8414 14.35 23:19:24.36 +56:40:25.8
110.50150 -3.96036 galactic Cas Second-epoch detections are separated by 5.0" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:24.36 +56:40:25.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:19:24.36 +56:40:25.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:19:24.36 +56:40:25.8: 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.3414* 23 19 24.36 +56 40 25.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.8414,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.3414 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.3414 2461274.8414 14.31 00:07:16.39 +54:17:21.5
116.44990 -8.02566 galactic Cas Second-epoch detections are separated by 4.5" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:16.39 +54:17:21.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.39 +54:17:21.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:07:16.39 +54:17:21.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.3414* 00 07 16.39 +54 17 21.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.8414,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.3414 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.3414 2461274.8414 14.18 00:14:54.54 +52:36:35.4
117.31810 -9.86330 galactic Cas Second-epoch detections are separated by 7.1" and 7.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:14:54.54 +52:36:35.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:14:54.54 +52:36:35.4: 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 00:14:54.54 +52:36:35.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.3414* 00 14 54.54 +52 36 35.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.8414,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.3414 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.3414 2461274.8414 14.29 23:16:32.11 +53:16:20.1
108.90251 -6.99471 galactic Cas Second-epoch detections are separated by 8.9" and 7.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: VOTx913878 | 23:16:32.11 +53:16:20.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:16:32.11 +53:16:20.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:16:32.11 +53:16:20.1: 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.3414* 23 16 32.11 +53 16 20.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: VOTx913878,2461274.8414,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: VOTx913878 20260822.3414 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.3414 2461274.8414 14.35 00:15:46.58 +50:56:07.8
117.21118 -11.53971 galactic Cas Second-epoch detections are separated by 4.6" and 7.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:15:46.58 +50:56: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 00:15:46.58 +50:56:07.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 00:15:46.58 +50:56:07.8: 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.3414* 00 15 46.58 +50 56 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.8414,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.3414 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.3414 2461274.8414 14.27 23:18:10.20 +54:54:18.8
109.71481 -5.55522 galactic Cas Second-epoch detections are separated by 8.3" 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 | DocumentRef: VOTx929109 | 23:18:10.20 +54:54:18.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:18:10.20 +54:54:18.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:18:10.20 +54:54:18.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.3414* 23 18 10.20 +54 54 18.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: VOTx929109,2461274.8414,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: VOTx929109 20260822.3414 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.3414 2461274.8414 14.27 23:22:53.15 +57:44:50.0
111.31311 -3.11309 galactic Cas Second-epoch detections are separated by 2.6" and 7.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:22:53.15 +57:44:50.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:22:53.15 +57:44:50.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:22:53.15 +57:44:50.0: 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.3414* 23 22 53.15 +57 44 50.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.8414,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.3414 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.3414 2461274.8414 14.23 23:17:25.89 +53:38:26.6
109.16119 -6.69872 galactic Cas Second-epoch detections are separated by 5.8" 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 | DocumentRef: VOTx1112199 | 23:17:25.89 +53:38:26.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:25.89 +53:38:26.6: 15.34 +/- 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:25.89 +53:38:26.6: 14.83 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.34 +/- 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.3414* 23 17 25.89 +53 38 26.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
DocumentRef: VOTx1112199,2461274.8414,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: VOTx1112199 20260822.3414 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.3414 2461274.8414 14.41 23:12:46.68 +56:35:07.2
109.61748 -3.71437 galactic Cas Second-epoch detections are separated by 3.8" 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 | 23:12:46.68 +56:35:07.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:12:46.68 +56:35:07.2: 15.17 +/- 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:46.68 +56:35:07.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.3414* 23 12 46.68 +56 35 07.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.8414,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.3414 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.3414 2461274.8414 14.40 23:42:45.94 +54:49:23.6
113.07256 -6.72859 galactic Cas Second-epoch detections are separated by 6.3" and 7.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: VOTx1180456 | 23:42:45.94 +54:49:23.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:42:45.94 +54:49:23.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:42:45.94 +54:49:23.6: 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.3414* 23 42 45.94 +54 49 23.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
DocumentRef: VOTx1180456,2461274.8414,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: VOTx1180456 20260822.3414 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.3414 2461274.8414 14.40 23:57:57.23 +51:06:43.5
114.43032 -10.87467 galactic Cas Second-epoch detections are separated by 1.9" and 7.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:57:57.23 +51:06:43.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:57:57.23 +51:06:43.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:57:57.23 +51:06:43.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.3414* 23 57 57.23 +51 06 43.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.8414,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.3414 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.3414 2461274.8414 14.32 23:26:31.44 +55:59:44.4
111.20474 -4.93056 galactic Cas Second-epoch detections are separated by 5.9" and 7.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: VOTx1292064 | 23:26:31.44 +55:59:44.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:26:31.44 +55:59:44.4: 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:26:31.44 +55:59:44.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.3414* 23 26 31.44 +55 59 44.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
DocumentRef: VOTx1292064,2461274.8414,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: VOTx1292064 20260822.3414 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.3414 2461274.8414 14.36 23:51:07.43 +50:04:53.9
113.11876 -11.63740 galactic Cas Second-epoch detections are separated by 3.2" and 7.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:51:07.43 +50: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:51:07.43 +50:04:53.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 23:51:07.43 +50:04:53.9: 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.3414* 23 51 07.43 +50 04 53.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.8414,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.3414 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.3414 2461274.8414 14.44 00:00:24.11 +51:47:09.1
114.95040 -10.29322 galactic Cas Second-epoch detections are separated by 7.8" and 7.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:00:24.11 +51:47: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 00:00:24.11 +51:47:09.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:00:24.11 +51:47:09.1: 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.3414* 00 00 24.11 +51 47 09.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.8414,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.3414 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.3414 2461274.8414 14.49 00:12:51.74 +50:33:59.7
116.69038 -11.83708 galactic Cas Second-epoch detections are separated by 7.1" and 7.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: VOTx1417388 | 00:12:51.74 +50:33:59.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 00:12:51.74 +50:33:59.7: 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:12:51.74 +50:33:59.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.3414* 00 12 51.74 +50 33 59.7 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
DocumentRef: VOTx1417388,2461274.8414,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx1417388 20260822.3414 14.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.42 23:17:43.46 +50:37:44.9
108.11440 -9.52678 galactic And Second-epoch detections are separated by 8.9" and 7.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:43.46 +50:37: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:17:43.46 +50:37:44.9: 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:17:43.46 +50:37:44.9: 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.3414* 23 17 43.46 +50 37 44.9 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.8414,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
target 20260822.3414 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.3414 2461274.8414 14.37 00:24:22.38 +56:28:53.4
119.17968 -6.19294 galactic Cas Second-epoch detections are separated by 2.0" and 7.5 pix
The object was found in VSX 8" Gaia DR3 421365467460218368
Type: ROT
# Max. Min./Amp. JD0 Period
15.340 G 15.380 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:24:22.38 +56:28:53.4: 15.33 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:24:22.38 +56:28:53.4: 14.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.33 +/- 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.3414* 00 24 22.38 +56 28 53.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
Gaia DR3 421365467460218368,2461274.8414,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
Gaia DR3 421365467460218368 20260822.3414 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.3414 2461274.8414 14.33 00:24:09.22 +50:06:56.0
118.45747 -12.51900 galactic Cas Second-epoch detections are separated by 7.5" and 7.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:09.22 +50:06:56.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:24:09.22 +50:06:56.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:24:09.22 +50:06:56.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.3414* 00 24 09.22 +50 06 56.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.53 00:06:12.63 +51:04:14.6
115.71790 -11.16643 galactic Cas Second-epoch detections are separated by 6.2" and 7.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:06:12.63 +51:04:14.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:06:12.63 +51:04:14.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:06:12.63 +51:04:14.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.3414* 00 06 12.63 +51 04 14.6 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.8414,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.3414 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.3414 2461274.8414 14.33 00:01:21.08 +53:54:25.4
115.51698 -8.24204 galactic Cas Second-epoch detections are separated by 3.6" and 7.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:01:21.08 +53:54:25.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:01:21.08 +53:54:25.4: 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:01:21.08 +53:54:25.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.3414* 00 01 21.08 +53 54 25.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.42 23:23:13.93 +56:37:19.1
110.97917 -4.18888 galactic Cas Second-epoch detections are separated by 0.6" 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 | 23:23:13.93 +56:37:19.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:13.93 +56:37:19.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 23:23:13.93 +56:37:19.1: 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.3414* 23 23 13.93 +56 37 19.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.8414,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
target 20260822.3414 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.3414 2461274.8414 14.32 23:25:02.24 +54:21:52.4
110.46789 -6.40295 galactic Cas Second-epoch detections are separated by 4.8" 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 | 23:25:02.24 +54:21:52.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:25:02.24 +54:21:52.4: 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:25:02.24 +54:21:52.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.3414* 23 25 02.24 +54 21 52.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.8414,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.3414 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.3414 2461274.8414 14.51 23:46:36.30 +51:22:55.7
112.73631 -10.20162 galactic Cas Second-epoch detections are separated by 4.0" and 7.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:36.30 +51:22: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:46:36.30 +51:22:55.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:46:36.30 +51:22:55.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.3414* 23 46 36.30 +51 22 55.7 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.8414,14.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 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.3414 2461274.8414 14.37 00:28:59.75 +53:42:07.5
119.57241 -9.02321 galactic Cas Second-epoch detections are separated by 5.9" and 7.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 J007.2623+53.7031 | 00:28:59.75 +53:42:07.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:28:59.75 +53:42:07.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 00:28:59.75 +53:42:07.5: 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.3414* 00 28 59.75 +53 42 07.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 J007.2623+53.7031,2461274.8414,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
ATO J007.2623+53.7031 20260822.3414 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.3414 2461274.8414 14.54 00:09:54.87 +51:05:44.9
116.30657 -11.24100 galactic Cas Second-epoch detections are separated by 5.1" and 7.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:54.87 +51:05: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 00:09:54.87 +51:05:44.9: 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:09:54.87 +51:05:44.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.3414* 00 09 54.87 +51 05 44.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.8414,14.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.3414 14.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.3414 2461274.8414 14.30 00:08:37.39 +53:17:20.7
116.47689 -9.04521 galactic Cas Second-epoch detections are separated by 2.0" and 7.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:37.39 +53:17:20.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 00:08:37.39 +53:17:20.7: 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 00:08:37.39 +53:17:20.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.3414* 00 08 37.39 +53 17 20.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.8414,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.3414 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.3414 2461274.8414 14.33 00:18:21.43 +52:39:28.2
117.85082 -9.88725 galactic Cas Second-epoch detections are separated by 8.0" and 7.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:18:21.43 +52:39:28.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:18:21.43 +52:39:28.2: 15.45 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:18:21.43 +52:39:28.2: 15.03 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.45 +/- 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.3414* 00 18 21.43 +52 39 28.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.8414,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.38 23:31:56.27 +55:25:40.4
111.75291 -5.70888 galactic Cas Second-epoch detections are separated by 3.5" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:56.27 +55:25: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:31:56.27 +55:25:40.4: 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:31:56.27 +55:25:40.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.3414* 23 31 56.27 +55 25 40.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.8414,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.3414 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.3414 2461274.8414 14.45 23:41:51.34 +54:18:07.8
112.80465 -7.19569 galactic Cas Second-epoch detections are separated by 6.7" and 7.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:51.34 +54:18: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:41:51.34 +54:18:07.8: 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:51.34 +54:18:07.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.3414* 23 41 51.34 +54 18 07.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.8414,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.3414 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.3414 2461274.8414 14.46 23:58:09.16 +50:28:52.3
114.32696 -11.49815 galactic Cas Second-epoch detections are separated by 4.5" and 7.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:58:09.16 +50:28:52.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:58:09.16 +50:28:52.3: 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:58:09.16 +50:28:52.3: 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.3414* 23 58 09.16 +50 28 52.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.8414,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.3414 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.3414 2461274.8414 14.29 23:48:20.07 +51:27:53.8
113.02257 -10.18860 galactic Cas Second-epoch detections are separated by 7.9" and 7.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: VOTx2016218 | 23:48:20.07 +51:27:53.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:48:20.07 +51:27:53.8: 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:48:20.07 +51:27:53.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.3414* 23 48 20.07 +51 27 53.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: VOTx2016218,2461274.8414,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: VOTx2016218 20260822.3414 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.3414 2461274.8414 14.59 23:35:43.27 +49:56:04.9
110.64544 -11.12212 galactic And 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 | DocumentRef: VOTx2046682 | 23:35:43.27 +49:56:04.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:35:43.27 +49:56:04.9: 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:35:43.27 +49:56:04.9: 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.3414* 23 35 43.27 +49 56 04.9 14.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2046682,2461274.8414,14.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2046682 20260822.3414 14.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.55 23:41:30.99 +50:42:02.5
111.76981 -10.64945 galactic Cas Second-epoch detections are separated by 2.8" and 7.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: VOTx2102675 | 23:41:30.99 +50:42:02.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:41:30.99 +50:42:02.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 23:41:30.99 +50:42:02.5: 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.3414* 23 41 30.99 +50 42 02.5 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2102675,2461274.8414,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DocumentRef: VOTx2102675 20260822.3414 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.38 23:33:38.32 +57:50:17.3
112.70322 -3.48026 galactic Cas Second-epoch detections are separated by 4.2" and 7.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: VOTx2205373 | 23:33:38.32 +57:50:17.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:33:38.32 +57:50:17.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:33:38.32 +57:50:17.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.3414* 23 33 38.32 +57 50 17.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: VOTx2205373,2461274.8414,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: VOTx2205373 20260822.3414 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.3414 2461274.8414 14.34 23:38:09.74 +50:55:35.9
111.31619 -10.28505 galactic Cas Second-epoch detections are separated by 3.0" and 7.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:38:09.74 +50:55:35.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:38:09.74 +50:55:35.9: 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:38:09.74 +50:55:35.9: 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.3414* 23 38 09.74 +50 55 35.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.8414,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.3414 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.3414 2461274.8414 14.47 23:16:57.80 +55:08:21.1
109.63615 -5.27501 galactic Cas Second-epoch detections are separated by 3.1" 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 | DocumentRef: VOTx2382613 | 23:16:57.80 +55:08:21.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:16:57.80 +55:08:21.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:16:57.80 +55:08:21.1: 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.3414* 23 16 57.80 +55 08 21.1 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
DocumentRef: VOTx2382613,2461274.8414,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
DocumentRef: VOTx2382613 20260822.3414 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.3414 2461274.8414 14.40 00:10:38.72 +56:15:30.5
117.25521 -6.16300 galactic Cas Second-epoch detections are separated by 8.8" and 7.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:38.72 +56:15:30.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:10:38.72 +56:15:30.5: 15.60 +/- 0.34 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 00:10:38.72 +56:15:30.5: 15.10 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.60 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 08 22.3414* 00 10 38.72 +56 15 30.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.8414,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.3414 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.3414 2461274.8414 14.53 23:42:54.31 +54:20:57.0
112.96592 -7.19112 galactic Cas Second-epoch detections are separated by 1.9" and 7.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: VOTx2483513 | 23:42:54.31 +54:20:57.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:42:54.31 +54:20:57.0: 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:42:54.31 +54:20:57.0: 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.3414* 23 42 54.31 +54 20 57.0 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
DocumentRef: VOTx2483513,2461274.8414,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
DocumentRef: VOTx2483513 20260822.3414 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.3414 2461274.8414 14.36 23:45:41.18 +50:59:07.9
112.49223 -10.54859 galactic Cas Second-epoch detections are separated by 6.7" and 7.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:45:41.18 +50:59:07.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:41.18 +50:59:07.9: 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:45:41.18 +50:59:07.9: 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.3414* 23 45 41.18 +50 59 07.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.8414,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.3414 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.3414 2461274.8414 14.36 23:23:07.37 +53:42:19.1
109.97982 -6.93079 galactic Cas Second-epoch detections are separated by 8.7" and 6.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:23:07.37 +53:42:19.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:07.37 +53:42:19.1: 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:07.37 +53:42:19.1: 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.3414* 23 23 07.37 +53 42 19.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.8414,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.3414 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.3414 2461274.8414 14.32 23:30:13.07 +56:22:02.0
111.81207 -4.74090 galactic Cas Second-epoch detections are separated by 2.4" 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 | DocumentRef: VOTx2614565 | 23:30:13.07 +56:22:02.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:30:13.07 +56:22:02.0: 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:13.07 +56:22:02.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.3414* 23 30 13.07 +56 22 02.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: VOTx2614565,2461274.8414,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: VOTx2614565 20260822.3414 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.3414 2461274.8414 14.46 23:19:42.83 +50:14:40.0
108.27610 -9.99896 galactic And Second-epoch detections are separated by 8.7" and 7.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:42.83 +50:14:40.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:19:42.83 +50:14:40.0: 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:19:42.83 +50:14:40.0: 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.3414* 23 19 42.83 +50 14 40.0 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.8414,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.3414 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.3414 2461274.8414 14.54 23:19:36.79 +50:35:39.9
108.38593 -9.66575 galactic And Second-epoch detections are separated by 7.7" and 7.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:19:36.79 +50:35: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 23:19:36.79 +50:35:39.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:19:36.79 +50:35:39.9: 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.3414* 23 19 36.79 +50 35 39.9 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.8414,14.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.3414 14.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.3414 2461274.8414 14.43 23:56:02.02 +51:54:41.2
114.30661 -10.03002 galactic Cas Second-epoch detections are separated by 5.0" and 7.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: VOTx2758222 | 23:56:02.02 +51:54:41.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:56:02.02 +51:54:41.2: 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 23:56:02.02 +51:54:41.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.3414* 23 56 02.02 +51 54 41.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
DocumentRef: VOTx2758222,2461274.8414,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: VOTx2758222 20260822.3414 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.3414 2461274.8414 14.46 00:16:21.13 +53:48:36.6
117.70555 -8.70516 galactic Cas Second-epoch detections are separated by 1.1" and 8.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:21.13 +53:48: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 00:16:21.13 +53:48:36.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 00:16:21.13 +53:48:36.6: 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.3414* 00 16 21.13 +53 48 36.6 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.8414,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.3414 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.3414 2461274.8414 14.54 23:51:03.48 +53:48:39.5
113.99887 -8.01024 galactic Cas Second-epoch detections are separated by 4.6" and 6.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J357.7737+53.8040 | 23:51:03.48 +53:48:39.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 23:51:03.48 +53:48:39.5: 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 23:51:03.48 +53:48:39.5: 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.3414* 23 51 03.48 +53 48 39.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
ATO J357.7737+53.8040,2461274.8414,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.7737+53.8040 20260822.3414 14.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.3414 2461274.8414 14.44 23:43:22.46 +52:13:17.4
112.46659 -9.26179 galactic Cas Second-epoch detections are separated by 4.4" and 7.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 J355.8519+52.2124 | 23:43:22.46 +52:13:17.4 (user input) | CBF (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:43:22.46 +52:13:17.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:43:22.46 +52:13:17.4: 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.3414* 23 43 22.46 +52 13 17.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
ATO J355.8519+52.2124,2461274.8414,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
ATO J355.8519+52.2124 20260822.3414 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.3414 2461274.8414 14.41 23:24:24.72 +53:44:34.2
110.17350 -6.95925 galactic Cas Second-epoch detections are separated by 0.8" and 7.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:24:24.72 +53:44: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:24:24.72 +53:44:34.2: 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:24.72 +53:44:34.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.3414* 23 24 24.72 +53 44 34.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.8414,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.3414 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.3414 2461274.8414 14.45 23:24:40.83 +50:27:52.6
109.10849 -10.06397 galactic And Second-epoch detections are separated by 5.3" and 7.2 pix
The object was found in VSX20" Gaia DR3 1991203635076959488
Type:
# Max. Min./Amp. JD0 Period
17.970 G 18.060 G
ATTENTION: measured mag 14.45 is 3.5 mag brighter than the VSX record maximum brightness 17.97 - 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:24:40.83 +50:27:52.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:24:40.83 +50:27:52.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.3414* 23 24 40.83 +50 27 52.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
Gaia DR3 1991203635076959488,2461274.8414,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
Gaia DR3 1991203635076959488 20260822.3414 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.3414 2461274.8414 14.53 23:36:35.61 +53:39:17.1
111.87373 -7.60236 galactic Cas Second-epoch detections are separated by 8.6" and 7.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: VOTx2934744 | 23:36:33.97 +53:38:38.0 (Gaia DR3) | (GCVS) | (GCVS) | 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:36:35.61 +53:39:17.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:36:35.61 +53:39:17.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.3414* 23 36 35.61 +53 39 17.1 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
DocumentRef: VOTx2934744,2461274.8414,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
DocumentRef: VOTx2934744 20260822.3414 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.3414 2461274.8414 14.50 23:22:12.61 +52:12:31.6
109.33727 -8.29199 galactic And Second-epoch detections are separated by 6.6" and 7.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:12.61 +52:12:31.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:22:12.61 +52:12:31.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:22:12.61 +52:12:31.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.3414* 23 22 12.61 +52 12 31.6 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.8414,14.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260822.3414 14.50CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 08 22.3414 2461274.8414 14.38 23:23:01.05 +53:16:37.0
109.81934 -7.32876 galactic Cas Second-epoch detections are separated by 6.6" and 7.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:01.05 +53:16:37.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:01.05 +53:16:37.0: 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.05 +53:16:37.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.3414* 23 23 01.05 +53 16 37.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.8414,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.3414 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.3414 2461274.8414 14.23 23:17:45.15 +56:02:13.8
110.06196 -4.47577 galactic Cas Second-epoch detections are separated by 4.5" 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 | target | 23:17:45.15 +56:02: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:17:45.15 +56:02:13.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:17:45.15 +56:02:13.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.3414* 23 17 45.15 +56 02 13.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.8414,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.3414 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.3414 2461274.8414 14.51 23:22:37.19 +56:31:56.8
110.86937 -4.24486 galactic Cas Second-epoch detections are separated by 2.8" and 7.2 pix
The object was found in VSX19" ZTF J232237.51+563137.9
Type: EW
# Max. Min./Amp. JD0 Period
20.205 r Y 0.524 r 2458319.95810 0.259130400000
ATTENTION: measured mag 14.51 is 5.2 mag brighter than the VSX record maximum brightness 19.68 - 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:22:37.19 +56:31:56.8: 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:22:37.19 +56:31:56.8: 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.3414* 23 22 37.19 +56 31 56.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
ZTF J232237.51+563137.9,2461274.8414,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
ZTF J232237.51+563137.9 20260822.3414 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.3414 2461274.8414 14.45 23:42:17.05 +55:27:07.3
113.17364 -6.10406 galactic Cas Second-epoch detections are separated by 8.0" and 7.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: VOTx3409719 | 23:42:17.05 +55:27: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:42:17.05 +55:27:07.3: 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:42:17.05 +55:27:07.3: 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.3414* 23 42 17.05 +55 27 07.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: VOTx3409719,2461274.8414,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
DocumentRef: VOTx3409719 20260822.3414 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.3414 2461274.8414 14.54 23:46:10.21 +55:17:36.1
113.66875 -6.40019 galactic Cas Second-epoch detections are separated by 2.2" and 7.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: VOTx3562881 | 23:46:10.21 +55:17:36.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:46:10.21 +55:17:36.1: 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:46:10.21 +55:17:36.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.3414* 23 46 10.21 +55 17 36.1 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
DocumentRef: VOTx3562881,2461274.8414,14.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
DocumentRef: VOTx3562881 20260822.3414 14.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.3414 2461274.8414 14.23 23:36:05.03 +55:53:53.4
112.45397 -5.43303 galactic Cas Second-epoch detections are separated by 1.3" and 7.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:05.03 +55:53:53.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:36:05.03 +55:53:53.4: 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:05.03 +55:53:53.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.3414* 23 36 05.03 +55 53 53.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.8414,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.3414 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.3414 2461274.8414 14.46 23:25:25.15 +57:39:33.7
111.60373 -3.30811 galactic Cas Second-epoch detections are separated by 6.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 | DocumentRef: VOTx3484796 | 23:25:25.15 +57:39:33.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:25.15 +57:39:33.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:25:25.15 +57:39:33.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.3414* 23 25 25.15 +57 39 33.7 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
DocumentRef: VOTx3484796,2461274.8414,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
DocumentRef: VOTx3484796 20260822.3414 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
## 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.84175508 22.08.2026 08:11:57.639 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 17
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: 9 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): 18258
Objects passed selection criteria: 18250
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: 18341.8
Average stars matched: 18149.5 (98.9518 %)
Memory usage VmPeak: 247840 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:21:24 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.84175508 22.08.2026 08:11:57.639 /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 1279
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: 248 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): 138975
Objects passed selection criteria: 138774
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: 130883
Average stars matched: 125569 (95.9395 %)
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:15 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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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.84110317
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-11-01_20.00sec_-0.00C_LIGHT_0070.fits exists and is non-empty
wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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.950 +54:01:14.63 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 23:59:57.950 +54:01:14.63
Angular distance between the image centers 0.0216 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-11-57_20.00sec_-0.00C_LIGHT_0071.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
Image size: 926.6'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:59.917 +54:01:54.21 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:59.917 +54:01:54.21
Angular distance between the image centers 0.0313 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 23:59:57.950 +54:01:14.63
Second-epoch second image center 23:59:59.917 +54:01:54.21
Angular distance between the image centers 0.01200 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.DOSmUAjGUZ
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.LZRtMFgNrF
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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits &> /tmp/tmp.FciffppHkq
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits &> /tmp/tmp.KREX86qEx5
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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 14 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-11-01_20.00sec_-0.00C_LIGHT_0070.fits
2.2 pix fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits
14.7 mag. fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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.DOSmUAjGUZ (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/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.LZRtMFgNrF (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/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.FciffppHkq (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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=1650, bad_region=4655, passed=21989
Got 21989 stars (including 15934 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat
util/solve_plate_with_UCAC5 got 21989 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.1047 through 0 to 14.8810, gap 14.8810 to 345.1047
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 3498 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2163 matched stars entering correct_measured_positions(), 2377 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.46"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2014 matched stars entering correct_measured_positions(), 18166 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.08"
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.1068 through 0 to 14.8990, gap 14.8990 to 345.1068
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 3604 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2424 matched stars entering correct_measured_positions(), 18166 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.23"
Accuracy estimation diagnostic: 2355 matched stars entering correct_measured_positions(), 18250 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.14"
Excluding outliers - 2355 stars left (next iteration limit 2215)
SIP_REFIT: SIP order 2 trial: matched=2355 robust_rms=26.275 arcsec worst_quadrant_rms=29.051 arcsec
SIP_REFIT: SIP order 3 trial: matched=2355 robust_rms=25.636 arcsec worst_quadrant_rms=29.750 arcsec
SIP_REFIT: SIP order 5 trial: matched=2355 robust_rms=23.454 arcsec worst_quadrant_rms=28.947 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2355 robust_rms_before=31.974 arcsec robust_rms_before_corrected=19.435 arcsec robust_rms_after=26.275 arcsec worst_quadrant_rms_before=24.512 worst_quadrant_rms_after=29.051
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.512 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits N_match=2355 sigma_overall_arcsec=13.115 sigma_q1_arcsec=28.709 sigma_q2_arcsec=28.482 sigma_q3_arcsec=6.909 sigma_q4_arcsec=5.536 n_q1=520 n_q2=280 n_q3=925 n_q4=630 worst_quadrant_to_overall_ratio=2.189
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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.KREX86qEx5 (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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=1635, bad_region=4615, passed=21977
Got 21977 stars (including 15947 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat
util/solve_plate_with_UCAC5 got 21977 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.6'
Seting catalog search parameters based on the expected field of view 926.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012869 (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.010296 (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.1042 through 0 to 14.8807, gap 14.8807 to 345.1042
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 3501 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2154 matched stars entering correct_measured_positions(), 2385 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.47"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2014 matched stars entering correct_measured_positions(), 18198 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.01"
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.1066 through 0 to 14.8985, gap 14.8985 to 345.1066
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 3591 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(), 18198 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.18"
Accuracy estimation diagnostic: 2364 matched stars entering correct_measured_positions(), 18276 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.14"
Excluding outliers - 2364 stars left (next iteration limit 2215)
SIP_REFIT: SIP order 2 trial: matched=2364 robust_rms=26.490 arcsec worst_quadrant_rms=29.330 arcsec
SIP_REFIT: SIP order 3 trial: matched=2364 robust_rms=25.808 arcsec worst_quadrant_rms=30.123 arcsec
SIP_REFIT: SIP order 5 trial: matched=2364 robust_rms=23.447 arcsec worst_quadrant_rms=29.243 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2364 robust_rms_before=31.810 arcsec robust_rms_before_corrected=19.503 arcsec robust_rms_after=26.490 arcsec worst_quadrant_rms_before=24.604 worst_quadrant_rms_after=29.330
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.604 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits N_match=2364 sigma_overall_arcsec=13.656 sigma_q1_arcsec=30.041 sigma_q2_arcsec=29.302 sigma_q3_arcsec=7.009 sigma_q4_arcsec=5.090 n_q1=531 n_q2=276 n_q3=947 n_q4=610 worst_quadrant_to_overall_ratio=2.200
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits'
Saving the final (post-refit) wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits sigma_overall=13.115 worst_q_ratio=2.189
new2=fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits sigma_overall=13.656 worst_q_ratio=2.200
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-11-01_20.00sec_-0.00C_LIGHT_0070.fits) flagged: sigma=13.115 (ref avg 0.463), ratio=2.189 (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/lib/make_outxyls_for_astrometric_calibration found 21139 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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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: "out1181546.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1181546.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 25.7001 (1.4502e+11), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.989,54.0191), pixel scale 5.92971 arcsec/pix.
Hit/miss: Hit/miss: ----+++------+----+-+---+---+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1181546.solved to indicate this.
Field: out1181546.xyls
Field center: (RA,Dec) = (359.990059, 54.019918) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:57.614, +54:01:11.704).
Field size: 15.6022 x 10.4297 degrees
Field rotation angle: up is 4.49981 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits' -> 'fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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:23 fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:23 out1181546.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits (fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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: "out1181546.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1181546.axy"...
Only searching for solutions within 15.4417 degrees of RA,Dec (359.991,54.0207)
log-odds ratio 25.7001 (1.4502e+11), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.989,54.0191), pixel scale 5.92971 arcsec/pix.
Hit/miss: Hit/miss: ----+++------+----+-+---+---+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1181546.solved to indicate this.
Field: out1181546.xyls
Field center: (RA,Dec) = (359.990059, 54.019918) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:57.614, +54:01:11.704).
Field size: 15.6022 x 10.4297 degrees
Field rotation angle: up is 4.49981 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:23 fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:24 out1181546.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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.950 +54:01:14.63 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 21989 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/correct_sextractor_wcs_catalog_usingxy2sky1184503.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-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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=1650, bad_region=4655, passed=21989
Got 21989 stars (including 15934 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat
util/solve_plate_with_UCAC5 got 21989 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.1047 through 0 to 14.8810, gap 14.8810 to 345.1047
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 3498 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2163 matched stars entering correct_measured_positions(), 2377 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.46"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2014 matched stars entering correct_measured_positions(), 18166 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.08"
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.1068 through 0 to 14.8990, gap 14.8990 to 345.1068
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 3604 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 2424 matched stars entering correct_measured_positions(), 18166 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.23"
Accuracy estimation diagnostic: 2355 matched stars entering correct_measured_positions(), 18250 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.14"
Excluding outliers - 2355 stars left (next iteration limit 2215)
SIP_REFIT: SIP order 2 trial: matched=2355 robust_rms=26.275 arcsec worst_quadrant_rms=29.051 arcsec
SIP_REFIT: SIP order 3 trial: matched=2355 robust_rms=25.636 arcsec worst_quadrant_rms=29.750 arcsec
SIP_REFIT: SIP order 5 trial: matched=2355 robust_rms=23.454 arcsec worst_quadrant_rms=28.947 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2355 robust_rms_before=31.974 arcsec robust_rms_before_corrected=19.435 arcsec robust_rms_after=26.275 arcsec worst_quadrant_rms_before=24.512 worst_quadrant_rms_after=29.051
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.512 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits N_match=2355 sigma_overall_arcsec=13.115 sigma_q1_arcsec=28.709 sigma_q2_arcsec=28.482 sigma_q3_arcsec=6.909 sigma_q4_arcsec=5.536 n_q1=520 n_q2=280 n_q3=925 n_q4=630 worst_quadrant_to_overall_ratio=2.189
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.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-11-01_20.00sec_-0.00C_LIGHT_0070.fits): sigma 13.115->13.115, ratio 2.189->2.189; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits) flagged: sigma=13.656 (ref avg 0.463), ratio=2.200 (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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/lib/make_outxyls_for_astrometric_calibration found 21186 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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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: "out1185230.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1185230.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 25.6116 (1.32737e+11), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.997,54.0301), pixel scale 5.92992 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----+----+-+-----+-+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1185230.solved to indicate this.
Field: out1185230.xyls
Field center: (RA,Dec) = (359.998253, 54.030911) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:59.581, +54:01:51.280).
Field size: 15.6031 x 10.4304 degrees
Field rotation angle: up is 4.4953 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits' -> 'fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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:24 fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:24 out1185230.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits (fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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: "out1185230.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1185230.axy"...
Only searching for solutions within 15.4433 degrees of RA,Dec (360,54.0317)
log-odds ratio 25.6116 (1.32737e+11), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.997,54.0301), pixel scale 5.92992 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----+----+-+-----+-+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1185230.solved to indicate this.
Field: out1185230.xyls
Field center: (RA,Dec) = (359.998253, 54.030911) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:59.581, +54:01:51.280).
Field size: 15.6031 x 10.4304 degrees
Field rotation angle: up is 4.4953 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:24 fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
-rw-r--r-- 1 apache apache 8.5K Aug 22 03:24 out1185230.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
Image size: 926.6'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:59.917 +54:01:54.21 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 21977 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/correct_sextractor_wcs_catalog_usingxy2sky1186965.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-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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=1635, bad_region=4615, passed=21977
Got 21977 stars (including 15947 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat
util/solve_plate_with_UCAC5 got 21977 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.6'
Seting catalog search parameters based on the expected field of view 926.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012869 (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.010296 (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.1042 through 0 to 14.8807, gap 14.8807 to 345.1042
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 3501 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2154 matched stars entering correct_measured_positions(), 2385 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 22.47"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 2014 matched stars entering correct_measured_positions(), 18198 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.01"
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.1066 through 0 to 14.8985, gap 14.8985 to 345.1066
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 3591 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(), 18198 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.18"
Accuracy estimation diagnostic: 2364 matched stars entering correct_measured_positions(), 18276 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 21.14"
Excluding outliers - 2364 stars left (next iteration limit 2215)
SIP_REFIT: SIP order 2 trial: matched=2364 robust_rms=26.490 arcsec worst_quadrant_rms=29.330 arcsec
SIP_REFIT: SIP order 3 trial: matched=2364 robust_rms=25.808 arcsec worst_quadrant_rms=30.123 arcsec
SIP_REFIT: SIP order 5 trial: matched=2364 robust_rms=23.447 arcsec worst_quadrant_rms=29.243 arcsec
SIP_REFIT: selected SIP order 2
SIP_REFIT: order=2 matched=2364 robust_rms_before=31.810 arcsec robust_rms_before_corrected=19.503 arcsec robust_rms_after=26.490 arcsec worst_quadrant_rms_before=24.604 worst_quadrant_rms_after=29.330
SIP_REFIT: refit does not sufficiently improve on the solution it would replace (best worst-quadrant baseline 24.604 arcsec) - keeping the original
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits N_match=2364 sigma_overall_arcsec=13.656 sigma_q1_arcsec=30.041 sigma_q2_arcsec=29.302 sigma_q3_arcsec=7.009 sigma_q4_arcsec=5.090 n_q1=531 n_q2=276 n_q3=947 n_q4=610 worst_quadrant_to_overall_ratio=2.200
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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_031613_TTUQ2b1x1_966823_xFrhn4Pq/fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits -region wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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-11-57_20.00sec_-0.00C_LIGHT_0071.fits): sigma 13.656->13.656, ratio 2.200->2.200; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=13.115 -- 28.33x the reference average (0.463); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=13.656 -- 29.49x 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-11-01_20.00sec_-0.00C_LIGHT_0070_astrometric_residuals.png (2355 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 12.00 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071_astrometric_residuals.png (2364 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 11.70 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-01_20.00sec_-0.00C_LIGHT_0070.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-08-22_CI_Cas-04-Q2b1x1_031613_TTUQ2b1x1_966823_xFrhn4Pq/wcs_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071.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:29:29.97 +49:37:15.3: 15.38 +/- 0.33 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:34:54.46 +52:08:21.4: 13.50 +/- 0.06 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:15:49.44 +57:32:33.9: 12.60 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:05:30.74 +56:58:33.8: 10.66 +/- 0.00 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 00:00:07.71 +51:20:32.3: 14.52 +/- 0.14 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:21:42.74 +50:06:34.6: 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:57:22.67 +56:41:44.3: 12.16 +/- 0.05 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-18_02-46-42_20.00sec_-0.00C_LIGHTs_0246.fits at 23:32:44.09 +53:36:12.7: 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 00:05:30.74 +56:58:33.8: 10.79 +/- 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:34:54.46 +52:08:21.4: 13.44 +/- 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.71 +51:20:32.3: 14.92 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 10.69 +/- 0.00
Forced photometry reference-image weighted average: 13.48 +/- 0.05
Forced photometry filter KEPT candidate at 23:34:54.46 +52:08:21.4: ref_mag=13.48 +/- 0.05 new_mean_mag=11.4558 delta=2.03 (need > 0.90)
Forced photometry filter REJECTED candidate at 00:05:30.74 +56:58:33.8: ref_mag=10.69 +/- 0.00 new_mean_mag=11.2662 delta=-0.58 (need > 0.90)
Forced photometry reference-image weighted average: 14.52 +/- 0.14
Forced photometry filter KEPT candidate at 00:00:07.71 +51:20:32.3: ref_mag=14.52 +/- 0.14 new_mean_mag=11.5992 delta=2.92 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:57:22.67 +56:41:44.3: 12.06 +/- 0.05 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-07-21_23-21-38_20.00sec_5.00C_LIGHT_0111.fits at 23:32:44.09 +53:36:12.7: 14.83 +/- 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.74 +50:06:34.6: 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:29:29.97 +49:37:15.3: 14.77 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.38 +/- 0.33
Forced photometry filter KEPT candidate at 23:29:29.97 +49:37:15.3: ref_mag=15.38 +/- 0.33 new_mean_mag=12.1693 delta=3.21 (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.44 +57:32:33.9: 12.70 +/- 0.05 detection
Forced photometry reference-image weighted average: 12.12 +/- 0.04
Forced photometry filter REJECTED candidate at 23:57:22.67 +56:41:44.3: ref_mag=12.12 +/- 0.04 new_mean_mag=11.9532 delta=0.16 (need > 0.90)
Forced photometry reference-image weighted average: 12.62 +/- 0.02
Forced photometry filter KEPT candidate at 00:15:49.44 +57:32:33.9: ref_mag=12.62 +/- 0.02 new_mean_mag=11.3908 delta=1.23 (need > 0.90)
Adding exclusion_list_local.txt__out50510.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50551.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50561.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50564.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50574.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out50663.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 935s
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: 7s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50505_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50505_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50510_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 50510_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50513_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50513_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50516_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50516_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (29.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50534_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50534_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50551_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 50551_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50560_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50560_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 50561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 50564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 50574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50580_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50580_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:28:56.42 +57:11:35.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 50637_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 50637_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190433_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190433_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190435_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190435_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190450_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190450_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190454_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190454_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190455_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190455_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190457_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190457_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190459_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190459_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190461_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190461_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190467_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190467_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190480_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190480_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190490_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190490_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190499_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190499_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190517_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190517_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190523_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190523_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190529_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190529_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190532_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190532_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190533_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190533_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190534_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190534_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190538_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190538_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190541_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190541_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190547_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190547_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190553_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190553_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190559_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190559_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190562_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190562_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (33.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190569_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190569_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190570_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190570_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190576_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190576_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190578_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190578_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190580_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190580_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190581_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190581_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190585_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190585_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190587_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190587_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190588_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190588_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190589_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190589_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190590_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190590_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190591_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190591_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190594_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190594_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190595_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190595_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190598_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190598_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190599_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190599_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190600_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190600_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190601_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190601_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190610_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190610_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190612_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190612_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190614_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190614_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (31.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190618_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190618_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190619_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190619_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190630_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190630_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190632_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190632_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190636_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190636_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190637_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190637_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190641_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190641_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190643_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190643_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190645_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190645_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190648_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190648_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190649_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190649_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190653_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190653_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190654_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190654_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190657_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190657_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190659_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190659_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190660_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190660_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190671_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190671_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190682_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190682_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190683_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190683_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190686_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190686_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190688_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190688_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190690_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190690_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190696_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190696_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190697_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190697_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190703_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190703_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190709_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190709_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190712_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190712_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190716_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190716_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190717_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190717_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (34.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190721_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190721_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190722_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190722_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190725_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190725_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190726_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190726_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190727_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190727_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190728_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190728_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190732_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190732_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190739_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190739_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190740_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190740_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190741_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190741_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190742_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190742_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190743_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190743_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190748_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190748_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190749_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190749_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190752_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190752_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190754_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190754_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190755_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190755_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190756_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190756_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190760_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190760_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190764_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190764_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190766_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190766_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190775_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190775_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190778_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190778_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190782_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190782_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190785_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190785_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190790_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190790_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190792_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190792_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190794_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190794_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190795_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190795_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190800_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190800_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190803_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190803_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190806_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190806_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190809_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190809_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190811_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190811_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190812_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190812_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190814_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190814_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190816_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190816_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190817_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190817_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190820_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190820_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190821_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190821_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190826_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190826_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190827_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190827_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190829_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190829_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190835_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190835_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190836_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190836_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190837_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190837_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (60.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190838_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190838_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190839_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190839_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190841_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190841_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190848_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190848_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190850_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190850_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190852_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190852_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190853_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190853_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190857_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190857_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190858_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190858_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190860_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190860_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190861_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190861_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190866_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190866_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190867_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190867_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:28:09.98 +57:27:34.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190868_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190868_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190871_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190871_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190879_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190879_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190885_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190885_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:48:09.95 +55:32:23.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190890_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190890_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190893_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190893_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190896_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190896_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190897_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190897_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190898_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190898_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190904_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190904_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190905_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190905_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190906_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190906_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190909_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190909_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190910_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190910_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190911_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190911_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190912_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190912_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190914_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190914_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190915_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190915_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190921_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190921_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190922_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190922_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190928_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190928_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190933_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190933_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190934_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190934_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190935_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190935_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190936_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190936_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190942_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190942_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190943_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190943_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190945_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190945_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190951_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190951_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (31.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190955_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190955_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190957_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190957_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190961_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190961_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190966_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190966_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190967_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190967_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190968_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190968_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190969_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190969_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190971_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190971_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190973_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190973_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190976_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190976_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190977_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190977_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190978_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190978_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190983_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190983_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190984_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190984_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190985_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190985_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190990_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190990_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190991_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 190991_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190993_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190993_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190996_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190996_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190998_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 190998_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191004_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191004_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191005_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191005_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191008_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191008_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191011_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191011_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191013_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191013_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191014_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191014_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191016_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191016_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191018_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191018_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191022_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191022_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191023_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191023_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191026_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191026_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191028_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191028_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191029_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191029_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191031_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191031_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191034_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191034_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191036_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191036_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191037_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191037_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191038_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191038_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191042_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191042_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191043_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191043_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191044_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191044_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191046_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191046_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191048_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191048_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191051_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191051_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191054_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191054_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191058_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191058_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191065_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191065_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191070_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191070_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191071_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191071_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191072_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191072_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (27.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191075_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191075_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191077_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191077_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191079_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191079_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (31.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191080_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191080_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191083_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191083_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191084_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191084_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191086_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191086_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191089_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191089_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191093_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191093_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191096_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191096_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191099_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191099_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191102_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191102_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191103_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191103_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191105_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191105_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191110_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191110_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191112_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191112_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191118_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191118_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191120_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191120_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191121_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191121_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191126_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191126_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191127_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191127_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191129_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191129_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191135_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191135_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191141_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191141_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191142_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191142_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191145_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191145_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:21:59.18 +57:17:44.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191148_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191148_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191149_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191149_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191155_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191155_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191156_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191156_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191157_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191157_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (28.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191158_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191158_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191161_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191161_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191166_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191166_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191167_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191167_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191168_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191168_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191172_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191172_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191176_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191176_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191177_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191177_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191178_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191178_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191181_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191181_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191182_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191182_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:00:03.17 +58:01:30.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191184_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191184_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191185_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191185_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191188_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191188_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191189_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191189_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191190_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191190_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191193_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191193_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191195_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191195_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191196_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191196_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:24:08.78 +56:40:22.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.90, MAG_FAINT_SEARCH_LIMIT=14.88)GAIADR2_OUTPUT=# 5.701 1997311357750085504 351.03385129553 +56.67249573864 14.8680 14.1105 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.701#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191200_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191200_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191201_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191201_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191204_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191204_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191212_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191212_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191215_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191215_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191216_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191216_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191217_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191217_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191218_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191218_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191221_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191221_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191223_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191223_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (28.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191224_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191224_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191226_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191226_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191227_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191227_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191228_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191228_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191229_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191229_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191230_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191230_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191233_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191233_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191235_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191235_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191236_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191236_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191237_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191237_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191242_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191242_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191245_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191245_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191248_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191248_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191249_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191249_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (34.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191250_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191250_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191252_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191252_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191253_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191253_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191254_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191254_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191256_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191256_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191258_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191258_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191259_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191259_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191261_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191261_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191265_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191265_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191267_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191267_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191270_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191270_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191274_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191274_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191280_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191280_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191281_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191281_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191283_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191283_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191285_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191285_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191286_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191286_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191290_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191290_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191294_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191294_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191298_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191298_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191300_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191300_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191302_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191302_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191309_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191309_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191310_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191310_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191315_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191315_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191316_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191316_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191322_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191322_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191325_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191325_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191332_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191332_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:58:25.37 +55:04:17.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191333_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191333_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191335_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191335_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191336_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191336_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191339_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191339_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191340_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191340_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191343_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191343_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191345_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191345_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191346_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191346_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191347_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191347_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191353_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191353_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191354_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191354_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191355_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191355_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191356_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191356_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191359_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191359_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191360_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191360_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191362_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191362_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191364_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191364_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191366_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191366_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191367_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191367_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191369_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191369_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191372_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191372_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191373_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191373_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191374_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191374_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191375_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191375_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191376_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191376_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191379_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191379_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191380_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191380_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191386_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191386_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191388_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191388_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191389_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191389_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191390_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191390_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191391_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191391_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191393_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191393_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191395_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191395_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191396_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191396_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191399_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191399_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191407_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191407_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191410_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191410_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191411_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191411_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191412_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191412_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191413_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191413_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191421_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191421_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191423_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191423_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191424_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191424_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191425_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191425_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191426_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191426_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191427_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191427_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191429_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191429_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191431_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191431_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:48:57.06 +56:40:25.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191432_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191432_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191433_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191433_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191436_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191436_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191437_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191437_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191438_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191438_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191441_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191441_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191442_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191442_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191443_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191443_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191446_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191446_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191447_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191447_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191449_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191449_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191450_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191450_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191456_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191456_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191462_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191462_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191469_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191469_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191471_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191471_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191472_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191472_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191474_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191474_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191475_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191475_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191478_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191478_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191479_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191479_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191481_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191481_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191483_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191483_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (27.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191488_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191488_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191492_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191492_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191493_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191493_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191494_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191494_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191495_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191495_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191496_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191496_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191497_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191497_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (29.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191498_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191498_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191500_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191500_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191502_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191502_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191506_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191506_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191508_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191508_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191510_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191510_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191512_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191512_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191516_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191516_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (28.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191520_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191520_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191525_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191525_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191527_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191527_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191530_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191530_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191533_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191533_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191537_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191537_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191542_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191542_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191546_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191546_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191547_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191547_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191551_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191551_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191556_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191556_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191562_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191562_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191565_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191565_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191568_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191568_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191571_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191571_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191577_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191577_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191582_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191582_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191585_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191585_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191592_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191592_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191595_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191595_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191599_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191599_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191601_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191601_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191603_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191603_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (34.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191606_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191606_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191607_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191607_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191608_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191610_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191610_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (40.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191614_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191614_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191615_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191615_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191617_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191617_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191620_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191620_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191621_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191621_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (25.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191624_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191624_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191626_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191626_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191628_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191628_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191630_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191630_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191631_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191631_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (29.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191632_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191632_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (29.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191634_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191634_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:26:29.80 +57:34:24.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191638_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191638_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191646_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191646_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191650_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191650_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191653_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191653_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191657_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191657_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191660_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191660_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191664_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191664_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191665_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191665_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191666_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191666_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191667_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191667_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191669_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191669_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191671_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191671_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191673_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191673_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191674_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191674_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191675_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191675_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191676_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191676_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191686_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191686_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191690_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191690_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191703_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191703_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191704_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191704_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191705_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191705_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191740_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191740_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (34.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191746_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191746_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191768_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191768_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191769_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191769_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191781_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191781_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191789_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191789_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191801_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191801_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191812_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191812_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191815_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191815_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191819_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191819_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191820_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191820_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191834_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191834_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191838_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191838_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:42:25.33 +56:49:50.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191847_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191847_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191853_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191853_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191856_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191856_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191867_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191867_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191870_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191870_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (30.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191872_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191872_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191892_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191892_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191895_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191895_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191896_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191896_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191907_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191907_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191911_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191911_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191917_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191917_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191925_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191925_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191929_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191929_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191930_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191930_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191931_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191931_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191935_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191935_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:54:23.05 +55:37:52.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191951_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191951_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191957_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191957_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191959_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191959_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191960_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 191960_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191964_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191964_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191982_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191982_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191983_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191983_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:53:17.68 +57:48:17.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191986_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191986_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191989_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191989_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191997_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191997_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 191999_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 191999_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:31:16.90 +57:14:10.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192001_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192001_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192003_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192003_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192004_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192004_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192014_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192014_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:49:03.08 +56:44:15.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192020_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192020_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192022_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192022_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192033_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192033_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192039_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192039_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192042_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192042_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192043_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192043_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192049_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192049_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192050_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192050_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192054_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192054_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192057_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192057_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192059_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192059_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192061_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192061_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192063_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192063_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192064_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192064_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192065_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192065_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192066_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192066_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:54:37.51 +54:37:15.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192069_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192069_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192074_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192074_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192076_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192076_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192083_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192083_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192084_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192084_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192094_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192094_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192099_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192099_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192101_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192101_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192106_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192106_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192107_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192107_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:09:24.02 +58:04:11.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192109_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192109_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192110_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192110_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192118_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192118_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192126_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192126_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192130_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192130_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192133_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192133_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192135_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192135_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192136_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192136_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192138_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192138_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192139_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192139_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:00:49.28 +56:12:30.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192147_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192147_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192148_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192148_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192150_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192150_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192151_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192151_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192152_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192152_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192153_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192153_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192156_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192156_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192164_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192164_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192165_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192165_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192174_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192174_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (38.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192181_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192181_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192184_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192184_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (33.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192190_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192190_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:07:12.08 +56:33:12.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192192_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192192_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192193_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192193_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192199_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192199_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192206_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192206_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192215_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192215_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (24.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192224_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192224_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192237_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192237_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192238_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192238_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192242_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192242_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:11:58.59 +57:59:10.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192247_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192247_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192249_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192249_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192251_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192251_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192255_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192255_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192258_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192258_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192267_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192267_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192270_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192270_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192273_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192273_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192274_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192274_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192276_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192276_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192278_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192278_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192288_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192288_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192292_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192292_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192293_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192293_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192301_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192301_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192312_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192312_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192321_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192321_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192324_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192324_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192327_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192327_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192337_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192337_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192340_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192340_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192341_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192341_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192346_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192346_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192362_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192362_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192371_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192371_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192373_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192373_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192377_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192377_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192378_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192378_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192380_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192380_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192387_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192387_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:00:38.91 +56:13:34.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192398_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192398_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192402_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192402_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192408_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192408_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192409_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192409_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192411_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192411_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192413_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192413_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192417_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192417_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192418_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192418_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192419_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192419_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192421_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192421_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192428_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192428_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192430_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192430_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192432_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192432_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192442_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192442_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192443_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192443_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192451_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192451_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192456_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192456_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192464_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (28.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192465_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192465_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192468_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192468_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192474_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192474_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192476_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192477_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192477_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192481_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192481_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192485_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192486_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192486_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192492_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192492_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192493_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192493_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192495_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192495_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (25.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192497_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192497_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192501_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192501_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192517_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192517_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192527_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192527_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192528_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192535_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192535_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192539_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192539_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192541_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192541_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (27.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192543_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192543_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (31.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192548_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192548_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (26.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192559_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192559_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192560_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192560_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192561_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192564_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192565_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192565_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192572_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192572_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192573_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192573_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192574_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192586_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192588_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192588_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192591_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192591_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (27.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192593_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192597_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192613_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192613_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192616_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192616_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192621_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192621_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192622_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192622_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192631_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192631_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192633_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192633_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (27.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192636_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192636_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192638_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192638_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192643_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192643_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192645_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192645_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192650_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192650_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192654_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192654_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192656_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192659_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192659_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192661_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192665_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192665_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192669_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192669_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192674_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192674_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192678_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192678_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192682_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192682_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192694_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192694_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192700_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192700_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192702_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192702_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192706_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192706_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192707_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192707_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192708_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192708_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192743_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192743_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192744_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192744_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192750_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192750_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192762_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192768_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192768_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192769_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192769_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192771_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192771_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192773_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192773_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192774_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192774_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192775_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192775_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192783_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192783_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192788_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192788_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192789_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192789_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192792_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192792_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:28:09.94 +53:34:42.0 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.23, MAG_FAINT_SEARCH_LIMIT=15.21)GAIADR2_OUTPUT=# 3.706 1992758383176329600 352.04017774798 +53.57905369788 14.9794 14.1514 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#3.706#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192797_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192797_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192799_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192799_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192805_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192805_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192808_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192808_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192811_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192811_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192814_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192814_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192817_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192817_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192819_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192819_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192822_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192822_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192824_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192824_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192835_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192835_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192836_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192836_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192840_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192840_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192844_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192844_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192850_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192850_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192858_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192858_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192859_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192859_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192874_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192874_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192876_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192876_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192881_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192881_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192887_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192887_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192888_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192888_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192891_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192891_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192894_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192894_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192902_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192902_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192903_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192903_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192905_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192905_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192906_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192906_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192907_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192907_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192908_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192908_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192910_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192910_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192913_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192913_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192915_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192915_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192927_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192927_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192928_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192928_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192932_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192932_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192934_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192934_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192939_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192939_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192944_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192944_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192945_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192945_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192946_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192946_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192950_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192950_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192952_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192952_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192953_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192953_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192954_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192954_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192955_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192955_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192956_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192956_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192962_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192962_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192969_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192969_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 192974_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192977_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192977_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192982_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192982_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192984_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192984_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192986_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192986_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192987_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192987_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192988_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192988_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192995_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192995_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192997_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 192997_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (28.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193000_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193001_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193001_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193002_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193003_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193003_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193006_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193006_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193007_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193007_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193009_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193009_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193015_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193023_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193023_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193025_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193025_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193026_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193026_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193031_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193031_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193035_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193035_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193036_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193036_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193039_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193039_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193040_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193040_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193046_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193046_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193048_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193048_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193052_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193052_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193053_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193053_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193057_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193057_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193059_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193059_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193060_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193064_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193064_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193070_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193070_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193071_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193071_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193072_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193072_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193073_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193073_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193076_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193076_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193081_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193081_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193085_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193091_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193091_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193094_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193094_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193101_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193101_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193102_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193102_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193108_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193108_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193112_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193112_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193113_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193115_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193123_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193123_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193128_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193128_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193129_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193129_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (34.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193132_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193132_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193133_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193133_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193134_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193136_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193136_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193138_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193138_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193143_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193143_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193145_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193145_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193147_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193147_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193151_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193151_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193152_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193152_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193155_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193155_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193160_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193160_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193164_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193164_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193167_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193167_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193169_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193169_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193174_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193174_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193176_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193176_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193177_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193177_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193185_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193185_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193186_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193186_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193188_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193188_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193189_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193189_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193194_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193195_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193195_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193197_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193197_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193201_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193201_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193202_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193202_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193203_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193203_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193206_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193206_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193209_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193209_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193212_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193212_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193217_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193217_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193225_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193225_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193229_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193229_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193232_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193232_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193234_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193234_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193238_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193238_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193243_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193244_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193244_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193245_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193245_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193253_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193253_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193255_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193255_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193259_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193259_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193260_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193262_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193262_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193263_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193265_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193265_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193277_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193279_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193279_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193284_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193284_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193286_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193286_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193290_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193290_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193291_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193291_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193297_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193297_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193299_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193299_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193302_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193302_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193304_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193304_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193305_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193307_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193309_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193309_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193313_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193313_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193314_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193314_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193318_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193318_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193320_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193320_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193329_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193329_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193330_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193330_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (30.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193335_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193335_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193336_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193336_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (46.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193345_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193345_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193350_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193350_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193351_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193351_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193353_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193353_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193355_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193355_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193358_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193358_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193359_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193359_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193361_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193361_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193365_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193365_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193368_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193368_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193370_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193370_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193377_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193377_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193379_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193379_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193384_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193384_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193387_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193387_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193389_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193389_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193391_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193391_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193392_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193392_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193399_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193399_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193404_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193404_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193405_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193405_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193408_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193408_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193410_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193410_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193422_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193422_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193423_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193423_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193434_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193434_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193454_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193454_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193459_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193459_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193466_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193466_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (12.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193468_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193468_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193469_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193469_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193470_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193472_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193472_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193473_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193473_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193477_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193477_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193482_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193482_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193487_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193487_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193507_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193507_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193513_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193513_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (16.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193520_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193520_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193525_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193525_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193553_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193553_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193581_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193581_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193584_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193584_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
Preparing report for the candidate 193635_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193658_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 193658_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 170697_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 170697_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:15:50.38 +57:32:38.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 140319_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 140319_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 00:19:58.75 +56:35:41.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 16337_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071
The candidate 16337_fd_Cas-04-Q2b1x1_2026-08-22_03-11-57_20.00sec_-0.00C_LIGHT_0071 did not pass the final checks
**** FOUND 23:21:42.63 +50:06:34.7 in the exclusion list exclusion_list_local.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 18s
make_report_in_HTML.sh TOTAL: 5368s
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:29:29.97 +49:37:15.3
23:21:42.74 +50:06:34.6
00:15:49.44 +57:32:33.9
23:34:54.46 +52:08:21.4
00:00:07.71 +51:20:32.3
23:32:44.09 +53:36:12.7
23:16:32.99 +54:49:21.6
00:25:19.84 +55:36:44.6
23:45:23.48 +50:07:59.0
23:32:19.52 +54:37:52.5
23:43:16.32 +53:14:40.0
23:16:46.59 +53:53:20.6
23:14:19.90 +56:28:34.6
23:53:10.37 +53:00:57.2
00:29:16.52 +53:48:56.1
23:43:41.74 +53:56:59.9
23:47:56.17 +50:14:16.4
23:22:35.41 +56:22:51.3
00:03:51.22 +51:49:58.3
23:48:15.24 +50:33:25.1
23:46:01.92 +54:36:44.3
23:23:09.30 +53:47:07.2
00:04:10.54 +53:29:36.3
23:28:37.49 +53:47:15.7
00:03:29.32 +53:34:29.9
23:46:07.83 +52:16:11.1
23:45:43.67 +53:35:11.7
23:32:06.07 +56:48:05.2
23:56:49.41 +50:59:53.3
23:32:03.08 +54:01:00.9
23:32:10.67 +52:27:49.1
23:14:31.07 +55:22:29.6
00:05:09.84 +52:39:12.8
23:39:36.44 +51:31:04.7
23:44:14.23 +53:16:50.7
00:08:08.63 +52:36:24.0
23:42:58.53 +50:44:45.4
00:22:06.58 +55:34:33.6
23:14:38.03 +57:34:53.5
23:57:13.90 +51:50:34.6
23:46:42.52 +51:44:29.6
23:14:21.80 +56:45:14.8
00:04:54.67 +50:30:18.5
23:27:40.60 +53:31:39.7
23:18:10.73 +56:56:38.8
23:51:14.86 +51:03:18.7
23:40:56.61 +56:21:53.9
23:29:49.37 +53:55:42.4
23:53:54.47 +53:23:43.6
23:32:52.68 +53:44:56.8
00:07:27.37 +50:53:53.2
23:19:44.60 +56:11:03.8
23:28:02.60 +55:38:41.1
00:10:19.91 +51:21:36.9
00:08:56.57 +52:27:44.6
23:50:41.11 +50:27:38.6
23:31:16.87 +51:15:22.6
00:05:42.71 +50:40:43.5
23:15:57.58 +56:35:13.7
23:59:31.01 +54:09:43.4
23:56:35.62 +53:30:25.1
00:04:43.27 +51:19:46.0
00:03:42.47 +51:10:37.1
00:13:35.89 +52:59:14.9
23:53:57.85 +51:34:47.9
23:27:49.24 +56:49:27.4
00:12:06.51 +52:49:27.0
23:27:07.82 +56:39:13.1
23:52:03.54 +52:58:06.0
00:03:15.67 +54:09:51.9
23:17:33.23 +56:09:21.6
00:07:29.71 +51:05:34.7
00:22:49.35 +53:31:12.0
23:23:21.75 +57:09:34.2
23:32:21.84 +56:20:21.3
00:08:06.07 +51:46:30.8
23:27:58.34 +57:50:03.6
23:16:49.00 +56:44:36.0
00:05:25.10 +52:54:41.6
00:03:44.07 +50:50:17.0
23:23:13.51 +56:57:50.2
23:58:50.68 +54:12:44.4
23:34:06.86 +54:09:21.7
00:09:16.55 +53:22:03.5
23:22:22.34 +51:21:56.1
23:40:56.86 +54:14:01.2
23:48:01.71 +49:59:48.2
23:17:49.65 +51:39:55.5
00:17:10.10 +50:18:51.7
23:27:41.87 +53:31:05.3
23:57:58.05 +50:00:24.8
00:00:45.62 +52:08:08.6
00:17:18.55 +50:49:48.3
23:30:46.14 +55:32:54.9
00:20:11.77 +56:00:27.7
23:23:07.72 +52:03:07.7
23:49:39.37 +51:05:46.5
00:15:17.11 +53:44:11.7
23:14:37.48 +56:41:29.6
00:24:08.78 +50:22:31.0
00:10:42.07 +53:58:57.0
23:26:51.29 +50:21:09.2
23:30:06.75 +51:01:43.6
23:28:15.12 +51:28:51.5
00:26:19.09 +55:49:26.5
23:41:14.04 +49:49:36.9
23:46:36.23 +53:17:01.6
23:17:23.23 +53:56:34.4
23:30:40.99 +51:38:18.3
23:43:08.28 +54:27:23.6
23:15:32.01 +55:29:11.5
23:52:37.64 +53:51:51.1
23:55:32.82 +51:24:52.5
23:50:29.86 +53:22:50.3
23:41:48.59 +51:06:39.4
23:15:41.40 +52:13:42.3
23:30:40.76 +54:19:12.6
00:13:02.17 +53:50:14.5
23:14:33.27 +57:05:59.1
23:45:02.68 +50:35:00.8
23:21:56.34 +51:25:10.8
23:58:27.60 +52:16:15.8
00:18:54.23 +51:50:01.8
23:45:25.99 +54:37:38.3
23:37:01.45 +49:45:09.2
23:22:50.94 +51:55:48.4
23:54:22.54 +51:29:59.1
00:09:04.15 +51:44:04.5
23:45:38.77 +51:01:03.5
23:18:52.43 +54:59:00.9
00:02:20.16 +54:17:37.2
00:02:46.70 +51:31:11.0
23:14:05.90 +55:29:19.6
23:27:03.80 +49:50:11.8
23:57:16.88 +54:23:51.7
23:17:33.82 +53:32:22.2
23:24:12.68 +57:04:12.5
00:25:26.06 +54:36:46.7
23:20:50.41 +55:51:37.3
00:30:57.48 +55:56:08.1
00:00:55.76 +53:32:19.1
00:20:05.82 +56:06:38.9
00:29:31.47 +54:18:13.1
23:19:03.26 +50:34:01.5
23:58:00.09 +54:14:36.2
23:50:08.86 +50:52:22.0
00:23:13.73 +56:00:14.0
00:01:04.96 +53:29:22.4
00:07:46.98 +54:40:43.2
23:29:51.74 +53:53:21.4
23:35:59.28 +53:20:20.0
00:20:15.23 +53:28:42.0
23:56:51.73 +51:51:53.0
23:41:28.09 +55:38:06.9
00:19:42.47 +50:07:36.4
23:25:30.43 +56:41:11.0
23:20:39.52 +54:42:07.1
00:25:38.27 +51:57:37.6
00:26:14.34 +55:46:35.7
23:12:57.41 +55:27:59.3
23:39:45.44 +51:01:24.4
23:17:59.42 +54:10:03.1
23:15:57.75 +54:49:29.8
23:45:29.79 +53:49:35.1
23:12:00.82 +56:27:27.7
23:27:45.51 +55:44:30.1
23:29:19.38 +54:25:59.6
23:53:43.24 +50:58:21.1
00:07:16.78 +51:00:16.6
00:23:20.28 +54:55:57.7
23:40:07.91 +51:56:11.6
23:23:22.94 +56:38:57.9
23:12:59.40 +56:18:49.8
23:20:01.55 +49:31:29.5
23:32:51.48 +54:47:21.1
23:25:40.67 +53:22:58.3
23:56:49.38 +50:03:02.2
00:12:47.58 +49:45:34.5
23:48:47.93 +49:47:28.5
23:17:14.26 +56:09:07.2
23:21:44.64 +54:27:13.8
23:43:57.31 +50:48:34.4
00:19:37.41 +50:48:31.5
23:27:29.73 +54:49:53.3
00:14:58.08 +54:13:21.4
23:13:13.59 +55:44:21.5
23:10:20.72 +57:28:17.8
00:06:00.89 +51:25:00.3
23:19:26.91 +55:24:29.3
00:22:28.01 +50:43:42.9
23:57:03.71 +52:12:03.8
23:53:56.97 +50:54:38.3
23:17:56.52 +56:24:55.7
23:27:37.67 +55:29:26.3
00:05:13.90 +51:50:43.2
23:26:59.99 +54:16:27.2
23:51:39.63 +50:16:05.2
23:48:52.01 +52:53:34.7
23:46:20.17 +51:20:04.0
23:18:16.06 +54:05:41.0
23:55:29.98 +51:30:59.5
23:19:19.85 +51:15:48.2
23:19:14.01 +52:17:58.3
23:23:12.95 +54:50:22.9
00:16:44.21 +54:00:39.1
23:19:22.81 +54:27:13.9
23:39:08.18 +51:12:37.7
00:18:16.38 +50:20:06.6
23:15:40.09 +52:17:13.7
23:55:59.04 +52:04:39.6
23:30:31.11 +54:53:22.7
23:42:14.12 +53:08:22.6
23:26:52.38 +52:05:31.3
23:33:46.45 +54:02:56.0
23:28:40.35 +52:21:28.3
23:40:25.77 +51:36:38.1
23:31:43.53 +51:03:14.4
23:45:24.33 +54:30:54.7
23:29:10.55 +56:37:30.6
23:56:57.38 +51:38:21.3
23:32:40.34 +56:50:03.2
23:54:22.33 +50:47:56.9
23:14:04.18 +56:21:23.9
23:34:13.82 +56:18:02.1
23:19:09.50 +56:44:16.5
00:14:12.21 +51:14:39.4
23:28:19.61 +53:31:54.8
23:20:08.25 +49:57:27.5
00:15:46.91 +51:08:54.9
23:37:55.93 +56:26:09.0
23:44:34.09 +55:20:20.6
23:15:00.47 +55:26:12.5
23:13:59.72 +56:34:34.3
23:23:20.81 +49:55:24.7
00:07:46.54 +53:00:37.9
00:16:43.41 +52:48:43.9
23:39:55.79 +51:47:05.1
23:16:14.45 +55:12:26.1
23:39:09.88 +50:57:48.1
23:44:02.40 +50:40:34.5
23:32:27.80 +55:10:17.5
23:25:22.78 +54:25:09.9
23:22:05.49 +50:07:46.9
23:32:02.31 +51:29:10.2
23:51:24.01 +53:36:25.8
00:14:15.94 +51:38:24.2
23:19:11.20 +49:46:33.1
23:26:08.38 +54:33:35.2
23:27:28.85 +54:50:53.7
00:20:07.24 +55:23:46.8
23:26:19.55 +55:50:52.0
23:33:42.98 +53:53:38.6
23:20:42.74 +52:39:38.0
23:22:56.11 +53:23:03.4
00:24:44.60 +53:17:26.5
23:55:41.04 +51:20:12.0
23:26:49.98 +50:38:35.5
23:19:24.36 +56:40:25.8
00:07:16.39 +54:17:21.5
00:14:54.54 +52:36:35.4
23:16:32.11 +53:16:20.1
00:15:46.58 +50:56:07.8
23:18:10.20 +54:54:18.8
23:22:53.15 +57:44:50.0
23:17:25.89 +53:38:26.6
23:12:46.68 +56:35:07.2
23:42:45.94 +54:49:23.6
23:57:57.23 +51:06:43.5
23:26:31.44 +55:59:44.4
23:51:07.43 +50:04:53.9
00:00:24.11 +51:47:09.1
00:12:51.74 +50:33:59.7
23:17:43.46 +50:37:44.9
00:24:22.38 +56:28:53.4
00:24:09.22 +50:06:56.0
00:06:12.63 +51:04:14.6
00:01:21.08 +53:54:25.4
23:23:13.93 +56:37:19.1
23:25:02.24 +54:21:52.4
23:46:36.30 +51:22:55.7
00:28:59.75 +53:42:07.5
00:09:54.87 +51:05:44.9
00:08:37.39 +53:17:20.7
00:18:21.43 +52:39:28.2
23:31:56.27 +55:25:40.4
23:41:51.34 +54:18:07.8
23:58:09.16 +50:28:52.3
23:48:20.07 +51:27:53.8
23:35:43.27 +49:56:04.9
23:41:30.99 +50:42:02.5
23:33:38.32 +57:50:17.3
23:38:09.74 +50:55:35.9
23:16:57.80 +55:08:21.1
00:10:38.72 +56:15:30.5
23:42:54.31 +54:20:57.0
23:45:41.18 +50:59:07.9
23:23:07.37 +53:42:19.1
23:30:13.07 +56:22:02.0
23:19:42.83 +50:14:40.0
23:19:36.79 +50:35:39.9
23:56:02.02 +51:54:41.2
00:16:21.13 +53:48:36.6
23:51:03.48 +53:48:39.5
23:43:22.46 +52:13:17.4
23:24:24.72 +53:44:34.2
23:24:40.83 +50:27:52.6
23:36:35.61 +53:39:17.1
23:22:12.61 +52:12:31.6
23:23:01.05 +53:16:37.0
23:17:45.15 +56:02:13.8
23:22:37.19 +56:31:56.8
23:42:17.05 +55:27:07.3
23:46:10.21 +55:17:36.1
23:36:05.03 +55:53:53.4
23:25:25.15 +57:39:33.7
########### 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:29:29.97 +49:37:15.3
23:21:42.74 +50:06:34.6
00:15:49.44 +57:32:33.9
23:34:54.46 +52:08:21.4
00:00:07.71 +51:20:32.3
23:32:44.09 +53:36:12.7
23:16:32.99 +54:49:21.6
00:25:19.84 +55:36:44.6
23:45:23.48 +50:07:59.0
23:32:19.52 +54:37:52.5
23:43:16.32 +53:14:40.0
23:16:46.59 +53:53:20.6
23:14:19.90 +56:28:34.6
23:53:10.37 +53:00:57.2
00:29:16.52 +53:48:56.1
23:43:41.74 +53:56:59.9
23:47:56.17 +50:14:16.4
23:22:35.41 +56:22:51.3
00:03:51.22 +51:49:58.3
23:48:15.24 +50:33:25.1
23:46:01.92 +54:36:44.3
23:23:09.30 +53:47:07.2
00:04:10.54 +53:29:36.3
23:28:37.49 +53:47:15.7
00:03:29.32 +53:34:29.9
23:46:07.83 +52:16:11.1
23:45:43.67 +53:35:11.7
23:32:06.07 +56:48:05.2
23:56:49.41 +50:59:53.3
23:32:03.08 +54:01:00.9
23:32:10.67 +52:27:49.1
23:14:31.07 +55:22:29.6
00:05:09.84 +52:39:12.8
23:39:36.44 +51:31:04.7
23:44:14.23 +53:16:50.7
00:08:08.63 +52:36:24.0
23:42:58.53 +50:44:45.4
00:22:06.58 +55:34:33.6
23:14:38.03 +57:34:53.5
23:57:13.90 +51:50:34.6
23:46:42.52 +51:44:29.6
23:14:21.80 +56:45:14.8
00:04:54.67 +50:30:18.5
23:27:40.60 +53:31:39.7
23:18:10.73 +56:56:38.8
23:51:14.86 +51:03:18.7
23:40:56.61 +56:21:53.9
23:29:49.37 +53:55:42.4
23:53:54.47 +53:23:43.6
23:32:52.68 +53:44:56.8
00:07:27.37 +50:53:53.2
23:19:44.60 +56:11:03.8
23:28:02.60 +55:38:41.1
00:10:19.91 +51:21:36.9
00:08:56.57 +52:27:44.6
23:50:41.11 +50:27:38.6
23:31:16.87 +51:15:22.6
00:05:42.71 +50:40:43.5
23:15:57.58 +56:35:13.7
23:59:31.01 +54:09:43.4
23:56:35.62 +53:30:25.1
00:04:43.27 +51:19:46.0
00:03:42.47 +51:10:37.1
00:13:35.89 +52:59:14.9
23:53:57.85 +51:34:47.9
23:27:49.24 +56:49:27.4
00:12:06.51 +52:49:27.0
23:27:07.82 +56:39:13.1
23:52:03.54 +52:58:06.0
00:03:15.67 +54:09:51.9
23:17:33.23 +56:09:21.6
00:07:29.71 +51:05:34.7
00:22:49.35 +53:31:12.0
23:23:21.75 +57:09:34.2
23:32:21.84 +56:20:21.3
00:08:06.07 +51:46:30.8
23:27:58.34 +57:50:03.6
23:16:49.00 +56:44:36.0
00:05:25.10 +52:54:41.6
00:03:44.07 +50:50:17.0
23:23:13.51 +56:57:50.2
23:58:50.68 +54:12:44.4
23:34:06.86 +54:09:21.7
00:09:16.55 +53:22:03.5
23:22:22.34 +51:21:56.1
23:40:56.86 +54:14:01.2
23:48:01.71 +49:59:48.2
23:17:49.65 +51:39:55.5
00:17:10.10 +50:18:51.7
23:27:41.87 +53:31:05.3
23:57:58.05 +50:00:24.8
00:00:45.62 +52:08:08.6
00:17:18.55 +50:49:48.3
23:30:46.14 +55:32:54.9
00:20:11.77 +56:00:27.7
23:23:07.72 +52:03:07.7
23:49:39.37 +51:05:46.5
00:15:17.11 +53:44:11.7
23:14:37.48 +56:41:29.6
00:24:08.78 +50:22:31.0
00:10:42.07 +53:58:57.0
23:26:51.29 +50:21:09.2
23:30:06.75 +51:01:43.6
23:28:15.12 +51:28:51.5
00:26:19.09 +55:49:26.5
23:41:14.04 +49:49:36.9
23:46:36.23 +53:17:01.6
23:17:23.23 +53:56:34.4
23:30:40.99 +51:38:18.3
23:43:08.28 +54:27:23.6
23:15:32.01 +55:29:11.5
23:52:37.64 +53:51:51.1
23:55:32.82 +51:24:52.5
23:50:29.86 +53:22:50.3
23:41:48.59 +51:06:39.4
23:15:41.40 +52:13:42.3
23:30:40.76 +54:19:12.6
00:13:02.17 +53:50:14.5
23:14:33.27 +57:05:59.1
23:45:02.68 +50:35:00.8
23:21:56.34 +51:25:10.8
23:58:27.60 +52:16:15.8
00:18:54.23 +51:50:01.8
23:45:25.99 +54:37:38.3
23:37:01.45 +49:45:09.2
23:22:50.94 +51:55:48.4
23:54:22.54 +51:29:59.1
00:09:04.15 +51:44:04.5
23:45:38.77 +51:01:03.5
23:18:52.43 +54:59:00.9
00:02:20.16 +54:17:37.2
00:02:46.70 +51:31:11.0
23:14:05.90 +55:29:19.6
23:27:03.80 +49:50:11.8
23:57:16.88 +54:23:51.7
23:17:33.82 +53:32:22.2
23:24:12.68 +57:04:12.5
00:25:26.06 +54:36:46.7
23:20:50.41 +55:51:37.3
00:30:57.48 +55:56:08.1
00:00:55.76 +53:32:19.1
00:20:05.82 +56:06:38.9
00:29:31.47 +54:18:13.1
23:19:03.26 +50:34:01.5
23:58:00.09 +54:14:36.2
23:50:08.86 +50:52:22.0
00:23:13.73 +56:00:14.0
00:01:04.96 +53:29:22.4
00:07:46.98 +54:40:43.2
23:29:51.74 +53:53:21.4
23:35:59.28 +53:20:20.0
00:20:15.23 +53:28:42.0
23:56:51.73 +51:51:53.0
23:41:28.09 +55:38:06.9
00:19:42.47 +50:07:36.4
23:25:30.43 +56:41:11.0
23:20:39.52 +54:42:07.1
00:25:38.27 +51:57:37.6
00:26:14.34 +55:46:35.7
23:12:57.41 +55:27:59.3
23:39:45.44 +51:01:24.4
23:17:59.42 +54:10:03.1
23:15:57.75 +54:49:29.8
23:45:29.79 +53:49:35.1
23:12:00.82 +56:27:27.7
23:27:45.51 +55:44:30.1
23:29:19.38 +54:25:59.6
23:53:43.24 +50:58:21.1
00:07:16.78 +51:00:16.6
00:23:20.28 +54:55:57.7
23:40:07.91 +51:56:11.6
23:23:22.94 +56:38:57.9
23:12:59.40 +56:18:49.8
23:20:01.55 +49:31:29.5
23:32:51.48 +54:47:21.1
23:25:40.67 +53:22:58.3
23:56:49.38 +50:03:02.2
00:12:47.58 +49:45:34.5
23:48:47.93 +49:47:28.5
23:17:14.26 +56:09:07.2
23:21:44.64 +54:27:13.8
23:43:57.31 +50:48:34.4
00:19:37.41 +50:48:31.5
23:27:29.73 +54:49:53.3
00:14:58.08 +54:13:21.4
23:13:13.59 +55:44:21.5
23:10:20.72 +57:28:17.8
00:06:00.89 +51:25:00.3
23:19:26.91 +55:24:29.3
00:22:28.01 +50:43:42.9
23:57:03.71 +52:12:03.8
23:53:56.97 +50:54:38.3
23:17:56.52 +56:24:55.7
23:27:37.67 +55:29:26.3
00:05:13.90 +51:50:43.2
23:26:59.99 +54:16:27.2
23:51:39.63 +50:16:05.2
23:48:52.01 +52:53:34.7
23:46:20.17 +51:20:04.0
23:18:16.06 +54:05:41.0
23:55:29.98 +51:30:59.5
23:19:19.85 +51:15:48.2
23:19:14.01 +52:17:58.3
23:23:12.95 +54:50:22.9
00:16:44.21 +54:00:39.1
23:19:22.81 +54:27:13.9
23:39:08.18 +51:12:37.7
00:18:16.38 +50:20:06.6
23:15:40.09 +52:17:13.7
23:55:59.04 +52:04:39.6
23:30:31.11 +54:53:22.7
23:42:14.12 +53:08:22.6
23:26:52.38 +52:05:31.3
23:33:46.45 +54:02:56.0
23:28:40.35 +52:21:28.3
23:40:25.77 +51:36:38.1
23:31:43.53 +51:03:14.4
23:45:24.33 +54:30:54.7
23:29:10.55 +56:37:30.6
23:56:57.38 +51:38:21.3
23:32:40.34 +56:50:03.2
23:54:22.33 +50:47:56.9
23:14:04.18 +56:21:23.9
23:34:13.82 +56:18:02.1
23:19:09.50 +56:44:16.5
00:14:12.21 +51:14:39.4
23:28:19.61 +53:31:54.8
23:20:08.25 +49:57:27.5
00:15:46.91 +51:08:54.9
23:37:55.93 +56:26:09.0
23:44:34.09 +55:20:20.6
23:15:00.47 +55:26:12.5
23:13:59.72 +56:34:34.3
23:23:20.81 +49:55:24.7
00:07:46.54 +53:00:37.9
00:16:43.41 +52:48:43.9
23:39:55.79 +51:47:05.1
23:16:14.45 +55:12:26.1
23:39:09.88 +50:57:48.1
23:44:02.40 +50:40:34.5
23:32:27.80 +55:10:17.5
23:25:22.78 +54:25:09.9
23:22:05.49 +50:07:46.9
23:32:02.31 +51:29:10.2
23:51:24.01 +53:36:25.8
00:14:15.94 +51:38:24.2
23:19:11.20 +49:46:33.1
23:26:08.38 +54:33:35.2
23:27:28.85 +54:50:53.7
00:20:07.24 +55:23:46.8
23:26:19.55 +55:50:52.0
23:33:42.98 +53:53:38.6
23:20:42.74 +52:39:38.0
23:22:56.11 +53:23:03.4
00:24:44.60 +53:17:26.5
23:55:41.04 +51:20:12.0
23:26:49.98 +50:38:35.5
23:19:24.36 +56:40:25.8
00:07:16.39 +54:17:21.5
00:14:54.54 +52:36:35.4
23:16:32.11 +53:16:20.1
00:15:46.58 +50:56:07.8
23:18:10.20 +54:54:18.8
23:22:53.15 +57:44:50.0
23:17:25.89 +53:38:26.6
23:12:46.68 +56:35:07.2
23:42:45.94 +54:49:23.6
23:57:57.23 +51:06:43.5
23:26:31.44 +55:59:44.4
23:51:07.43 +50:04:53.9
00:00:24.11 +51:47:09.1
00:12:51.74 +50:33:59.7
23:17:43.46 +50:37:44.9
00:24:22.38 +56:28:53.4
00:24:09.22 +50:06:56.0
00:06:12.63 +51:04:14.6
00:01:21.08 +53:54:25.4
23:23:13.93 +56:37:19.1
23:25:02.24 +54:21:52.4
23:46:36.30 +51:22:55.7
00:28:59.75 +53:42:07.5
00:09:54.87 +51:05:44.9
00:08:37.39 +53:17:20.7
00:18:21.43 +52:39:28.2
23:31:56.27 +55:25:40.4
23:41:51.34 +54:18:07.8
23:58:09.16 +50:28:52.3
23:48:20.07 +51:27:53.8
23:35:43.27 +49:56:04.9
23:41:30.99 +50:42:02.5
23:33:38.32 +57:50:17.3
23:38:09.74 +50:55:35.9
23:16:57.80 +55:08:21.1
00:10:38.72 +56:15:30.5
23:42:54.31 +54:20:57.0
23:45:41.18 +50:59:07.9
23:23:07.37 +53:42:19.1
23:30:13.07 +56:22:02.0
23:19:42.83 +50:14:40.0
23:19:36.79 +50:35:39.9
23:56:02.02 +51:54:41.2
00:16:21.13 +53:48:36.6
23:51:03.48 +53:48:39.5
23:43:22.46 +52:13:17.4
23:24:24.72 +53:44:34.2
23:24:40.83 +50:27:52.6
23:36:35.61 +53:39:17.1
23:22:12.61 +52:12:31.6
23:23:01.05 +53:16:37.0
23:17:45.15 +56:02:13.8
23:22:37.19 +56:31:56.8
23:42:17.05 +55:27:07.3
23:46:10.21 +55:17:36.1
23:36:05.03 +55:53:53.4
23:25:25.15 +57:39:33.7
###################################################################################
23:29:29.97 +49:37:15.3 -- not an asteroid (will add it to exclusion list)
23:21:42.74 +50:06:34.6 -- not an asteroid (will add it to exclusion list)
00:15:49.44 +57:32:33.9 -- not an asteroid (will add it to exclusion list)
23:34:54.46 +52:08:21.4 -- not an asteroid (will add it to exclusion list)
00:00:07.71 +51:20:32.3 -- not an asteroid (will add it to exclusion list)
23:32:44.09 +53:36:12.7 -- not an asteroid (will add it to exclusion list)
23:16:32.99 +54:49:21.6 -- not an asteroid (will add it to exclusion list)
00:25:19.84 +55:36:44.6 -- not an asteroid (will add it to exclusion list)
23:45:23.48 +50:07:59.0 -- not an asteroid (will add it to exclusion list)
23:32:19.52 +54:37:52.5 -- not an asteroid (will add it to exclusion list)
23:43:16.32 +53:14:40.0 -- not an asteroid (will add it to exclusion list)
23:16:46.59 +53:53:20.6 -- not an asteroid (will add it to exclusion list)
23:14:19.90 +56:28:34.6 -- not an asteroid (will add it to exclusion list)
23:53:10.37 +53:00:57.2 -- not an asteroid (will add it to exclusion list)
00:29:16.52 +53:48:56.1 -- not an asteroid (will add it to exclusion list)
23:43:41.74 +53:56:59.9 -- not an asteroid (will add it to exclusion list)
23:47:56.17 +50:14:16.4 -- not an asteroid (will add it to exclusion list)
23:22:35.41 +56:22:51.3 -- not an asteroid (will add it to exclusion list)
00:03:51.22 +51:49:58.3 -- not an asteroid (will add it to exclusion list)
23:48:15.24 +50:33:25.1 -- not an asteroid (will add it to exclusion list)
23:46:01.92 +54:36:44.3 -- not an asteroid (will add it to exclusion list)
23:23:09.30 +53:47:07.2 -- not an asteroid (will add it to exclusion list)
00:04:10.54 +53:29:36.3 -- not an asteroid (will add it to exclusion list)
23:28:37.49 +53:47:15.7 -- not an asteroid (will add it to exclusion list)
00:03:29.32 +53:34:29.9 -- not an asteroid (will add it to exclusion list)
23:46:07.83 +52:16:11.1 -- not an asteroid (will add it to exclusion list)
23:45:43.67 +53:35:11.7 -- not an asteroid (will add it to exclusion list)
23:32:06.07 +56:48:05.2 -- not an asteroid (will add it to exclusion list)
23:56:49.41 +50:59:53.3 -- not an asteroid (will add it to exclusion list)
23:32:03.08 +54:01:00.9 -- not an asteroid (will add it to exclusion list)
23:32:10.67 +52:27:49.1 -- not an asteroid (will add it to exclusion list)
23:14:31.07 +55:22:29.6 -- not an asteroid (will add it to exclusion list)
00:05:09.84 +52:39:12.8 -- not an asteroid (will add it to exclusion list)
23:39:36.44 +51:31:04.7 -- not an asteroid (will add it to exclusion list)
23:44:14.23 +53:16:50.7 -- not an asteroid (will add it to exclusion list)
00:08:08.63 +52:36:24.0 -- not an asteroid (will add it to exclusion list)
23:42:58.53 +50:44:45.4 -- not an asteroid (will add it to exclusion list)
00:22:06.58 +55:34:33.6 -- not an asteroid (will add it to exclusion list)
23:14:38.03 +57:34:53.5 -- not an asteroid (will add it to exclusion list)
23:57:13.90 +51:50:34.6 -- not an asteroid (will add it to exclusion list)
23:46:42.52 +51:44:29.6 -- not an asteroid (will add it to exclusion list)
23:14:21.80 +56:45:14.8 -- not an asteroid (will add it to exclusion list)
00:04:54.67 +50:30:18.5 -- not an asteroid (will add it to exclusion list)
23:27:40.60 +53:31:39.7 -- not an asteroid (will add it to exclusion list)
23:18:10.73 +56:56:38.8 -- not an asteroid (will add it to exclusion list)
23:51:14.86 +51:03:18.7 -- not an asteroid (will add it to exclusion list)
23:40:56.61 +56:21:53.9 -- not an asteroid (will add it to exclusion list)
23:29:49.37 +53:55:42.4 -- not an asteroid (will add it to exclusion list)
23:53:54.47 +53:23:43.6 -- not an asteroid (will add it to exclusion list)
23:32:52.68 +53:44:56.8 -- not an asteroid (will add it to exclusion list)
00:07:27.37 +50:53:53.2 -- not an asteroid (will add it to exclusion list)
23:19:44.60 +56:11:03.8 -- not an asteroid (will add it to exclusion list)
23:28:02.60 +55:38:41.1 -- not an asteroid (will add it to exclusion list)
00:10:19.91 +51:21:36.9 -- not an asteroid (will add it to exclusion list)
00:08:56.57 +52:27:44.6 -- not an asteroid (will add it to exclusion list)
23:50:41.11 +50:27:38.6 -- not an asteroid (will add it to exclusion list)
23:31:16.87 +51:15:22.6 -- not an asteroid (will add it to exclusion list)
00:05:42.71 +50:40:43.5 -- not an asteroid (will add it to exclusion list)
23:15:57.58 +56:35:13.7 -- not an asteroid (will add it to exclusion list)
23:59:31.01 +54:09:43.4 -- not an asteroid (will add it to exclusion list)
23:56:35.62 +53:30:25.1 -- not an asteroid (will add it to exclusion list)
00:04:43.27 +51:19:46.0 -- not an asteroid (will add it to exclusion list)
00:03:42.47 +51:10:37.1 -- not an asteroid (will add it to exclusion list)
00:13:35.89 +52:59:14.9 -- not an asteroid (will add it to exclusion list)
23:53:57.85 +51:34:47.9 -- not an asteroid (will add it to exclusion list)
23:27:49.24 +56:49:27.4 -- not an asteroid (will add it to exclusion list)
00:12:06.51 +52:49:27.0 -- not an asteroid (will add it to exclusion list)
23:27:07.82 +56:39:13.1 -- not an asteroid (will add it to exclusion list)
23:52:03.54 +52:58:06.0 -- not an asteroid (will add it to exclusion list)
00:03:15.67 +54:09:51.9 -- not an asteroid (will add it to exclusion list)
23:17:33.23 +56:09:21.6 -- not an asteroid (will add it to exclusion list)
00:07:29.71 +51:05:34.7 -- not an asteroid (will add it to exclusion list)
00:22:49.35 +53:31:12.0 -- not an asteroid (will add it to exclusion list)
23:23:21.75 +57:09:34.2 -- not an asteroid (will add it to exclusion list)
23:32:21.84 +56:20:21.3 -- not an asteroid (will add it to exclusion list)
00:08:06.07 +51:46:30.8 -- not an asteroid (will add it to exclusion list)
23:27:58.34 +57:50:03.6 -- not an asteroid (will add it to exclusion list)
23:16:49.00 +56:44:36.0 -- not an asteroid (will add it to exclusion list)
00:05:25.10 +52:54:41.6 -- not an asteroid (will add it to exclusion list)
00:03:44.07 +50:50:17.0 -- not an asteroid (will add it to exclusion list)
23:23:13.51 +56:57:50.2 -- not an asteroid (will add it to exclusion list)
23:58:50.68 +54:12:44.4 -- not an asteroid (will add it to exclusion list)
23:34:06.86 +54:09:21.7 -- not an asteroid (will add it to exclusion list)
00:09:16.55 +53:22:03.5 -- not an asteroid (will add it to exclusion list)
23:22:22.34 +51:21:56.1 -- not an asteroid (will add it to exclusion list)
23:40:56.86 +54:14:01.2 -- not an asteroid (will add it to exclusion list)
23:48:01.71 +49:59:48.2 -- not an asteroid (will add it to exclusion list)
23:17:49.65 +51:39:55.5 -- not an asteroid (will add it to exclusion list)
00:17:10.10 +50:18:51.7 -- not an asteroid (will add it to exclusion list)
23:27:41.87 +53:31:05.3 -- not an asteroid (will add it to exclusion list)
23:57:58.05 +50:00:24.8 -- not an asteroid (will add it to exclusion list)
00:00:45.62 +52:08:08.6 -- not an asteroid (will add it to exclusion list)
00:17:18.55 +50:49:48.3 -- not an asteroid (will add it to exclusion list)
23:30:46.14 +55:32:54.9 -- not an asteroid (will add it to exclusion list)
00:20:11.77 +56:00:27.7 -- not an asteroid (will add it to exclusion list)
23:23:07.72 +52:03:07.7 -- not an asteroid (will add it to exclusion list)
23:49:39.37 +51:05:46.5 -- not an asteroid (will add it to exclusion list)
00:15:17.11 +53:44:11.7 -- not an asteroid (will add it to exclusion list)
23:14:37.48 +56:41:29.6 -- not an asteroid (will add it to exclusion list)
00:24:08.78 +50:22:31.0 -- not an asteroid (will add it to exclusion list)
00:10:42.07 +53:58:57.0 -- not an asteroid (will add it to exclusion list)
23:26:51.29 +50:21:09.2 -- not an asteroid (will add it to exclusion list)
23:30:06.75 +51:01:43.6 -- not an asteroid (will add it to exclusion list)
23:28:15.12 +51:28:51.5 -- not an asteroid (will add it to exclusion list)
00:26:19.09 +55:49:26.5 -- not an asteroid (will add it to exclusion list)
23:41:14.04 +49:49:36.9 -- not an asteroid (will add it to exclusion list)
23:46:36.23 +53:17:01.6 -- not an asteroid (will add it to exclusion list)
23:17:23.23 +53:56:34.4 -- not an asteroid (will add it to exclusion list)
23:30:40.99 +51:38:18.3 -- not an asteroid (will add it to exclusion list)
23:43:08.28 +54:27:23.6 -- not an asteroid (will add it to exclusion list)
23:15:32.01 +55:29:11.5 -- not an asteroid (will add it to exclusion list)
23:52:37.64 +53:51:51.1 -- not an asteroid (will add it to exclusion list)
23:55:32.82 +51:24:52.5 -- not an asteroid (will add it to exclusion list)
23:50:29.86 +53:22:50.3 -- not an asteroid (will add it to exclusion list)
23:41:48.59 +51:06:39.4 -- not an asteroid (will add it to exclusion list)
23:15:41.40 +52:13:42.3 -- not an asteroid (will add it to exclusion list)
23:30:40.76 +54:19:12.6 -- not an asteroid (will add it to exclusion list)
00:13:02.17 +53:50:14.5 -- not an asteroid (will add it to exclusion list)
23:14:33.27 +57:05:59.1 -- not an asteroid (will add it to exclusion list)
23:45:02.68 +50:35:00.8 -- not an asteroid (will add it to exclusion list)
23:21:56.34 +51:25:10.8 -- not an asteroid (will add it to exclusion list)
23:58:27.60 +52:16:15.8 -- not an asteroid (will add it to exclusion list)
00:18:54.23 +51:50:01.8 -- not an asteroid (will add it to exclusion list)
23:45:25.99 +54:37:38.3 -- not an asteroid (will add it to exclusion list)
23:37:01.45 +49:45:09.2 -- not an asteroid (will add it to exclusion list)
23:22:50.94 +51:55:48.4 -- not an asteroid (will add it to exclusion list)
23:54:22.54 +51:29:59.1 -- not an asteroid (will add it to exclusion list)
00:09:04.15 +51:44:04.5 -- not an asteroid (will add it to exclusion list)
23:45:38.77 +51:01:03.5 -- not an asteroid (will add it to exclusion list)
23:18:52.43 +54:59:00.9 -- not an asteroid (will add it to exclusion list)
00:02:20.16 +54:17:37.2 -- not an asteroid (will add it to exclusion list)
00:02:46.70 +51:31:11.0 -- not an asteroid (will add it to exclusion list)
23:14:05.90 +55:29:19.6 -- not an asteroid (will add it to exclusion list)
23:27:03.80 +49:50:11.8 -- not an asteroid (will add it to exclusion list)
23:57:16.88 +54:23:51.7 -- not an asteroid (will add it to exclusion list)
23:17:33.82 +53:32:22.2 -- not an asteroid (will add it to exclusion list)
23:24:12.68 +57:04:12.5 -- not an asteroid (will add it to exclusion list)
00:25:26.06 +54:36:46.7 -- not an asteroid (will add it to exclusion list)
23:20:50.41 +55:51:37.3 -- not an asteroid (will add it to exclusion list)
00:30:57.48 +55:56:08.1 -- not an asteroid (will add it to exclusion list)
00:00:55.76 +53:32:19.1 -- not an asteroid (will add it to exclusion list)
00:20:05.82 +56:06:38.9 -- not an asteroid (will add it to exclusion list)
00:29:31.47 +54:18:13.1 -- not an asteroid (will add it to exclusion list)
23:19:03.26 +50:34:01.5 -- not an asteroid (will add it to exclusion list)
23:58:00.09 +54:14:36.2 -- not an asteroid (will add it to exclusion list)
23:50:08.86 +50:52:22.0 -- not an asteroid (will add it to exclusion list)
00:23:13.73 +56:00:14.0 -- not an asteroid (will add it to exclusion list)
00:01:04.96 +53:29:22.4 -- not an asteroid (will add it to exclusion list)
00:07:46.98 +54:40:43.2 -- not an asteroid (will add it to exclusion list)
23:29:51.74 +53:53:21.4 -- not an asteroid (will add it to exclusion list)
23:35:59.28 +53:20:20.0 -- not an asteroid (will add it to exclusion list)
00:20:15.23 +53:28:42.0 -- not an asteroid (will add it to exclusion list)
23:56:51.73 +51:51:53.0 -- not an asteroid (will add it to exclusion list)
23:41:28.09 +55:38:06.9 -- not an asteroid (will add it to exclusion list)
00:19:42.47 +50:07:36.4 -- not an asteroid (will add it to exclusion list)
23:25:30.43 +56:41:11.0 -- not an asteroid (will add it to exclusion list)
23:20:39.52 +54:42:07.1 -- not an asteroid (will add it to exclusion list)
00:25:38.27 +51:57:37.6 -- not an asteroid (will add it to exclusion list)
00:26:14.34 +55:46:35.7 -- not an asteroid (will add it to exclusion list)
23:12:57.41 +55:27:59.3 -- not an asteroid (will add it to exclusion list)
23:39:45.44 +51:01:24.4 -- not an asteroid (will add it to exclusion list)
23:17:59.42 +54:10:03.1 -- not an asteroid (will add it to exclusion list)
23:15:57.75 +54:49:29.8 -- not an asteroid (will add it to exclusion list)
23:45:29.79 +53:49:35.1 -- not an asteroid (will add it to exclusion list)
23:12:00.82 +56:27:27.7 -- not an asteroid (will add it to exclusion list)
23:27:45.51 +55:44:30.1 -- not an asteroid (will add it to exclusion list)
23:29:19.38 +54:25:59.6 -- not an asteroid (will add it to exclusion list)
23:53:43.24 +50:58:21.1 -- not an asteroid (will add it to exclusion list)
00:07:16.78 +51:00:16.6 -- not an asteroid (will add it to exclusion list)
00:23:20.28 +54:55:57.7 -- not an asteroid (will add it to exclusion list)
23:40:07.91 +51:56:11.6 -- not an asteroid (will add it to exclusion list)
23:23:22.94 +56:38:57.9 -- not an asteroid (will add it to exclusion list)
23:12:59.40 +56:18:49.8 -- not an asteroid (will add it to exclusion list)
23:20:01.55 +49:31:29.5 -- not an asteroid (will add it to exclusion list)
23:32:51.48 +54:47:21.1 -- not an asteroid (will add it to exclusion list)
23:25:40.67 +53:22:58.3 -- not an asteroid (will add it to exclusion list)
23:56:49.38 +50:03:02.2 -- not an asteroid (will add it to exclusion list)
00:12:47.58 +49:45:34.5 -- not an asteroid (will add it to exclusion list)
23:48:47.93 +49:47:28.5 -- not an asteroid (will add it to exclusion list)
23:17:14.26 +56:09:07.2 -- not an asteroid (will add it to exclusion list)
23:21:44.64 +54:27:13.8 -- not an asteroid (will add it to exclusion list)
23:43:57.31 +50:48:34.4 -- not an asteroid (will add it to exclusion list)
00:19:37.41 +50:48:31.5 -- not an asteroid (will add it to exclusion list)
23:27:29.73 +54:49:53.3 -- not an asteroid (will add it to exclusion list)
00:14:58.08 +54:13:21.4 -- not an asteroid (will add it to exclusion list)
23:13:13.59 +55:44:21.5 -- not an asteroid (will add it to exclusion list)
23:10:20.72 +57:28:17.8 -- not an asteroid (will add it to exclusion list)
00:06:00.89 +51:25:00.3 -- not an asteroid (will add it to exclusion list)
23:19:26.91 +55:24:29.3 -- not an asteroid (will add it to exclusion list)
00:22:28.01 +50:43:42.9 -- not an asteroid (will add it to exclusion list)
23:57:03.71 +52:12:03.8 -- not an asteroid (will add it to exclusion list)
23:53:56.97 +50:54:38.3 -- not an asteroid (will add it to exclusion list)
23:17:56.52 +56:24:55.7 -- not an asteroid (will add it to exclusion list)
23:27:37.67 +55:29:26.3 -- not an asteroid (will add it to exclusion list)
00:05:13.90 +51:50:43.2 -- not an asteroid (will add it to exclusion list)
23:26:59.99 +54:16:27.2 -- not an asteroid (will add it to exclusion list)
23:51:39.63 +50:16:05.2 -- not an asteroid (will add it to exclusion list)
23:48:52.01 +52:53:34.7 -- not an asteroid (will add it to exclusion list)
23:46:20.17 +51:20:04.0 -- not an asteroid (will add it to exclusion list)
23:18:16.06 +54:05:41.0 -- not an asteroid (will add it to exclusion list)
23:55:29.98 +51:30:59.5 -- not an asteroid (will add it to exclusion list)
23:19:19.85 +51:15:48.2 -- not an asteroid (will add it to exclusion list)
23:19:14.01 +52:17:58.3 -- not an asteroid (will add it to exclusion list)
23:23:12.95 +54:50:22.9 -- not an asteroid (will add it to exclusion list)
00:16:44.21 +54:00:39.1 -- not an asteroid (will add it to exclusion list)
23:19:22.81 +54:27:13.9 -- not an asteroid (will add it to exclusion list)
23:39:08.18 +51:12:37.7 -- not an asteroid (will add it to exclusion list)
00:18:16.38 +50:20:06.6 -- not an asteroid (will add it to exclusion list)
23:15:40.09 +52:17:13.7 -- not an asteroid (will add it to exclusion list)
23:55:59.04 +52:04:39.6 -- not an asteroid (will add it to exclusion list)
23:30:31.11 +54:53:22.7 -- not an asteroid (will add it to exclusion list)
23:42:14.12 +53:08:22.6 -- not an asteroid (will add it to exclusion list)
23:26:52.38 +52:05:31.3 -- not an asteroid (will add it to exclusion list)
23:33:46.45 +54:02:56.0 -- not an asteroid (will add it to exclusion list)
23:28:40.35 +52:21:28.3 -- not an asteroid (will add it to exclusion list)
23:40:25.77 +51:36:38.1 -- not an asteroid (will add it to exclusion list)
23:31:43.53 +51:03:14.4 -- not an asteroid (will add it to exclusion list)
23:45:24.33 +54:30:54.7 -- not an asteroid (will add it to exclusion list)
23:29:10.55 +56:37:30.6 -- not an asteroid (will add it to exclusion list)
23:56:57.38 +51:38:21.3 -- not an asteroid (will add it to exclusion list)
23:32:40.34 +56:50:03.2 -- not an asteroid (will add it to exclusion list)
23:54:22.33 +50:47:56.9 -- not an asteroid (will add it to exclusion list)
23:14:04.18 +56:21:23.9 -- not an asteroid (will add it to exclusion list)
23:34:13.82 +56:18:02.1 -- not an asteroid (will add it to exclusion list)
23:19:09.50 +56:44:16.5 -- not an asteroid (will add it to exclusion list)
00:14:12.21 +51:14:39.4 -- not an asteroid (will add it to exclusion list)
23:28:19.61 +53:31:54.8 -- not an asteroid (will add it to exclusion list)
23:20:08.25 +49:57:27.5 -- not an asteroid (will add it to exclusion list)
00:15:46.91 +51:08:54.9 -- not an asteroid (will add it to exclusion list)
23:37:55.93 +56:26:09.0 -- not an asteroid (will add it to exclusion list)
23:44:34.09 +55:20:20.6 -- not an asteroid (will add it to exclusion list)
23:15:00.47 +55:26:12.5 -- not an asteroid (will add it to exclusion list)
23:13:59.72 +56:34:34.3 -- not an asteroid (will add it to exclusion list)
23:23:20.81 +49:55:24.7 -- not an asteroid (will add it to exclusion list)
00:07:46.54 +53:00:37.9 -- not an asteroid (will add it to exclusion list)
00:16:43.41 +52:48:43.9 -- not an asteroid (will add it to exclusion list)
23:39:55.79 +51:47:05.1 -- not an asteroid (will add it to exclusion list)
23:16:14.45 +55:12:26.1 -- not an asteroid (will add it to exclusion list)
23:39:09.88 +50:57:48.1 -- not an asteroid (will add it to exclusion list)
23:44:02.40 +50:40:34.5 -- not an asteroid (will add it to exclusion list)
23:32:27.80 +55:10:17.5 -- not an asteroid (will add it to exclusion list)
23:25:22.78 +54:25:09.9 -- not an asteroid (will add it to exclusion list)
23:22:05.49 +50:07:46.9 -- not an asteroid (will add it to exclusion list)
23:32:02.31 +51:29:10.2 -- not an asteroid (will add it to exclusion list)
23:51:24.01 +53:36:25.8 -- not an asteroid (will add it to exclusion list)
00:14:15.94 +51:38:24.2 -- not an asteroid (will add it to exclusion list)
23:19:11.20 +49:46:33.1 -- not an asteroid (will add it to exclusion list)
23:26:08.38 +54:33:35.2 -- not an asteroid (will add it to exclusion list)
23:27:28.85 +54:50:53.7 -- not an asteroid (will add it to exclusion list)
00:20:07.24 +55:23:46.8 -- not an asteroid (will add it to exclusion list)
23:26:19.55 +55:50:52.0 -- not an asteroid (will add it to exclusion list)
23:33:42.98 +53:53:38.6 -- not an asteroid (will add it to exclusion list)
23:20:42.74 +52:39:38.0 -- not an asteroid (will add it to exclusion list)
23:22:56.11 +53:23:03.4 -- not an asteroid (will add it to exclusion list)
00:24:44.60 +53:17:26.5 -- not an asteroid (will add it to exclusion list)
23:55:41.04 +51:20:12.0 -- not an asteroid (will add it to exclusion list)
23:26:49.98 +50:38:35.5 -- not an asteroid (will add it to exclusion list)
23:19:24.36 +56:40:25.8 -- not an asteroid (will add it to exclusion list)
00:07:16.39 +54:17:21.5 -- not an asteroid (will add it to exclusion list)
00:14:54.54 +52:36:35.4 -- not an asteroid (will add it to exclusion list)
23:16:32.11 +53:16:20.1 -- not an asteroid (will add it to exclusion list)
00:15:46.58 +50:56:07.8 -- not an asteroid (will add it to exclusion list)
23:18:10.20 +54:54:18.8 -- not an asteroid (will add it to exclusion list)
23:22:53.15 +57:44:50.0 -- not an asteroid (will add it to exclusion list)
23:17:25.89 +53:38:26.6 -- not an asteroid (will add it to exclusion list)
23:12:46.68 +56:35:07.2 -- not an asteroid (will add it to exclusion list)
23:42:45.94 +54:49:23.6 -- not an asteroid (will add it to exclusion list)
23:57:57.23 +51:06:43.5 -- not an asteroid (will add it to exclusion list)
23:26:31.44 +55:59:44.4 -- not an asteroid (will add it to exclusion list)
23:51:07.43 +50:04:53.9 -- not an asteroid (will add it to exclusion list)
00:00:24.11 +51:47:09.1 -- not an asteroid (will add it to exclusion list)
00:12:51.74 +50:33:59.7 -- not an asteroid (will add it to exclusion list)
23:17:43.46 +50:37:44.9 -- not an asteroid (will add it to exclusion list)
00:24:22.38 +56:28:53.4 -- not an asteroid (will add it to exclusion list)
00:24:09.22 +50:06:56.0 -- not an asteroid (will add it to exclusion list)
00:06:12.63 +51:04:14.6 -- not an asteroid (will add it to exclusion list)
00:01:21.08 +53:54:25.4 -- not an asteroid (will add it to exclusion list)
23:23:13.93 +56:37:19.1 -- not an asteroid (will add it to exclusion list)
23:25:02.24 +54:21:52.4 -- not an asteroid (will add it to exclusion list)
23:46:36.30 +51:22:55.7 -- not an asteroid (will add it to exclusion list)
00:28:59.75 +53:42:07.5 -- not an asteroid (will add it to exclusion list)
00:09:54.87 +51:05:44.9 -- not an asteroid (will add it to exclusion list)
00:08:37.39 +53:17:20.7 -- not an asteroid (will add it to exclusion list)
00:18:21.43 +52:39:28.2 -- not an asteroid (will add it to exclusion list)
23:31:56.27 +55:25:40.4 -- not an asteroid (will add it to exclusion list)
23:41:51.34 +54:18:07.8 -- not an asteroid (will add it to exclusion list)
23:58:09.16 +50:28:52.3 -- not an asteroid (will add it to exclusion list)
23:48:20.07 +51:27:53.8 -- not an asteroid (will add it to exclusion list)
23:35:43.27 +49:56:04.9 -- not an asteroid (will add it to exclusion list)
23:41:30.99 +50:42:02.5 -- not an asteroid (will add it to exclusion list)
23:33:38.32 +57:50:17.3 -- not an asteroid (will add it to exclusion list)
23:38:09.74 +50:55:35.9 -- not an asteroid (will add it to exclusion list)
23:16:57.80 +55:08:21.1 -- not an asteroid (will add it to exclusion list)
00:10:38.72 +56:15:30.5 -- not an asteroid (will add it to exclusion list)
23:42:54.31 +54:20:57.0 -- not an asteroid (will add it to exclusion list)
23:45:41.18 +50:59:07.9 -- not an asteroid (will add it to exclusion list)
23:23:07.37 +53:42:19.1 -- not an asteroid (will add it to exclusion list)
23:30:13.07 +56:22:02.0 -- not an asteroid (will add it to exclusion list)
23:19:42.83 +50:14:40.0 -- not an asteroid (will add it to exclusion list)
23:19:36.79 +50:35:39.9 -- not an asteroid (will add it to exclusion list)
23:56:02.02 +51:54:41.2 -- not an asteroid (will add it to exclusion list)
00:16:21.13 +53:48:36.6 -- not an asteroid (will add it to exclusion list)
23:51:03.48 +53:48:39.5 -- not an asteroid (will add it to exclusion list)
23:43:22.46 +52:13:17.4 -- not an asteroid (will add it to exclusion list)
23:24:24.72 +53:44:34.2 -- not an asteroid (will add it to exclusion list)
23:24:40.83 +50:27:52.6 -- not an asteroid (will add it to exclusion list)
23:36:35.61 +53:39:17.1 -- not an asteroid (will add it to exclusion list)
23:22:12.61 +52:12:31.6 -- not an asteroid (will add it to exclusion list)
23:23:01.05 +53:16:37.0 -- not an asteroid (will add it to exclusion list)
23:17:45.15 +56:02:13.8 -- not an asteroid (will add it to exclusion list)
23:22:37.19 +56:31:56.8 -- not an asteroid (will add it to exclusion list)
23:42:17.05 +55:27:07.3 -- not an asteroid (will add it to exclusion list)
23:46:10.21 +55:17:36.1 -- not an asteroid (will add it to exclusion list)
23:36:05.03 +55:53:53.4 -- not an asteroid (will add it to exclusion list)
23:25:25.15 +57:39:33.7 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:07.71 +51:20:32.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:24.11 +51:47:09.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:45.62 +52:08:08.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:55.76 +53:32:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:04.96 +53:29:22.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:21.08 +53:54:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:20.16 +54:17:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:46.70 +51:31:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:15.67 +54:09:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:29.32 +53:34:29.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:42.47 +51:10:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:44.07 +50:50:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:51.22 +51:49:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:10.54 +53:29:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:43.27 +51:19:46.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:54.67 +50:30:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:09.84 +52:39:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:13.90 +51:50:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:25.10 +52:54:41.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:42.71 +50:40:43.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:00.89 +51:25:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:12.63 +51:04:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:16.39 +54:17:21.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:16.78 +51:00:16.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:27.37 +50:53:53.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:29.71 +51:05:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:46.54 +53:00:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:46.98 +54:40:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:06.07 +51:46:30.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:08.63 +52:36:24.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:37.39 +53:17:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:56.57 +52:27:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:04.15 +51:44:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:16.55 +53:22:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:54.87 +51:05:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:19.91 +51:21:36.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:38.72 +56:15:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:42.07 +53:58:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:06.51 +52:49:27.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:47.58 +49:45:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:51.74 +50:33:59.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:02.17 +53:50:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:35.89 +52:59:14.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:12.21 +51:14:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:15.94 +51:38:24.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:54.54 +52:36:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:58.08 +54:13:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:17.11 +53:44:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:46.58 +50:56:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:46.91 +51:08:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:49.44 +57:32:33.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:21.13 +53:48:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:43.41 +52:48:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:44.21 +54:00:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:10.10 +50:18:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:18.55 +50:49:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:16.38 +50:20:06.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:21.43 +52:39:28.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:54.23 +51:50:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:37.41 +50:48:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:42.47 +50:07:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:05.82 +56:06:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:07.24 +55:23:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:11.77 +56:00:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:15.23 +53:28:42.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:06.58 +55:34:33.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:28.01 +50:43:42.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:49.35 +53:31:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:13.73 +56:00:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:20.28 +54:55:57.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:08.78 +50:22:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:09.22 +50:06:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:22.38 +56:28:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:44.60 +53:17:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:19.84 +55:36:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:26.06 +54:36:46.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:38.27 +51:57:37.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:14.34 +55:46:35.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:26:19.09 +55:49:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:59.75 +53:42:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:16.52 +53:48:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:31.47 +54:18:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:57.48 +55:56:08.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:20.72 +57:28:17.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:00.82 +56:27:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:46.68 +56:35:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:57.41 +55:27:59.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:59.40 +56:18:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:13.59 +55:44:21.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:59.72 +56:34:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:04.18 +56:21:23.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:05.90 +55:29:19.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:19.90 +56:28:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:21.80 +56:45:14.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:31.07 +55:22:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:33.27 +57:05:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:37.48 +56:41:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:14:38.03 +57:34:53.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:00.47 +55:26:12.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:32.01 +55:29:11.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:40.09 +52:17:13.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:41.40 +52:13:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:57.58 +56:35:13.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:57.75 +54:49:29.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:14.45 +55:12:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:32.11 +53:16:20.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:32.99 +54:49:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:46.59 +53:53:20.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:49.00 +56:44:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:57.80 +55:08:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:14.26 +56:09:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:23.23 +53:56:34.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:25.89 +53:38:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:33.23 +56:09:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:33.82 +53:32:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:43.46 +50:37:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:45.15 +56:02:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:49.65 +51:39:55.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:56.52 +56:24:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:59.42 +54:10:03.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:10.20 +54:54:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:10.73 +56:56:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:16.06 +54:05:41.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:52.43 +54:59:00.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:03.26 +50:34:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:09.50 +56:44:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:11.20 +49:46:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:14.01 +52:17:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:19.85 +51:15:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:22.81 +54:27:13.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:24.36 +56:40:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:26.91 +55:24:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:36.79 +50:35:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:42.83 +50:14:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:44.60 +56:11:03.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:01.55 +49:31:29.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:08.25 +49:57:27.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:39.52 +54:42:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:42.74 +52:39:38.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:50.41 +55:51:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:42.74 +50:06:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:44.64 +54:27:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:56.34 +51:25:10.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:05.49 +50:07:46.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:12.61 +52:12:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:22.34 +51:21:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:35.41 +56:22:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:37.19 +56:31:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:50.94 +51:55:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:53.15 +57:44:50.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:56.11 +53:23:03.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:01.05 +53:16:37.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:07.37 +53:42:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:07.72 +52:03:07.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:09.30 +53:47:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:12.95 +54:50:22.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.51 +56:57:50.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:13.93 +56:37:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:20.81 +49:55:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:21.75 +57:09:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:22.94 +56:38:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:12.68 +57:04:12.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:24.72 +53:44:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:40.83 +50:27:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:02.24 +54:21:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:22.78 +54:25:09.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:25.15 +57:39:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:30.43 +56:41:11.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:40.67 +53:22:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:08.38 +54:33:35.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:19.55 +55:50:52.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:31.44 +55:59:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:49.98 +50:38:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:51.29 +50:21:09.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:52.38 +52:05:31.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:59.99 +54:16:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:03.80 +49:50:11.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:07.82 +56:39:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:28.85 +54:50:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:29.73 +54:49:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:37.67 +55:29:26.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:40.60 +53:31:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:41.87 +53:31:05.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:45.51 +55:44:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:49.24 +56:49:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:58.34 +57:50:03.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:02.60 +55:38:41.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:15.12 +51:28:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:19.61 +53:31:54.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:37.49 +53:47:15.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:40.35 +52:21:28.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:10.55 +56:37:30.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:19.38 +54:25:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:29.97 +49:37:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:49.37 +53:55:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:51.74 +53:53:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:06.75 +51:01:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:13.07 +56:22:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:31.11 +54:53:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:40.76 +54:19:12.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:40.99 +51:38:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:46.14 +55:32:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:16.87 +51:15:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:43.53 +51:03:14.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:56.27 +55:25:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:02.31 +51:29:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:03.08 +54:01:00.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:06.07 +56:48:05.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:10.67 +52:27:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:19.52 +54:37:52.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:21.84 +56:20:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:27.80 +55:10:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:40.34 +56:50:03.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:44.09 +53:36:12.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:51.48 +54:47:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:52.68 +53:44:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:38.32 +57:50:17.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:42.98 +53:53:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:46.45 +54:02:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:06.86 +54:09:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:13.82 +56:18:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:54.46 +52:08:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:43.27 +49:56:04.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:59.28 +53:20:20.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:05.03 +55:53:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:35.61 +53:39:17.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:01.45 +49:45:09.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:55.93 +56:26:09.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:09.74 +50:55:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:08.18 +51:12:37.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:09.88 +50:57:48.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:36.44 +51:31:04.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:45.44 +51:01:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:55.79 +51:47:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:07.91 +51:56:11.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:25.77 +51:36:38.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:56.61 +56:21:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:56.86 +54:14:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:14.04 +49:49:36.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:28.09 +55:38:06.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:30.99 +50:42:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:48.59 +51:06:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:51.34 +54:18:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:14.12 +53:08:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:17.05 +55:27:07.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:45.94 +54:49:23.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:54.31 +54:20:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:58.53 +50:44:45.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:08.28 +54:27:23.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:16.32 +53:14:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:22.46 +52:13:17.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:41.74 +53:56:59.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:57.31 +50:48:34.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:02.40 +50:40:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:14.23 +53:16:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:34.09 +55:20:20.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:02.68 +50:35:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:23.48 +50:07:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:24.33 +54:30:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:25.99 +54:37:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:29.79 +53:49:35.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:38.77 +51:01:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:41.18 +50:59:07.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:43.67 +53:35:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:01.92 +54:36:44.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:07.83 +52:16:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:10.21 +55:17:36.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:20.17 +51:20:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:36.23 +53:17:01.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:36.30 +51:22:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:42.52 +51:44:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:56.17 +50:14:16.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:01.71 +49:59:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:15.24 +50:33:25.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:20.07 +51:27:53.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:47.93 +49:47:28.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:52.01 +52:53:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:39.37 +51:05:46.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:08.86 +50:52:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:29.86 +53:22:50.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:41.11 +50:27:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:03.48 +53:48:39.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:07.43 +50:04:53.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:14.86 +51:03:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:24.01 +53:36:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:39.63 +50:16:05.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:03.54 +52:58:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:37.64 +53:51:51.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:10.37 +53:00:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:43.24 +50:58:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:54.47 +53:23:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:56.97 +50:54:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:57.85 +51:34:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:22.33 +50:47:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:22.54 +51:29:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:29.98 +51:30:59.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:32.82 +51:24:52.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:41.04 +51:20:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:59.04 +52:04:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:02.02 +51:54:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:35.62 +53:30:25.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:49.38 +50:03:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:49.41 +50:59:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:51.73 +51:51:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:57.38 +51:38:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:03.71 +52:12:03.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:13.90 +51:50:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:16.88 +54:23:51.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:57.23 +51:06:43.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:58.05 +50:00:24.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:00.09 +54:14:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:09.16 +50:28:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:27.60 +52:16:15.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:50.68 +54:12:44.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:31.01 +54:09:43.4 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:00:07.71 +51:20:32.3 -- not a known variable star
00:00:24.11 +51:47:09.1 -- not a known variable star
00:00:45.62 +52:08:08.6 -- not a known variable star
00:00:55.76 +53:32:19.1 -- not a known variable star
00:01:04.96 +53:29:22.4 -- not a known variable star
00:01:21.08 +53:54:25.4 -- not a known variable star
00:02:20.16 +54:17:37.2 -- not a known variable star
00:02:46.70 +51:31:11.0 -- not a known variable star
00:03:15.67 +54:09:51.9 -- not a known variable star
00:03:29.32 +53:34:29.9 -- not a known variable star
00:03:42.47 +51:10:37.1 -- a known variable star
00:03:44.07 +50:50:17.0 -- not a known variable star
00:03:51.22 +51:49:58.3 -- not a known variable star
00:04:10.54 +53:29:36.3 -- a known variable star
00:04:43.27 +51:19:46.0 -- not a known variable star
00:04:54.67 +50:30:18.5 -- not a known variable star
00:05:09.84 +52:39:12.8 -- not a known variable star
00:05:13.90 +51:50:43.2 -- not a known variable star
00:05:25.10 +52:54:41.6 -- not a known variable star
00:05:42.71 +50:40:43.5 -- a known variable star
00:06:00.89 +51:25:00.3 -- not a known variable star
00:06:12.63 +51:04:14.6 -- not a known variable star
00:07:16.39 +54:17:21.5 -- not a known variable star
00:07:16.78 +51:00:16.6 -- not a known variable star
00:07:27.37 +50:53:53.2 -- not a known variable star
00:07:29.71 +51:05:34.7 -- not a known variable star
00:07:46.54 +53:00:37.9 -- not a known variable star
00:07:46.98 +54:40:43.2 -- not a known variable star
00:08:06.07 +51:46:30.8 -- not a known variable star
00:08:08.63 +52:36:24.0 -- not a known variable star
00:08:37.39 +53:17:20.7 -- not a known variable star
00:08:56.57 +52:27:44.6 -- not a known variable star
00:09:04.15 +51:44:04.5 -- not a known variable star
00:09:16.55 +53:22:03.5 -- not a known variable star
00:09:54.87 +51:05:44.9 -- not a known variable star
00:10:19.91 +51:21:36.9 -- not a known variable star
00:10:38.72 +56:15:30.5 -- not a known variable star
00:10:42.07 +53:58:57.0 -- not a known variable star
00:12:06.51 +52:49:27.0 -- not a known variable star
00:12:47.58 +49:45:34.5 -- not a known variable star
00:12:51.74 +50:33:59.7 -- not a known variable star
00:13:02.17 +53:50:14.5 -- not a known variable star
00:13:35.89 +52:59:14.9 -- not a known variable star
00:14:12.21 +51:14:39.4 -- not a known variable star
00:14:15.94 +51:38:24.2 -- not a known variable star
00:14:54.54 +52:36:35.4 -- not a known variable star
00:14:58.08 +54:13:21.4 -- not a known variable star
00:15:17.11 +53:44:11.7 -- not a known variable star
00:15:46.58 +50:56:07.8 -- not a known variable star
00:15:46.91 +51:08:54.9 -- not a known variable star
00:15:49.44 +57:32:33.9 -- a known variable star
00:16:21.13 +53:48:36.6 -- not a known variable star
00:16:43.41 +52:48:43.9 -- not a known variable star
00:16:44.21 +54:00:39.1 -- not a known variable star
00:17:10.10 +50:18:51.7 -- not a known variable star
00:17:18.55 +50:49:48.3 -- not a known variable star
00:18:16.38 +50:20:06.6 -- not a known variable star
00:18:21.43 +52:39:28.2 -- not a known variable star
00:18:54.23 +51:50:01.8 -- not a known variable star
00:19:37.41 +50:48:31.5 -- not a known variable star
00:19:42.47 +50:07:36.4 -- not a known variable star
00:20:05.82 +56:06:38.9 -- not a known variable star
00:20:07.24 +55:23:46.8 -- a known variable star
00:20:11.77 +56:00:27.7 -- not a known variable star
00:20:15.23 +53:28:42.0 -- not a known variable star
00:22:06.58 +55:34:33.6 -- not a known variable star
00:22:28.01 +50:43:42.9 -- not a known variable star
00:22:49.35 +53:31:12.0 -- not a known variable star
00:23:13.73 +56:00:14.0 -- not a known variable star
00:23:20.28 +54:55:57.7 -- not a known variable star
00:24:08.78 +50:22:31.0 -- not a known variable star
00:24:09.22 +50:06:56.0 -- not a known variable star
00:24:22.38 +56:28:53.4 -- a known variable star
00:24:44.60 +53:17:26.5 -- not a known variable star
00:25:19.84 +55:36:44.6 -- not a known variable star
00:25:26.06 +54:36:46.7 -- not a known variable star
00:25:38.27 +51:57:37.6 -- not a known variable star
00:26:14.34 +55:46:35.7 -- not a known variable star
00:26:19.09 +55:49:26.5 -- not a known variable star
00:28:59.75 +53:42:07.5 -- not a known variable star
00:29:16.52 +53:48:56.1 -- not a known variable star
00:29:31.47 +54:18:13.1 -- a known variable star
00:30:57.48 +55:56:08.1 -- not a known variable star
23:10:20.72 +57:28:17.8 -- not a known variable star
23:12:00.82 +56:27:27.7 -- not a known variable star
23:12:46.68 +56:35:07.2 -- not a known variable star
23:12:57.41 +55:27:59.3 -- a known variable star
23:12:59.40 +56:18:49.8 -- not a known variable star
23:13:13.59 +55:44:21.5 -- not a known variable star
23:13:59.72 +56:34:34.3 -- not a known variable star
23:14:04.18 +56:21:23.9 -- not a known variable star
23:14:05.90 +55:29:19.6 -- not a known variable star
23:14:19.90 +56:28:34.6 -- not a known variable star
23:14:21.80 +56:45:14.8 -- not a known variable star
23:14:31.07 +55:22:29.6 -- not a known variable star
23:14:33.27 +57:05:59.1 -- not a known variable star
23:14:37.48 +56:41:29.6 -- not a known variable star
23:14:38.03 +57:34:53.5 -- not a known variable star
23:15:00.47 +55:26:12.5 -- not a known variable star
23:15:32.01 +55:29:11.5 -- a known variable star
23:15:40.09 +52:17:13.7 -- not a known variable star
23:15:41.40 +52:13:42.3 -- not a known variable star
23:15:57.58 +56:35:13.7 -- not a known variable star
23:15:57.75 +54:49:29.8 -- not a known variable star
23:16:14.45 +55:12:26.1 -- not a known variable star
23:16:32.11 +53:16:20.1 -- not a known variable star
23:16:32.99 +54:49:21.6 -- not a known variable star
23:16:46.59 +53:53:20.6 -- not a known variable star
23:16:49.00 +56:44:36.0 -- not a known variable star
23:16:57.80 +55:08:21.1 -- not a known variable star
23:17:14.26 +56:09:07.2 -- not a known variable star
23:17:23.23 +53:56:34.4 -- a known variable star
23:17:25.89 +53:38:26.6 -- not a known variable star
23:17:33.23 +56:09:21.6 -- not a known variable star
23:17:33.82 +53:32:22.2 -- not a known variable star
23:17:43.46 +50:37:44.9 -- not a known variable star
23:17:45.15 +56:02:13.8 -- not a known variable star
23:17:49.65 +51:39:55.5 -- not a known variable star
23:17:56.52 +56:24:55.7 -- not a known variable star
23:17:59.42 +54:10:03.1 -- not a known variable star
23:18:10.20 +54:54:18.8 -- not a known variable star
23:18:10.73 +56:56:38.8 -- not a known variable star
23:18:16.06 +54:05:41.0 -- a known variable star
23:18:52.43 +54:59:00.9 -- not a known variable star
23:19:03.26 +50:34:01.5 -- not a known variable star
23:19:09.50 +56:44:16.5 -- not a known variable star
23:19:11.20 +49:46:33.1 -- not a known variable star
23:19:14.01 +52:17:58.3 -- not a known variable star
23:19:19.85 +51:15:48.2 -- not a known variable star
23:19:22.81 +54:27:13.9 -- not a known variable star
23:19:24.36 +56:40:25.8 -- not a known variable star
23:19:26.91 +55:24:29.3 -- not a known variable star
23:19:36.79 +50:35:39.9 -- not a known variable star
23:19:42.83 +50:14:40.0 -- not a known variable star
23:19:44.60 +56:11:03.8 -- not a known variable star
23:20:01.55 +49:31:29.5 -- not a known variable star
23:20:08.25 +49:57:27.5 -- not a known variable star
23:20:39.52 +54:42:07.1 -- not a known variable star
23:20:42.74 +52:39:38.0 -- not a known variable star
23:20:50.41 +55:51:37.3 -- not a known variable star
23:21:42.74 +50:06:34.6 -- not a known variable star
23:21:44.64 +54:27:13.8 -- not a known variable star
23:21:56.34 +51:25:10.8 -- not a known variable star
23:22:05.49 +50:07:46.9 -- not a known variable star
23:22:12.61 +52:12:31.6 -- not a known variable star
23:22:22.34 +51:21:56.1 -- not a known variable star
23:22:35.41 +56:22:51.3 -- not a known variable star
23:22:37.19 +56:31:56.8 -- a known variable star
23:22:50.94 +51:55:48.4 -- not a known variable star
23:22:53.15 +57:44:50.0 -- not a known variable star
23:22:56.11 +53:23:03.4 -- not a known variable star
23:23:01.05 +53:16:37.0 -- not a known variable star
23:23:07.37 +53:42:19.1 -- not a known variable star
23:23:07.72 +52:03:07.7 -- not a known variable star
23:23:09.30 +53:47:07.2 -- not a known variable star
23:23:12.95 +54:50:22.9 -- not a known variable star
23:23:13.51 +56:57:50.2 -- not a known variable star
23:23:13.93 +56:37:19.1 -- not a known variable star
23:23:20.81 +49:55:24.7 -- not a known variable star
23:23:21.75 +57:09:34.2 -- not a known variable star
23:23:22.94 +56:38:57.9 -- not a known variable star
23:24:12.68 +57:04:12.5 -- not a known variable star
23:24:24.72 +53:44:34.2 -- not a known variable star
23:24:40.83 +50:27:52.6 -- a known variable star
23:25:02.24 +54:21:52.4 -- not a known variable star
23:25:22.78 +54:25:09.9 -- not a known variable star
23:25:25.15 +57:39:33.7 -- not a known variable star
23:25:30.43 +56:41:11.0 -- not a known variable star
23:25:40.67 +53:22:58.3 -- not a known variable star
23:26:08.38 +54:33:35.2 -- not a known variable star
23:26:19.55 +55:50:52.0 -- not a known variable star
23:26:31.44 +55:59:44.4 -- not a known variable star
23:26:49.98 +50:38:35.5 -- not a known variable star
23:26:51.29 +50:21:09.2 -- not a known variable star
23:26:52.38 +52:05:31.3 -- not a known variable star
23:26:59.99 +54:16:27.2 -- not a known variable star
23:27:03.80 +49:50:11.8 -- not a known variable star
23:27:07.82 +56:39:13.1 -- not a known variable star
23:27:28.85 +54:50:53.7 -- not a known variable star
23:27:29.73 +54:49:53.3 -- not a known variable star
23:27:37.67 +55:29:26.3 -- not a known variable star
23:27:40.60 +53:31:39.7 -- not a known variable star
23:27:41.87 +53:31:05.3 -- not a known variable star
23:27:45.51 +55:44:30.1 -- not a known variable star
23:27:49.24 +56:49:27.4 -- not a known variable star
23:27:58.34 +57:50:03.6 -- not a known variable star
23:28:02.60 +55:38:41.1 -- not a known variable star
23:28:15.12 +51:28:51.5 -- not a known variable star
23:28:19.61 +53:31:54.8 -- not a known variable star
23:28:37.49 +53:47:15.7 -- not a known variable star
23:28:40.35 +52:21:28.3 -- not a known variable star
23:29:10.55 +56:37:30.6 -- not a known variable star
23:29:19.38 +54:25:59.6 -- not a known variable star
23:29:29.97 +49:37:15.3 -- not a known variable star
23:29:49.37 +53:55:42.4 -- not a known variable star
23:29:51.74 +53:53:21.4 -- not a known variable star
23:30:06.75 +51:01:43.6 -- not a known variable star
23:30:13.07 +56:22:02.0 -- not a known variable star
23:30:31.11 +54:53:22.7 -- not a known variable star
23:30:40.76 +54:19:12.6 -- not a known variable star
23:30:40.99 +51:38:18.3 -- not a known variable star
23:30:46.14 +55:32:54.9 -- not a known variable star
23:31:16.87 +51:15:22.6 -- not a known variable star
23:31:43.53 +51:03:14.4 -- not a known variable star
23:31:56.27 +55:25:40.4 -- not a known variable star
23:32:02.31 +51:29:10.2 -- not a known variable star
23:32:03.08 +54:01:00.9 -- not a known variable star
23:32:06.07 +56:48:05.2 -- not a known variable star
23:32:10.67 +52:27:49.1 -- not a known variable star
23:32:19.52 +54:37:52.5 -- not a known variable star
23:32:21.84 +56:20:21.3 -- not a known variable star
23:32:27.80 +55:10:17.5 -- not a known variable star
23:32:40.34 +56:50:03.2 -- not a known variable star
23:32:44.09 +53:36:12.7 -- not a known variable star
23:32:51.48 +54:47:21.1 -- not a known variable star
23:32:52.68 +53:44:56.8 -- not a known variable star
23:33:38.32 +57:50:17.3 -- not a known variable star
23:33:42.98 +53:53:38.6 -- not a known variable star
23:33:46.45 +54:02:56.0 -- not a known variable star
23:34:06.86 +54:09:21.7 -- not a known variable star
23:34:13.82 +56:18:02.1 -- not a known variable star
23:34:54.46 +52:08:21.4 -- not a known variable star
23:35:43.27 +49:56:04.9 -- not a known variable star
23:35:59.28 +53:20:20.0 -- not a known variable star
23:36:05.03 +55:53:53.4 -- not a known variable star
23:36:35.61 +53:39:17.1 -- not a known variable star
23:37:01.45 +49:45:09.2 -- not a known variable star
23:37:55.93 +56:26:09.0 -- not a known variable star
23:38:09.74 +50:55:35.9 -- not a known variable star
23:39:08.18 +51:12:37.7 -- a known variable star
23:39:09.88 +50:57:48.1 -- not a known variable star
23:39:36.44 +51:31:04.7 -- not a known variable star
23:39:45.44 +51:01:24.4 -- not a known variable star
23:39:55.79 +51:47:05.1 -- not a known variable star
23:40:07.91 +51:56:11.6 -- not a known variable star
23:40:25.77 +51:36:38.1 -- not a known variable star
23:40:56.61 +56:21:53.9 -- not a known variable star
23:40:56.86 +54:14:01.2 -- not a known variable star
23:41:14.04 +49:49:36.9 -- not a known variable star
23:41:28.09 +55:38:06.9 -- not a known variable star
23:41:30.99 +50:42:02.5 -- not a known variable star
23:41:48.59 +51:06:39.4 -- not a known variable star
23:41:51.34 +54:18:07.8 -- not a known variable star
23:42:14.12 +53:08:22.6 -- not a known variable star
23:42:17.05 +55:27:07.3 -- not a known variable star
23:42:45.94 +54:49:23.6 -- not a known variable star
23:42:54.31 +54:20:57.0 -- not a known variable star
23:42:58.53 +50:44:45.4 -- not a known variable star
23:43:08.28 +54:27:23.6 -- a known variable star
23:43:16.32 +53:14:40.0 -- not a known variable star
23:43:22.46 +52:13:17.4 -- not a known variable star
23:43:41.74 +53:56:59.9 -- not a known variable star
23:43:57.31 +50:48:34.4 -- not a known variable star
23:44:02.40 +50:40:34.5 -- a known variable star
23:44:14.23 +53:16:50.7 -- not a known variable star
23:44:34.09 +55:20:20.6 -- not a known variable star
23:45:02.68 +50:35:00.8 -- not a known variable star
23:45:23.48 +50:07:59.0 -- not a known variable star
23:45:24.33 +54:30:54.7 -- not a known variable star
23:45:25.99 +54:37:38.3 -- not a known variable star
23:45:29.79 +53:49:35.1 -- not a known variable star
23:45:38.77 +51:01:03.5 -- not a known variable star
23:45:41.18 +50:59:07.9 -- not a known variable star
23:45:43.67 +53:35:11.7 -- not a known variable star
23:46:01.92 +54:36:44.3 -- not a known variable star
23:46:07.83 +52:16:11.1 -- not a known variable star
23:46:10.21 +55:17:36.1 -- not a known variable star
23:46:20.17 +51:20:04.0 -- not a known variable star
23:46:36.23 +53:17:01.6 -- not a known variable star
23:46:36.30 +51:22:55.7 -- not a known variable star
23:46:42.52 +51:44:29.6 -- not a known variable star
23:47:56.17 +50:14:16.4 -- a known variable star
23:48:01.71 +49:59:48.2 -- not a known variable star
23:48:15.24 +50:33:25.1 -- not a known variable star
23:48:20.07 +51:27:53.8 -- not a known variable star
23:48:47.93 +49:47:28.5 -- not a known variable star
23:48:52.01 +52:53:34.7 -- not a known variable star
23:49:39.37 +51:05:46.5 -- not a known variable star
23:50:08.86 +50:52:22.0 -- not a known variable star
23:50:29.86 +53:22:50.3 -- not a known variable star
23:50:41.11 +50:27:38.6 -- not a known variable star
23:51:03.48 +53:48:39.5 -- not a known variable star
23:51:07.43 +50:04:53.9 -- not a known variable star
23:51:14.86 +51:03:18.7 -- not a known variable star
23:51:24.01 +53:36:25.8 -- not a known variable star
23:51:39.63 +50:16:05.2 -- not a known variable star
23:52:03.54 +52:58:06.0 -- a known variable star
23:52:37.64 +53:51:51.1 -- not a known variable star
23:53:10.37 +53:00:57.2 -- not a known variable star
23:53:43.24 +50:58:21.1 -- not a known variable star
23:53:54.47 +53:23:43.6 -- not a known variable star
23:53:56.97 +50:54:38.3 -- not a known variable star
23:53:57.85 +51:34:47.9 -- not a known variable star
23:54:22.33 +50:47:56.9 -- not a known variable star
23:54:22.54 +51:29:59.1 -- not a known variable star
23:55:29.98 +51:30:59.5 -- not a known variable star
23:55:32.82 +51:24:52.5 -- not a known variable star
23:55:41.04 +51:20:12.0 -- not a known variable star
23:55:59.04 +52:04:39.6 -- not a known variable star
23:56:02.02 +51:54:41.2 -- not a known variable star
23:56:35.62 +53:30:25.1 -- not a known variable star
23:56:49.38 +50:03:02.2 -- not a known variable star
23:56:49.41 +50:59:53.3 -- not a known variable star
23:56:51.73 +51:51:53.0 -- not a known variable star
23:56:57.38 +51:38:21.3 -- not a known variable star
23:57:03.71 +52:12:03.8 -- not a known variable star
23:57:13.90 +51:50:34.6 -- not a known variable star
23:57:16.88 +54:23:51.7 -- a known variable star
23:57:57.23 +51:06:43.5 -- not a known variable star
23:57:58.05 +50:00:24.8 -- not a known variable star
23:58:00.09 +54:14:36.2 -- not a known variable star
23:58:09.16 +50:28:52.3 -- not a known variable star
23:58:27.60 +52:16:15.8 -- not a known variable star
23:58:50.68 +54:12:44.4 -- not a known variable star
23:59:31.01 +54:09:43.4 -- not a known variable star
Found 296 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
315 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 315 (excluding asteroids and hot pixels, 296 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.84110317 -observatory V36
09:45:05.81 +15:19:29.0 Mercury (-1.7mag)
12:50:09.57 -07:46:12.2 Venus (-4.5mag)
06:29:49.60 +23:39:00.2 Mars (1.3mag)
08:55:29.20 +17:53:07.1 Jupiter (-1.8mag)
00:54:49.38 +03:01:33.5 Saturn (0.5mag)
04:13:02.19 +21:00:19.1 Uranus (5.7mag)
00:15:08.08 +00:06:17.0 Neptune (7.7mag)
20:26:50.70 -23:35:11.8 Pluto (14.5mag)
17:26:13.90 -28:32:16.6 Moon (-11.0mag)
-rw-r--r-- 1 apache apache 363 Aug 22 03:21 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461274.84110317:
08:55:33.17 +17:52:48.8 Io (6.1mag)
08:55:36.40 +17:52:34.7 Europa (6.3mag)
08:55:45.26 +17:51:54.1 Ganymede (5.6mag)
08:55:09.72 +17:54:38.6 Callisto (6.9mag)
08:52:57.43 +18:01:07.0 Himalia (15.7mag)
08:55:28.55 +17:53:11.0 Thebe (16.6mag)
08:52:36.66 +17:56:59.4 Elara (17.7mag)
08:59:36.81 +17:26:22.8 Pasiphae (17.9mag)
08:57:42.39 +18:06:41.9 Carme (19.0mag)
00:54:45.84 +03:01:58.8 Titan (8.4mag)
00:54:54.02 +03:01:24.1 Rhea (9.7mag)
00:55:24.82 +03:03:14.2 Iapetus (11.1mag)
00:54:57.29 +03:01:50.1 Hyperion (14.4mag)
00:53:54.17 +02:52:58.9 Phoebe (16.4mag)
-rw-r--r-- 1 apache apache 568 Aug 22 03:21 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461274.84110317:
20:11:51.98 -14:04:44.9 JWST
17:32:36.47 +35:47:03.5 Chandra
10:53:55.74 -59:08:50.9 XMM-Newton
-rw-r--r-- 1 apache apache 96 Aug 22 03:21 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461274.84110317 -observatory V36
03:28:14.47 +18:26:24.8 17.5mag P/1996 R2 (Lagerkvist)
17:59:54.59 -34:28:36.1 14.2mag P/2010 H2 (Vales)
07:06:29.51 -69:29:22.4 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
06:13:08.43 +33:18:25.8 17.7mag C/2017 K2 (PANSTARRS)
04:21:04.81 +42:24:14.1 17.5mag P/2021 N1 (ZTF)
22:26:44.68 +30:22:45.3 17.4mag C/2022 E2 (ATLAS)
06:56:53.87 +26:17:01.6 16.8mag C/2022 N2 (PANSTARRS)
10:34:41.58 +27:51:09.7 17.0mag C/2022 QE78 (ATLAS)
09:38:17.57 +05:17:59.6 18.0mag C/2022 R6 (PANSTARRS)
15:15:39.63 -12:52:39.2 18.0mag P/2023 B1 (PANSTARRS)
20:53:27.04 +64:04:25.1 18.0mag C/2023 H5 (Lemmon)
15:36:29.47 -14:13:54.0 14.6mag C/2023 R1 (PANSTARRS)
08:23:14.61 +32:00:42.4 15.5mag C/2024 E1 (Wierzchos)
15:05:42.23 +15:30:16.9 17.8mag C/2024 G6 (ATLAS)
18:46:52.36 +43:29:22.9 13.7mag C/2024 J3 (ATLAS)
20:49:26.04 +49:41:18.6 17.5mag C/2024 R4 (PANSTARRS)
05:25:45.07 -12:53:57.4 15.3mag C/2024 T5 (ATLAS)
07:04:36.16 +21:36:37.2 17.9mag C/2025 J1 (Borisov)
10:53:14.67 +19:57:32.5 17.1mag C/2025 V2 (Rankin)
13:07:23.02 +01:21:19.7 16.9mag C/2025 Y1 (ATLAS)
16:10:28.38 +76:17:30.6 16.5mag C/2026 A2 (Bok)
03:09:55.63 +46:20:58.9 17.3mag C/2026 B2 (Sun-Gao)
11:58:50.36 +09:55:35.5 17.4mag A/2026 E1
22:12:23.62 -32:17:53.6 7.1mag 10P/Tempel
11:37:42.66 -04:19:10.2 16.3mag 29P/Schwassmann-Wachmann
11:36:22.69 +00:01:45.8 17.4mag 63P/Wild
00:51:37.86 -06:06:06.3 15.4mag 65P/Gunn
06:06:44.79 +20:14:37.5 13.7mag 78P/Gehrels
20:25:50.65 -24:59:53.3 17.5mag 84P/Giclas
03:11:59.21 +14:32:11.1 16.9mag 88P/Howell
08:30:28.00 +25:35:20.3 16.4mag 93P/Lovas
04:47:31.12 +22:24:22.9 17.2mag 112P/Urata-Niijima
06:42:30.63 +28:18:02.8 16.1mag 114P/Wiseman-Skiff
09:51:36.70 +24:05:50.7 14.9mag 123P/West-Hartley
12:12:29.04 -15:35:56.7 17.3mag 124P/Mrkos
05:56:43.75 +21:01:46.5 16.0mag 128P/Shoemaker-Holt
06:51:55.42 +18:06:07.1 17.9mag 131P/Mueller
23:59:37.93 +03:06:04.0 17.4mag 139P/Vaisala-Oterma
03:09:38.82 -18:37:37.5 12.8mag 161P/Hartley-IRAS
08:03:33.57 +38:07:18.7 16.1mag 162P/Siding Spring
11:04:22.36 +29:57:22.4 12.2mag 169P/NEAT
03:06:09.37 +09:23:42.1 17.6mag 220P/McNaught
20:16:20.84 -51:48:44.2 18.0mag 259P/Garradd
04:03:13.27 +30:49:21.8 15.3mag 260P/McNaught
07:47:15.28 +37:05:21.6 17.3mag 295P/LINEAR
15:16:10.72 +01:33:24.3 17.8mag 391P/Kowalski
09:13:41.99 +17:40:07.3 17.9mag 450P/LONEOS
-rw-r--r-- 1 apache apache 2.3K Aug 22 03:21 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:21 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:21 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:21 tns_transients_list.txt
