This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.67 23:04:18.14 +64:23:31.0
111.67459 3.88758 galactic Cep Second-epoch detections are separated by 8.2" and 6.5 pix
The object was found in VSX 7" ZTF J230417.33+642326.7
Type: SR
# Max. Min./Amp. JD0 Period
15.946 r Y 0.182 r 2458325.94050 52.116709200000
ATTENTION: measured mag 11.67 is 4.1 mag brighter than the VSX record maximum brightness 15.76 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:18.14 +64:23:31.0: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:18.14 +64:23:31.0: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J230417.33+642326.7,2461235.6540,11.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J230417.33+642326.7 20260714.1540 11.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 10.96 23:11:57.43 +60:33:55.8
111.00423 0.01829 galactic Cep Second-epoch detections are separated by 8.7" 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 | ATO J347.9687+60.5725 | 23:11:57.43 +60:33:55.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:57.43 +60:33:55.8: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:57.43 +60:33:55.8: 15.67 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J347.9687+60.5725,2461235.6540,10.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J347.9687+60.5725 20260714.1540 10.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 07 14.1540 2461235.6540 9.63 00:36:51.69 +63:07:02.1
121.28504 0.29212 galactic Cas Second-epoch detections are separated by 2.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 | 00:36:51.69 +63:07:02.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:36:51.69 +63:07:02.1: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:36:51.69 +63:07:02.1: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 36 51.69 +63 07 02.1 9.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,2461235.6540,9.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 9.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 10.82 23:16:27.43 +64:56:10.0
113.08726 3.89562 galactic Cep Second-epoch detections are separated by 7.1" 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:16:27.43 +64:56:10.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:16:27.43 +64:56:10.0: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:16:27.43 +64:56:10.0: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,10.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 10.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.07 23:25:41.92 +62:16:34.8
113.14207 1.04542 galactic Cas Second-epoch detections are separated by 6.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:25:41.92 +62:16:34.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:41.92 +62:16:34.8: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:41.92 +62:16:34.8: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 41.92 +62 16 34.8 11.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.21 00:34:18.96 +64:31:04.4
121.09091 1.70736 galactic Cas Second-epoch detections are separated by 4.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 | 00:34:18.96 +64:31:04.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:18.96 +64:31:04.4: 15.37 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:34:18.96 +64:31:04.4: 15.77 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.49 +/- 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 07 14.1540* 00 34 18.96 +64 31 04.4 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.89 00:04:21.81 +61:29:34.4
117.34506 -0.86718 galactic Cas Second-epoch detections are separated by 6.7" and 7.3 pix
The object was found in VSX10" ZTF J000422.94+612939.4
Type: BY
# Max. Min./Amp. JD0 Period
20.016 r Y 0.302 r 2458271.94460 0.788855000000
ATTENTION: measured mag 11.89 is 7.8 mag brighter than the VSX record maximum brightness 19.71 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:21.81 +61:29:34.4: 13.06 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:04:21.81 +61:29:34.4: 12.93 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.99 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 04 21.81 +61 29 34.4 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000422.94+612939.4,2461235.6540,11.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J000422.94+612939.4 20260714.1540 11.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 8.35 00:54:55.87 +58:33:48.0
123.38867 -4.30532 galactic Cas Second-epoch detections are separated by 3.5" and 7.9 pix
The object was found in VSX16" W Cas
Type: M
# Max. Min./Amp. JD0 Period
8.200 V 13.000 V 2457218.00000 407.900000000000 C7,1e
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:54:55.87 +58:33:48.0: 9.96 +/- 0.00 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:54:55.87 +58:33:48.0: 10.57 +/- 0.00 detection
Forced photometry reference-image weighted average: 10.11 +/- 0.00
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 54 55.87 +58 33 48.0 8.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
W Cas,2461235.6540,8.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
W Cas 20260714.1540 8.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 07 14.1540 2461235.6540 10.88 23:03:27.30 +57:56:22.5
108.98089 -1.97720 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 | ATO J345.8481+57.9325 | 23:03:27.30 +57:56:22.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:27.30 +57:56:22.5: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:27.30 +57:56:22.5: 15.49 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 03 27.30 +57 56 22.5 10.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 J345.8481+57.9325,2461235.6540,10.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J345.8481+57.9325 20260714.1540 10.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 10.79 23:39:54.53 +59:34:56.9
113.98244 -2.04065 galactic Cas Second-epoch detections are separated by 3.7" and 7.1 pix
The object was found in VSX 5" ZTF J233954.35+593452.0
Type: EW
# Max. Min./Amp. JD0 Period
16.724 r Y 0.245 r 2458256.98080 0.348732200000
ATTENTION: measured mag 10.79 is 5.7 mag brighter than the VSX record maximum brightness 16.48 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:39:54.53 +59:34:56.9: 15.70 +/- 0.33 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:39:54.53 +59:34:56.9: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.70 +/- 0.33
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 39 54.53 +59 34 56.9 10.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J233954.35+593452.0,2461235.6540,10.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J233954.35+593452.0 20260714.1540 10.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.49 23:29:12.13 +61:01:50.8
113.13899 -0.26769 galactic Cas Second-epoch detections are separated by 6.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 | target | 23:29:12.13 +61:01:50.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:29:12.13 +61:01:50.8: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:12.13 +61:01:50.8: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 29 12.13 +61 01 50.8 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.31 00:09:36.37 +63:15:35.9
118.24688 0.76938 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:09:36.37 +63:15:35.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:36.37 +63:15:35.9: 15.95 +/- 0.34 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:09:36.37 +63:15:35.9: 16.11 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.95 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 09 36.37 +63 15 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,2461235.6540,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.29 23:05:38.20 +63:30:31.9
111.45573 3.01950 galactic Cep Second-epoch detections are separated by 4.4" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:05:38.20 +63:30:31.9 (user input) | T | P | (position from user input) J-Ks=1.136+/-0.122 (M)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:38.20 +63:30:31.9: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:38.20 +63:30:31.9: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.33 23:19:09.37 +63:08:34.7
112.72808 2.11409 galactic Cas Second-epoch detections are separated by 4.5" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015340737105586048 | 23:19:10.38 +63:08:01.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A0 1955IzKry..14....3B [B55b] 2208 J-Ks=1.319+/- (Very red! L if it's a dwarf)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:19:09.37 +63:08:34.7: 15.17 +/- 0.17 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:19:09.37 +63:08:34.7: 15.75 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.31 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 19 09.37 +63 08 34.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015340737105586048,2461235.6540,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2015340737105586048 20260714.1540 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 07 14.1540 2461235.6540 14.05 23:56:15.10 +60:36:10.9
116.20715 -1.54616 galactic Cas Second-epoch detections are separated by 2.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 | target | 23:56:15.10 +60:36:10.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:56:15.10 +60:36:10.9: 16.07 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:56:15.10 +60:36:10.9: 16.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 07 14.1540* 23 56 15.10 +60 36 10.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,2461235.6540,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.06 23:33:36.03 +60:24:35.3
113.46213 -1.02292 galactic Cas Second-epoch detections are separated by 4.1" 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:33:36.03 +60:24:35.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:36.03 +60:24:35.3: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:36.03 +60:24:35.3: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 33 36.03 +60 24 35.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,2461235.6540,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.04 23:18:19.01 +60:57:16.5
111.86910 0.09885 galactic Cas Second-epoch detections are separated by 6.3" 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:18:19.01 +60:57:16.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:18:19.01 +60:57:16.5: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:18:19.01 +60:57:16.5: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 18 19.01 +60 57 16.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,2461235.6540,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.09 23:04:27.13 +61:01:48.2
110.34033 0.80120 galactic Cep Second-epoch detections are separated by 6.3" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:04:27.13 +61:01:48.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:27.13 +61:01:48.2: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:27.13 +61:01:48.2: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.97 23:21:30.92 +62:54:45.9
112.89992 1.80576 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 | Gaia DR3 2016774289811311744 | 23:21:35.62 +62:54:36.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F8 1955IzKry..14....3B [B55b] 2403
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:30.92 +62:54:45.9: 15.78 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:30.92 +62:54:45.9: 15.94 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.78 +/- 0.30
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 21 30.92 +62 54 45.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
Gaia DR3 2016774289811311744,2461235.6540,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2016774289811311744 20260714.1540 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 07 14.1540 2461235.6540 14.15 23:03:46.58 +63:01:32.2
111.07016 2.66034 galactic Cep Second-epoch detections are separated by 4.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:03:46.58 +63:01:32.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:46.58 +63:01:32.2: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:46.58 +63:01:32.2: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.96 23:20:02.87 +59:12:28.3
111.46225 -1.61349 galactic Cas Second-epoch detections are separated by 2.1" 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:20:02.87 +59:12:28.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:20:02.87 +59:12:28.3: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:20:02.87 +59:12:28.3: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 20 02.87 +59 12 28.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,2461235.6540,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.97 23:28:43.33 +60:24:59.0
112.89069 -0.83273 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:28:43.33 +60:24:59.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:28:43.33 +60:24:59.0: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:28:43.33 +60:24:59.0: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 28 43.33 +60 24 59.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,2461235.6540,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.88 23:31:40.51 +61:01:06.9
113.42018 -0.37155 galactic Cas Second-epoch detections are separated by 5.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:31:40.51 +61:01:06.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:31:40.51 +61:01:06.9: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:31:40.51 +61:01:06.9: 15.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 31 40.51 +61 01 06.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.90 23:35:19.57 +61:06:50.7
113.87021 -0.41145 galactic Cas Second-epoch detections are separated by 3.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:35:19.57 +61:06:50.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:35:19.57 +61:06:50.7: 16.07 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:35:19.57 +61:06:50.7: 16.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 07 14.1540* 23 35 19.57 +61 06 50.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,2461235.6540,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.79 23:52:26.42 +63:10:05.8
116.33204 1.05502 galactic Cas Second-epoch detections are separated by 2.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 | target | 23:52:26.42 +63:10:05.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:52:26.42 +63:10:05.8: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:52:26.42 +63:10:05.8: 15.51 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.51 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 52 26.42 +63 10 05.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,2461235.6540,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.98 23:05:48.67 +64:40:34.1
111.93743 4.08334 galactic Cep Second-epoch detections are separated by 4.7" and 6.2 pix
The object was found in VSX23" ZTF J230552.28+644030.7
Type: EA
# Max. Min./Amp. JD0 Period
18.510 r Y 0.470 r 2458370.78790 0.696898000000
ATTENTION: measured mag 13.98 is 4.1 mag brighter than the VSX record maximum brightness 18.04 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:48.67 +64:40:34.1: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:48.67 +64:40:34.1: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J230552.28+644030.7,2461235.6540,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J230552.28+644030.7 20260714.1540 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:27:46.92 +60:55:56.4
112.94452 -0.30685 galactic Cas Second-epoch detections are separated by 5.7" 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:27:46.92 +60:55:56.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:27:46.92 +60:55:56.4: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:27:46.92 +60:55:56.4: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 27 46.92 +60 55 56.4 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.91 23:50:52.68 +60:43:30.3
115.59243 -1.28078 galactic Cas Second-epoch detections are separated by 2.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:50:52.68 +60:43:30.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:50:52.68 +60:43:30.3: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:50:52.68 +60:43:30.3: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 50 52.68 +60 43 30.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,2461235.6540,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.78 23:34:43.26 +60:59:52.1
113.76630 -0.50136 galactic Cas Second-epoch detections are separated by 5.2" 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:34:43.26 +60:59:52.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:34:43.26 +60:59:52.1: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:34:43.26 +60:59:52.1: 16.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 07 14.1540* 23 34 43.26 +60 59 52.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,2461235.6540,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.02 23:18:46.65 +63:31:48.6
112.82377 2.49169 galactic Cas Second-epoch detections are separated by 5.7" 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:18:46.65 +63:31:48.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:18:46.65 +63:31:48.6: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:18:46.65 +63:31:48.6: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 18 46.65 +63 31 48.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,2461235.6540,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.70 23:59:12.70 +64:48:34.5
117.40886 2.49936 galactic Cas Second-epoch detections are separated by 1.5" 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 | 23:59:12.70 +64:48:34.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:59:12.70 +64:48:34.5: 16.12 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:59:12.70 +64:48:34.5: 16.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 07 14.1540* 23 59 12.70 +64 48 34.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,2461235.6540,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.79 23:24:26.91 +60:12:31.9
112.32284 -0.85878 galactic Cas Second-epoch detections are separated by 5.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 | Gaia DR3 2012339757556735488 | 23:24:29.73 +60:12:30.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:24:26.91 +60:12:31.9: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:26.91 +60:12:31.9: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 24 26.91 +60 12 31.9 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012339757556735488,2461235.6540,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2012339757556735488 20260714.1540 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.79 23:28:50.07 +62:35:47.0
113.58818 1.23273 galactic Cas Second-epoch detections are separated by 5.8" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:28:50.07 +62:35:47.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:28:50.07 +62:35:47.0: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:28:50.07 +62:35:47.0: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 28 50.07 +62 35 47.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,2461235.6540,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:29:14.05 +61:01:26.4
113.14056 -0.27534 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:29:14.05 +61:01:26.4 (user input) | T | P | (position from user input) SpType: em 1975AbaOB..47....3D [D75b] Em* 23-042
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:29:14.05 +61:01:26.4: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:14.05 +61:01:26.4: 15.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 29 14.05 +61 01 26.4 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.68 00:01:54.00 +61:33:05.1
117.06741 -0.75499 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 | target | 00:01:54.00 +61:33:05.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:54.00 +61:33:05.1: 15.69 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:01:54.00 +61:33:05.1: 15.62 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.65 +/- 0.20
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 01 54.00 +61 33 05.1 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.79 23:25:54.71 +60:40:05.1
112.64365 -0.48387 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 | target | 23:25:54.71 +60:40:05.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:54.71 +60:40:05.1: 15.94 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:54.71 +60:40:05.1: 15.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 54.71 +60 40 05.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,2461235.6540,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.72 23:02:26.54 +61:09:11.4
110.16787 1.01195 galactic Cep Second-epoch detections are separated by 3.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:02:26.54 +61:09:11.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:02:26.54 +61:09:11.4: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:02:26.54 +61:09:11.4: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.91 23:05:17.91 +61:01:43.4
110.43377 0.75907 galactic Cep Second-epoch detections are separated by 2.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:05:17.91 +61:01:43.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:17.91 +61:01:43.4: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:17.91 +61:01:43.4: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.64 23:40:02.01 +63:26:39.6
115.05161 1.67035 galactic Cas Second-epoch detections are separated by 2.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:40:02.01 +63:26:39.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:40:02.01 +63:26:39.6: 16.12 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:40:02.01 +63:26:39.6: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 40 02.01 +63 26 39.6 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.71 23:10:13.53 +61:18:15.3
111.08825 0.78178 galactic Cep Second-epoch detections are separated by 3.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:10:13.53 +61:18:15.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:10:13.53 +61:18:15.3: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:10:13.53 +61:18:15.3: 15.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.61 23:25:05.95 +59:40:49.1
112.22606 -1.38475 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:25:05.95 +59:40:49.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:05.95 +59:40:49.1: 16.04 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:05.95 +59:40:49.1: 16.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 07 14.1540* 23 25 05.95 +59 40 49.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.57 23:35:45.33 +61:28:25.0
114.02360 -0.08222 galactic Cas Second-epoch detections are separated by 5.3" 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:35:45.33 +61:28:25.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:35:45.33 +61:28:25.0: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:35:45.33 +61:28:25.0: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 35 45.33 +61 28 25.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,2461235.6540,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.56 23:04:57.61 +57:15:14.2
108.89004 -2.68609 galactic Cas Second-epoch detections are separated by 7.2" and 6.6 pix
The object was found in VSX18" Gaia DR3 2009945708426172800
Type: RS
# Max. Min./Amp. JD0 Period
18.480 G 18.660 G
ATTENTION: measured mag 13.56 is 4.9 mag brighter than the VSX record maximum brightness 18.48 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:57.61 +57:15:14.2: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:57.61 +57:15:14.2: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 04 57.61 +57 15 14.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
Gaia DR3 2009945708426172800,2461235.6540,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2009945708426172800 20260714.1540 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 07 14.1540 2461235.6540 13.73 23:02:28.03 +60:46:00.3
110.01315 0.65785 galactic Cep Second-epoch detections are separated by 5.2" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:02:28.03 +60:46:00.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:02:28.03 +60:46:00.3: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:02:28.03 +60:46:00.3: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.74 23:35:46.39 +59:56:05.4
113.58154 -1.55615 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:35:46.39 +59:56:05.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:35:46.39 +59:56:05.4: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:35:46.39 +59:56:05.4: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 35 46.39 +59 56 05.4 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.52 23:25:23.63 +63:24:25.0
113.47780 2.12563 galactic Cas Second-epoch detections are separated by 5.4" 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:25:23.63 +63:24:25.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:23.63 +63:24:25.0: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:23.63 +63:24:25.0: 16.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 07 14.1540* 23 25 23.63 +63 24 25.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,2461235.6540,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.31 00:21:53.86 +61:32:10.3
119.41902 -1.13390 galactic Cas Second-epoch detections are separated by 3.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 | 00:21:53.86 +61:32:10.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:21:53.86 +61:32:10.3: 14.80 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:21:53.86 +61:32:10.3: 14.85 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.82 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 21 53.86 +61 32 10.3 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.68 23:13:11.08 +56:53:51.6
109.78558 -3.44508 galactic Cas Second-epoch detections are separated by 3.7" and 7.3 pix
The object was found in VSX25" Gaia DR3 2009457078578470912
Type: S
# Max. Min./Amp. JD0 Period
16.960 G 17.500 G B
ATTENTION: measured mag 13.68 is 3.3 mag brighter than the VSX record maximum brightness 16.96 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:11.08 +56:53:51.6: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:11.08 +56:53:51.6: 15.67 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.67 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 13 11.08 +56 53 51.6 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2009457078578470912,2461235.6540,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2009457078578470912 20260714.1540 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.60 23:04:17.98 +59:38:08.8
109.76419 -0.46863 galactic Cas Second-epoch detections are separated by 4.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:04:17.98 +59:38:08.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:17.98 +59:38:08.8: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:17.98 +59:38:08.8: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 04 17.98 +59 38 08.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.61 23:05:39.09 +59:18:22.8
109.79027 -0.83920 galactic Cas Second-epoch detections are separated by 6.4" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:05:39.09 +59:18:22.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:39.09 +59:18:22.8: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:39.09 +59:18:22.8: 15.59 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 05 39.09 +59 18 22.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.44 23:01:46.97 +60:35:18.6
109.86383 0.52939 galactic Cep Second-epoch detections are separated by 4.9" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:01:46.97 +60:35:18.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:46.97 +60:35:18.6: 14.69 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:46.97 +60:35:18.6: 14.54 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.61 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.47 00:05:04.37 +63:58:28.1
117.87217 1.55915 galactic Cas Second-epoch detections are separated by 2.7" and 6.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 431714994309244800 | 00:04:57.92 +63:58:33.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:04.37 +63:58:28.1: 15.33 +/- 0.24 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:05:04.37 +63:58:28.1: 14.81 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.95 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 05 04.37 +63 58 28.1 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431714994309244800,2461235.6540,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 431714994309244800 20260714.1540 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.53 23:11:02.90 +61:17:38.3
111.17578 0.73483 galactic Cep Second-epoch detections are separated by 3.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 | target | 23:11:02.90 +61:17:38.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:02.90 +61:17:38.3: 15.94 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:02.90 +61:17:38.3: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.47 23:36:56.22 +61:41:19.5
114.21991 0.08364 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:36:56.22 +61:41:19.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:36:56.22 +61:41:19.5: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:36:56.22 +61:41:19.5: 15.36 +/- 0.19 detection
Forced photometry reference-image weighted average: 15.36 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 36 56.22 +61 41 19.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.62 23:00:47.26 +58:49:15.8
109.02213 -1.02984 galactic Cas Second-epoch detections are separated by 4.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 | ATO J345.1848+58.8170 | 23:00:47.26 +58:49:15.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:00:47.26 +58:49:15.8: 14.97 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:00:47.26 +58:49:15.8: 14.72 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.81 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 00 47.26 +58 49 15.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 J345.1848+58.8170,2461235.6540,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J345.1848+58.8170 20260714.1540 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 07 14.1540 2461235.6540 13.46 23:11:54.98 +61:50:30.4
111.47754 1.20358 galactic Cep Second-epoch detections are separated by 3.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:11:54.98 +61:50:30.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:54.98 +61:50:30.4: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:54.98 +61:50:30.4: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.55 23:18:41.66 +63:02:16.1
112.64229 2.03385 galactic Cas Second-epoch detections are separated by 4.0" 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:18:41.66 +63:02:16.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:18:41.66 +63:02:16.1: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:18:41.66 +63:02:16.1: 16.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 07 14.1540* 23 18 41.66 +63 02 16.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.56 22:56:44.12 +61:32:18.3
109.70686 1.64759 galactic Cep Second-epoch detections are separated by 7.0" 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 | 22:56:44.12 +61:32:18.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 22:56:44.12 +61:32:18.3: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 22:56:44.12 +61:32:18.3: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.45 23:00:31.92 +58:53:47.4
109.02325 -0.94748 galactic Cas Second-epoch detections are separated by 6.7" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:00:31.92 +58:53:47.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:00:31.92 +58:53:47.4: 15.01 +/- 0.24 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:00:31.92 +58:53:47.4: 14.85 +/- 0.20 detection
Forced photometry reference-image weighted average: 14.91 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 00 31.92 +58 53 47.4 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.28 23:05:51.09 +59:09:57.1
109.75811 -0.97831 galactic Cas Second-epoch detections are separated by 6.2" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J346.4843+59.1661 | 23:05:51.09 +59:09:57.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:51.09 +59:09:57.1: 15.40 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:51.09 +59:09:57.1: 15.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 05 51.09 +59 09 57.1 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J346.4843+59.1661,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J346.4843+59.1661 20260714.1540 13.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 07 14.1540 2461235.6540 13.28 23:07:53.63 +58:08:43.7
109.60211 -2.02110 galactic Cas Second-epoch detections are separated by 6.7" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J346.9563+58.1445 | 23:07:53.63 +58:08:43.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:07:53.63 +58:08:43.7: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:07:53.63 +58:08:43.7: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 07 53.63 +58 08 43.7 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J346.9563+58.1445,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J346.9563+58.1445 20260714.1540 13.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 07 14.1540 2461235.6540 13.36 23:06:12.29 +58:59:20.5
109.72993 -1.15869 galactic Cas Second-epoch detections are separated by 3.4" and 7.0 pix
The object was found in VSX23" Gaia DR3 2013306846753485312
Type: S
# Max. Min./Amp. JD0 Period
16.600 G 17.120 G F
ATTENTION: measured mag 13.36 is 3.2 mag brighter than the VSX record maximum brightness 16.60 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:06:12.29 +58:59:20.5: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:06:12.29 +58:59:20.5: 15.53 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 06 12.29 +58 59 20.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2013306846753485312,2461235.6540,13.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2013306846753485312 20260714.1540 13.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.09 00:09:30.61 +62:33:39.9
118.12306 0.08146 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 | 00:09:30.61 +62:33:39.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:30.61 +62:33:39.9: 15.59 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:09:30.61 +62:33:39.9: 15.63 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 09 30.61 +62 33 39.9 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.28 23:04:51.92 +59:25:31.3
109.74572 -0.69016 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:04:51.92 +59:25:31.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:51.92 +59:25:31.3: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:51.92 +59:25:31.3: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 04 51.92 +59 25 31.3 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.28 23:21:47.23 +60:58:11.1
112.26951 -0.03243 galactic Cas Second-epoch detections are separated by 5.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 | target | 23:21:47.23 +60:58:11.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:47.23 +60:58:11.1: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:47.23 +60:58:11.1: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 21 47.23 +60 58 11.1 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.19 23:28:44.27 +57:14:04.1
111.89078 -3.85377 galactic Cas Second-epoch detections are separated by 4.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:28:44.27 +57:14:04.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:28:44.27 +57:14:04.1: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:28:44.27 +57:14:04.1: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 28 44.27 +57 14 04.1 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:47:19.80 +65:40:28.2
116.38860 3.62046 galactic Cas Second-epoch detections are separated by 4.0" and 6.8 pix
The object was found in VSX24" ZTF J234720.18+654051.8
Type: BY
# Max. Min./Amp. JD0 Period
16.913 r Y 0.063 r 2458378.89460 0.808485000000
ATTENTION: measured mag 13.21 is 3.6 mag brighter than the VSX record maximum brightness 16.85 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:47:19.80 +65:40:28.2: 16.11 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:47:19.80 +65:40:28.2: 16.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 07 14.1540* 23 47 19.80 +65 40 28.2 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
ZTF J234720.18+654051.8,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J234720.18+654051.8 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.26 23:07:12.81 +56:45:12.0
108.97401 -3.26720 galactic Cas Second-epoch detections are separated by 6.1" 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:07:12.81 +56:45:12.0 (user input) | T | P | (position from user input) SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:07:12.81 +56:45:12.0: 14.97 +/- 0.21 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:07:12.81 +56:45:12.0: 15.40 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.12 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 07 12.81 +56 45 12.0 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.05 00:50:31.33 +64:11:25.0
122.83222 1.31871 galactic Cas Second-epoch detections are separated by 2.6" and 8.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:50:31.33 +64:11:25.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:50:31.33 +64:11:25.0: 14.34 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:50:31.33 +64:11:25.0: 14.68 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.46 +/- 0.08
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 50 31.33 +64 11 25.0 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.32 23:21:17.94 +61:29:33.2
112.39214 0.47917 galactic Cas Second-epoch detections are separated by 5.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:21:17.94 +61:29:33.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:17.94 +61:29:33.2: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:17.94 +61:29:33.2: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 21 17.94 +61 29 33.2 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.32 22:59:35.70 +59:25:59.6
109.13717 -0.40942 galactic Cas Second-epoch detections are separated by 4.0" and 6.6 pix
The object was found in VSX 3" Gaia DR3 2013603611813965568
Type:
# Max. Min./Amp. JD0 Period
15.130 G 15.210 G F
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 22:59:35.70 +59:25:59.6: 15.69 +/- 0.36 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 22:59:35.70 +59:25:59.6: 15.68 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.69 +/- 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 07 14.1540* 22 59 35.70 +59 25 59.6 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2013603611813965568,2461235.6540,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2013603611813965568 20260714.1540 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.13 23:11:01.83 +58:31:23.1
110.12735 -1.83011 galactic Cas Second-epoch detections are separated by 4.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:11:01.83 +58:31:23.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:01.83 +58:31:23.1: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:01.83 +58:31:23.1: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 11 01.83 +58 31 23.1 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.27 23:05:35.39 +65:07:07.0
112.09212 4.49871 galactic Cep Second-epoch detections are separated by 0.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:05:35.39 +65:07:07.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:35.39 +65:07:07.0: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:35.39 +65:07:07.0: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.00 00:24:11.96 +61:50:06.3
119.72321 -0.86685 galactic Cas Second-epoch detections are separated by 1.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:24:11.96 +61:50:06.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:24:11.96 +61:50:06.3: 14.27 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:24:11.96 +61:50:06.3: 14.40 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.32 +/- 0.08
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 24 11.96 +61 50 06.3 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,2461235.6540,13.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.28 23:08:50.50 +59:39:19.1
110.29950 -0.67629 galactic Cas Second-epoch detections are separated by 4.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:08:50.50 +59:39:19.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:08:50.50 +59:39:19.1: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:08:50.50 +59:39:19.1: 15.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 08 50.50 +59 39 19.1 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.13 23:26:34.03 +61:18:56.1
112.92816 0.10318 galactic Cas Second-epoch detections are separated by 5.1" 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:26:34.03 +61:18:56.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:26:34.03 +61:18:56.1: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:26:34.03 +61:18:56.1: 15.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 07 14.1540* 23 26 34.03 +61 18 56.1 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.11 23:21:18.07 +57:14:06.9
110.93871 -3.52265 galactic Cas Second-epoch detections are separated by 4.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:21:18.07 +57:14:06.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:18.07 +57:14:06.9: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:18.07 +57:14:06.9: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 21 18.07 +57 14 06.9 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.29 22:55:47.27 +63:45:33.4
110.56266 3.70023 galactic Cep Second-epoch detections are separated by 4.4" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 22:55:47.27 +63:45:33.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 22:55:47.27 +63:45:33.4: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 22:55:47.27 +63:45:33.4: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.11 23:01:46.49 +58:21:55.9
108.95183 -1.49792 galactic Cas Second-epoch detections are separated by 5.3" and 6.9 pix
The object was found in VSX16" ZTF J230147.63+582142.6
Type: BY
# Max. Min./Amp. JD0 Period
16.520 r Y 0.048 r 2458354.81350 1.822313000000
ATTENTION: measured mag 13.11 is 3.4 mag brighter than the VSX record maximum brightness 16.47 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:46.49 +58:21:55.9: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:46.49 +58:21:55.9: 15.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 01 46.49 +58 21 55.9 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J230147.63+582142.6,2461235.6540,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J230147.63+582142.6 20260714.1540 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.82 00:34:15.48 +62:34:11.1
120.95480 -0.23603 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 | 00:34:15.48 +62:34:11.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:15.48 +62:34:11.1: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:34:15.48 +62:34:11.1: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 34 15.48 +62 34 11.1 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.99 23:13:42.62 +59:30:39.1
110.81597 -1.04224 galactic Cas Second-epoch detections are separated by 8.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 | ATO J348.4125+59.5144 | 23:13:42.62 +59:30:39.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:42.62 +59:30:39.1: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:42.62 +59:30:39.1: 15.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 07 14.1540* 23 13 42.62 +59 30 39.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
ATO J348.4125+59.5144,2461235.6540,12.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.4125+59.5144 20260714.1540 12.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 07 14.1540 2461235.6540 13.02 23:09:49.80 +59:48:09.8
110.47107 -0.58792 galactic Cep Second-epoch detections are separated by 3.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 | Gaia DR3 2013770286602124416 | 23:09:49.89 +59:47:42.3 (Gaia DR3) | BE/GCAS/S (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:09:49.80 +59:48:09.8: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:09:49.80 +59:48:09.8: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 2013770286602124416,2461235.6540,13.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2013770286602124416 20260714.1540 13.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.09 23:16:39.20 +62:20:15.4
112.17511 1.46198 galactic Cas Second-epoch detections are separated by 4.6" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:16:39.20 +62:20:15.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:16:39.20 +62:20:15.4: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:16:39.20 +62:20:15.4: 16.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 07 14.1540* 23 16 39.20 +62 20 15.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,2461235.6540,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.10 23:01:03.13 +60:41:20.9
109.82355 0.65795 galactic Cep Second-epoch detections are separated by 3.8" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:01:03.13 +60:41:20.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:03.13 +60:41:20.9: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:03.13 +60:41:20.9: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.97 23:11:56.93 +60:47:40.2
111.08901 0.23102 galactic Cep Second-epoch detections are separated by 3.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:11:56.93 +60:47:40.2 (user input) | T | P | (position from user input) J-Ks=0.838+/-0.087 (M)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:56.93 +60:47:40.2: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:56.93 +60:47:40.2: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.95 23:51:29.41 +66:17:25.5
116.94785 4.11764 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:51:29.41 +66:17:25.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:51:29.41 +66:17:25.5: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:51:29.41 +66:17:25.5: 16.12 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 51 29.41 +66 17 25.5 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,2461235.6540,12.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.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 07 14.1540 2461235.6540 12.93 23:25:07.96 +61:33:21.6
112.84404 0.38625 galactic Cas Second-epoch detections are separated by 3.7" and 6.8 pix
The object was found in VSX 9" Gaia DR3 2015656709261454976
Type:
# Max. Min./Amp. JD0 Period
16.470 G 17.420 G
ATTENTION: measured mag 12.93 is 3.5 mag brighter than the VSX record maximum brightness 16.47 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:07.96 +61:33:21.6: 15.24 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:07.96 +61:33:21.6: 15.23 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 07.96 +61 33 21.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
Gaia DR3 2015656709261454976,2461235.6540,12.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2015656709261454976 20260714.1540 12.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 07 14.1540 2461235.6540 12.98 23:10:01.64 +61:30:39.1
111.14500 0.98185 galactic Cep Second-epoch detections are separated by 3.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:10:01.64 +61:30:39.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:10:01.64 +61:30:39.1: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:10:01.64 +61:30:39.1: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.80 23:37:56.85 +57:20:48.0
113.11472 -4.11763 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:37:56.85 +57:20:48.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:37:56.85 +57:20:48.0: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:37:56.85 +57:20:48.0: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 37 56.85 +57 20 48.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.88 23:13:24.20 +57:52:02.7
110.17238 -2.55510 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:13:24.20 +57:52:02.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:24.20 +57:52:02.7: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:24.20 +57:52:02.7: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 13 24.20 +57 52 02.7 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,2461235.6540,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.93 23:04:18.78 +59:42:36.4
109.79555 -0.40121 galactic Cas Second-epoch detections are separated by 4.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:04:18.78 +59:42:36.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:18.78 +59:42:36.4: 15.65 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:18.78 +59:42:36.4: 15.65 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 04 18.78 +59 42 36.4 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.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 07 14.1540 2461235.6540 12.62 00:01:34.47 +61:37:17.0
117.04281 -0.67890 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 | Gaia DR3 429517315392831104 | 00:01:31.68 +61:37:18.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:34.47 +61:37:17.0: 15.15 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:01:34.47 +61:37:17.0: 15.72 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.30 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 01 34.47 +61 37 17.0 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429517315392831104,2461235.6540,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 429517315392831104 20260714.1540 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.74 23:05:45.82 +60:42:39.7
110.35967 0.44500 galactic Cep Second-epoch detections are separated by 3.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:05:45.82 +60:42:39.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:45.82 +60:42:39.7: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:45.82 +60:42:39.7: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.56 23:16:28.54 +57:51:00.6
110.54707 -2.71996 galactic Cas Second-epoch detections are separated by 2.9" and 6.9 pix
The object was found in VSX17" Gaia DR3 2009583178825790336
Type: ROT
# Max. Min./Amp. JD0 Period
14.920 G 14.960 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:16:28.54 +57:51:00.6: 14.87 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:16:28.54 +57:51:00.6: 14.88 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.88 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 16 28.54 +57 51 00.6 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2009583178825790336,2461235.6540,12.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2009583178825790336 20260714.1540 12.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.48 23:07:47.86 +58:52:02.4
109.87138 -1.35117 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:07:47.86 +58:52:02.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:07:47.86 +58:52:02.4: 15.50 +/- 0.35 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:07:47.86 +58:52:02.4: 15.42 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.50 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 07 47.86 +58 52 02.4 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.47 23:57:24.41 +61:22:12.3
116.50532 -0.82566 galactic Cas Second-epoch detections are separated by 8.6" and 7.2 pix
The object was found in VSX 8" Gaia DR3 2011950839683607424
Type: ROT
# Max. Min./Amp. JD0 Period
16.030 G 16.080 G K
ATTENTION: measured mag 12.47 is 3.6 mag brighter than the VSX record maximum brightness 16.03 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:24.41 +61:22:12.3: 13.75 +/- 0.05 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:24.41 +61:22:12.3: 13.86 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.80 +/- 0.04
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 57 24.41 +61 22 12.3 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2011950839683607424,2461235.6540,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2011950839683607424 20260714.1540 12.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.28 23:23:35.45 +60:08:13.9
112.19846 -0.89106 galactic Cas Second-epoch detections are separated by 6.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:23:35.45 +60:08:13.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:23:35.45 +60:08:13.9: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:23:35.45 +60:08:13.9: 15.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 23 35.45 +60 08 13.9 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.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 07 14.1540 2461235.6540 12.19 23:16:21.30 +59:47:18.8
111.22819 -0.90497 galactic Cas Second-epoch detections are separated by 6.2" 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 J349.0988+59.7768 | 23:16:21.30 +59:47:18.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:16:21.30 +59:47:18.8: 15.58 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:16:21.30 +59:47:18.8: 15.63 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 16 21.30 +59 47 18.8 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J349.0988+59.7768,2461235.6540,12.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.0988+59.7768 20260714.1540 12.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.04 23:25:06.86 +61:36:46.8
112.86064 0.44082 galactic Cas Second-epoch detections are separated by 3.1" 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:25:06.86 +61:36:46.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:06.86 +61:36:46.8: 14.17 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:06.86 +61:36:46.8: 14.01 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.09 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 06.86 +61 36 46.8 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.08 23:03:47.92 +59:20:56.8
109.59074 -0.70556 galactic Cas Second-epoch detections are separated by 4.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 | ATO J345.9531+59.3614 | 23:03:47.92 +59:20:56.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:47.92 +59:20:56.8: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:47.92 +59:20:56.8: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 03 47.92 +59 20 56.8 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J345.9531+59.3614,2461235.6540,12.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J345.9531+59.3614 20260714.1540 12.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.02 23:02:42.31 +59:03:08.8
109.34264 -0.92019 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 | target | 23:02:42.31 +59:03:08.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:02:42.31 +59:03:08.8: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:02:42.31 +59:03:08.8: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 02 42.31 +59 03 08.8 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.82 23:06:41.98 +59:06:53.3
109.83795 -1.06811 galactic Cas Second-epoch detections are separated by 6.1" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J346.6645+59.1036 | 23:06:41.98 +59:06:53.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:06:41.98 +59:06:53.3: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:06:41.98 +59:06:53.3: 15.52 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.52 +/- 0.33
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 06 41.98 +59 06 53.3 11.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J346.6645+59.1036,2461235.6540,11.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J346.6645+59.1036 20260714.1540 11.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.78 23:08:00.76 +61:02:02.5
110.73809 0.63483 galactic Cep Second-epoch detections are separated by 3.6" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:08:00.76 +61:02:02.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:08:00.76 +61:02:02.5: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:08:00.76 +61:02:02.5: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 10.99 23:25:32.63 +61:34:52.9
112.89858 0.39424 galactic Cas Second-epoch detections are separated by 3.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:25:32.63 +61:34:52.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:32.63 +61:34:52.9: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:32.63 +61:34:52.9: 15.63 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 32.63 +61 34 52.9 11.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,10.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 10.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 07 14.1540 2461235.6540 11.15 00:33:09.08 +62:53:16.1
120.85021 0.08999 galactic Cas 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 | target | 00:33:09.08 +62:53:16.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:33:09.08 +62:53:16.1: 15.17 +/- 0.25 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:33:09.08 +62:53:16.1: 15.45 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.26 +/- 0.20
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 33 09.08 +62 53 16.1 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.67 23:25:37.74 +61:35:07.5
112.90948 0.39477 galactic Cas Second-epoch detections are separated by 3.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:25:37.74 +61:35:07.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:37.74 +61:35:07.5: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:37.74 +61:35:07.5: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 37.74 +61 35 07.5 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,2461235.6540,11.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.39 00:56:26.90 +60:47:12.3
123.54363 -2.07905 galactic Cas Second-epoch detections are separated by 5.7" and 7.9 pix
The object was found in VSX11" V0867 Cas
Type: M
# Max. Min./Amp. JD0 Period
12.800 V < 18.000 V 2457986.00000 412.000000000000 M6-M7e
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:56:26.90 +60:47:12.3: 15.36 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:56:26.90 +60:47:12.3: 15.41 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 56 26.90 +60 47 12.3 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
V0867 Cas,2461235.6540,11.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0867 Cas 20260714.1540 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 07 14.1540 2461235.6540 11.94 23:11:18.29 +58:26:37.1
110.13058 -1.91721 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 | target | 23:11:18.29 +58:26:37.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:18.29 +58:26:37.1: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:18.29 +58:26:37.1: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 11 18.29 +58 26 37.1 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.02 00:20:26.06 +61:51:27.2
119.28442 -0.79443 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:20:26.06 +61:51:27.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:20:26.06 +61:51:27.2: 15.51 +/- 0.27 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:20:26.06 +61:51:27.2: 15.44 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.48 +/- 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 07 14.1540* 00 20 26.06 +61 51 27.2 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.35 23:25:20.59 +61:35:47.5
112.88096 0.41636 galactic Cas Second-epoch detections are separated by 3.2" and 6.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015657117274606592 | 23:25:23.97 +61:35:53.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A3: 1935BSD...C01....0S BSD 19-1851
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:20.59 +61:35:47.5: 13.61 +/- 0.06 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:20.59 +61:35:47.5: 13.46 +/- 0.05 detection
Forced photometry reference-image weighted average: 13.52 +/- 0.04
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 20.59 +61 35 47.5 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015657117274606592,2461235.6540,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2015657117274606592 20260714.1540 12.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 07 14.1540 2461235.6540 12.38 23:13:46.29 +57:12:01.7
109.97194 -3.19320 galactic Cas Second-epoch detections are separated by 3.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 | Gaia DR3 2009481473997910784 | 23:13:46.22 +57:11:23.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:46.29 +57:12:01.7: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:46.29 +57:12:01.7: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 13 46.29 +57 12 01.7 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2009481473997910784,2461235.6540,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2009481473997910784 20260714.1540 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.62 23:25:05.93 +61:36:17.0
112.85618 0.43360 galactic Cas Second-epoch detections are separated by 3.7" and 6.8 pix
The object was found in VSX13" ZTF J232507.68+613615.8
Type: BY
# Max. Min./Amp. JD0 Period
17.549 r Y 0.082 r 2458386.77500 0.599400400000
ATTENTION: measured mag 12.62 is 4.8 mag brighter than the VSX record maximum brightness 17.47 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:05.93 +61:36:17.0: 14.04 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:05.93 +61:36:17.0: 13.92 +/- 0.13 detection
Forced photometry reference-image weighted average: 13.98 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 05.93 +61 36 17.0 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J232507.68+613615.8,2461235.6540,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J232507.68+613615.8 20260714.1540 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.62 23:25:03.81 +61:34:50.3
112.84433 0.41222 galactic Cas Second-epoch detections are separated by 6.1" and 7.5 pix
The object was found in VSX19" ZTF J232506.21+613458.8
Type: BY
# Max. Min./Amp. JD0 Period
17.622 r Y 0.071 r 2458257.95400 4.130846400000
ATTENTION: measured mag 12.62 is 4.9 mag brighter than the VSX record maximum brightness 17.55 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:03.81 +61:34:50.3: 14.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:03.81 +61:34:50.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 07 14.1540* 23 25 03.81 +61 34 50.3 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J232506.21+613458.8,2461235.6540,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J232506.21+613458.8 20260714.1540 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.62 23:31:36.46 +61:01:45.3
113.41563 -0.35891 galactic Cas Second-epoch detections are separated by 4.5" and 6.7 pix
The object was found in VSX18" ZTF J233134.12+610150.5
Type: EW
# Max. Min./Amp. JD0 Period
17.970 r Y 0.135 r 2458249.97690 0.819536600000
ATTENTION: measured mag 12.62 is 5.2 mag brighter than the VSX record maximum brightness 17.83 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:31:36.46 +61:01:45.3: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:31:36.46 +61:01:45.3: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 31 36.46 +61 01 45.3 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J233134.12+610150.5,2461235.6540,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J233134.12+610150.5 20260714.1540 12.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.64 23:25:46.25 +61:34:26.0
112.92169 0.37838 galactic Cas Second-epoch detections are separated by 3.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:25:46.25 +61:34:26.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:46.25 +61:34:26.0: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:46.25 +61:34:26.0: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 46.25 +61 34 26.0 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.49 23:42:16.71 +57:16:44.2
113.66018 -4.34256 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 | ATO J355.5616+57.2686 | 23:42:18.06 +57:16:19.2 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:42:16.71 +57:16:44.2: 14.34 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:16.71 +57:16:44.2: 14.53 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.42 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 42 16.71 +57 16 44.2 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.5616+57.2686,2461235.6540,12.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.5616+57.2686 20260714.1540 12.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.44 01:10:28.12 +64:11:40.8
125.00170 1.39942 galactic Cas Second-epoch detections are separated by 5.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 | Gaia DR3 523451857922272128 | 01:10:28.37 +64:11:34.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 01:10:28.12 +64:11:40.8: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 01:10:28.12 +64:11:40.8: 15.39 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.39 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 01 10 28.12 +64 11 40.8 12.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 523451857922272128,2461235.6540,12.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 523451857922272128 20260714.1540 12.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.54 23:57:37.86 +61:02:13.5
116.46263 -1.15701 galactic Cas Second-epoch detections are separated by 3.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:57:37.86 +61:02:13.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:37.86 +61:02:13.5: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:37.86 +61:02:13.5: 15.66 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 57 37.86 +61 02 13.5 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.69 00:41:31.53 +65:48:40.9
121.91544 2.95918 galactic Cas Second-epoch detections are separated by 2.5" and 7.4 pix
The object was found in VSX12" Gaia DR3 527536406179372288
Type: RS
# Max. Min./Amp. JD0 Period
16.560 G 16.650 G
ATTENTION: measured mag 12.69 is 3.9 mag brighter than the VSX record maximum brightness 16.56 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:41:31.53 +65:48:40.9: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:41:31.53 +65:48:40.9: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 41 31.53 +65 48 40.9 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 527536406179372288,2461235.6540,12.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 527536406179372288 20260714.1540 12.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.90 23:24:06.13 +61:58:40.5
112.86784 0.82477 galactic Cas Second-epoch detections are separated by 4.8" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015734220530247296 | 23:24:07.72 +61:58:56.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:24:06.13 +61:58:40.5: 15.34 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:06.13 +61:58:40.5: 15.96 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.34 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 24 06.13 +61 58 40.5 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015734220530247296,2461235.6540,12.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2015734220530247296 20260714.1540 12.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.75 23:53:14.48 +61:56:10.0
116.14462 -0.16631 galactic Cas Second-epoch detections are separated by 2.1" and 6.9 pix
The object was found in VSX11" Gaia DR3 2012771620815152512
Type:
# Max. Min./Amp. JD0 Period
17.620 G 17.760 G
ATTENTION: measured mag 12.75 is 4.9 mag brighter than the VSX record maximum brightness 17.62 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:53:14.48 +61:56:10.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:53:14.48 +61:56:10.0: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 53 14.48 +61 56 10.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012771620815152512,2461235.6540,12.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2012771620815152512 20260714.1540 12.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.93 23:13:03.38 +57:07:09.4
109.85164 -3.23279 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 | target | 23:13:03.38 +57:07:09.4 (user input) | T | P | (position from user input) SpType: G3 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:03.38 +57:07:09.4: 14.58 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:03.38 +57:07:09.4: 14.81 +/- 0.18 detection
Forced photometry reference-image weighted average: 14.67 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 13 03.38 +57 07 09.4 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.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 07 14.1540 2461235.6540 13.08 23:05:07.28 +60:05:42.6
110.04232 -0.08873 galactic Cep Second-epoch detections are separated by 4.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 | ATO J346.2638+60.0944 | 23:05:07.28 +60:05:42.6 (user input) | NSINE (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:07.28 +60:05:42.6: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:07.28 +60:05:42.6: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J346.2638+60.0944,2461235.6540,13.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J346.2638+60.0944 20260714.1540 13.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.04 23:17:12.73 +64:44:37.7
113.09340 3.68733 galactic Cep Second-epoch detections are separated by 3.4" 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:17:12.73 +64:44:37.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:17:12.73 +64:44:37.7: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:17:12.73 +64:44:37.7: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.00 23:21:06.09 +65:26:40.2
113.72347 4.20066 galactic Cep Second-epoch detections are separated by 3.3" 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:21:06.09 +65:26:40.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:06.09 +65:26:40.2: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:06.09 +65:26:40.2: 15.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.96 00:16:34.64 +65:57:06.0
119.38590 3.32022 galactic Cas Second-epoch detections are separated by 2.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 | 00:16:34.64 +65:57:06.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:34.64 +65:57:06.0: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:16:34.64 +65:57:06.0: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 16 34.64 +65 57 06.0 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.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 07 14.1540 2461235.6540 13.07 23:26:22.97 +60:42:16.0
112.70996 -0.46812 galactic Cas Second-epoch detections are separated by 5.3" and 6.7 pix
The object was found in VSX11" ZTF J232623.44+604226.2
Type: EW
# Max. Min./Amp. JD0 Period
17.414 r Y 0.459 r 2458441.78480 0.354356800000
ATTENTION: measured mag 13.07 is 3.9 mag brighter than the VSX record maximum brightness 16.96 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:26:22.97 +60:42:16.0: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:26:22.97 +60:42:16.0: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 26 22.97 +60 42 16.0 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J232623.44+604226.2,2461235.6540,13.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J232623.44+604226.2 20260714.1540 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 07 14.1540 2461235.6540 13.12 23:03:43.23 +59:32:32.8
109.65955 -0.52461 galactic Cas Second-epoch detections are separated by 5.6" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J345.9276+59.5413 | 23:03:43.23 +59:32:32.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:43.23 +59:32:32.8: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:43.23 +59:32:32.8: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 03 43.23 +59 32 32.8 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J345.9276+59.5413,2461235.6540,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J345.9276+59.5413 20260714.1540 13.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.19 22:57:14.98 +62:15:45.2
110.07065 2.27676 galactic Cep Second-epoch detections are separated by 5.5" and 6.4 pix
The object was found in VSX 7" Gaia DR3 2207009837435816448
Type: E
# Max. Min./Amp. JD0 Period
19.040 G 19.330 G 0.270229000000
ATTENTION: measured mag 13.19 is 5.8 mag brighter than the VSX record maximum brightness 19.04 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 22:57:14.98 +62:15:45.2: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 22:57:14.98 +62:15:45.2: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 2207009837435816448,2461235.6540,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2207009837435816448 20260714.1540 13.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.28 23:04:37.70 +59:50:33.7
109.88501 -0.29561 galactic Cep Second-epoch detections are separated by 3.7" 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:04:37.70 +59:50:33.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:37.70 +59:50:33.7: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:37.70 +59:50:33.7: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.29 23:21:57.66 +62:00:09.7
112.63924 0.93230 galactic Cas Second-epoch detections are separated by 3.3" 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:21:57.66 +62:00:09.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:57.66 +62:00:09.7: 16.06 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:57.66 +62:00:09.7: 16.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 07 14.1540* 23 21 57.66 +62 00 09.7 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.20 23:41:29.65 +61:42:37.5
114.74505 -0.04452 galactic Cas Second-epoch detections are separated by 3.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:41:29.65 +61:42:37.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:41:29.65 +61:42:37.5: 15.32 +/- 0.17 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:41:29.65 +61:42:37.5: 15.71 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.45 +/- 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 07 14.1540* 23 41 29.65 +61 42 37.5 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:29:41.09 +60:54:36.5
113.15703 -0.40057 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 | target | 23:29:41.09 +60:54:36.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:29:41.09 +60:54:36.5: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:41.09 +60:54:36.5: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 29 41.09 +60 54 36.5 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:13:08.83 +57:06:05.8
109.85655 -3.25377 galactic Cas 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:13:08.83 +57:06:05.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:13:08.83 +57:06:05.8: 15.65 +/- 0.34 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:13:08.83 +57:06:05.8: 15.72 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.65 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 13 08.83 +57 06 05.8 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:38:48.35 +60:51:21.1
114.20155 -0.77879 galactic Cas Second-epoch detections are separated by 4.3" 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:38:48.35 +60:51:21.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:48.35 +60:51:21.1: 16.11 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:48.35 +60:51:21.1: 16.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 07 14.1540* 23 38 48.35 +60 51 21.1 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:24:27.62 +60:27:27.4
112.40626 -0.62442 galactic Cas Second-epoch detections are separated by 4.9" and 7.0 pix
The object was found in VSX15" Gaia DR3 2012358517973814144
Type: ROT
# Max. Min./Amp. JD0 Period
13.710 G 13.740 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:24:27.62 +60:27:27.4: 16.01 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:27.62 +60:27:27.4: 15.93 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.93 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 24 27.62 +60 27 27.4 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012358517973814144,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2012358517973814144 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.13 23:38:46.52 +58:40:51.5
113.59384 -2.86715 galactic Cas Second-epoch detections are separated by 4.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:38:46.52 +58:40:51.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:46.52 +58:40:51.5: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:46.52 +58:40:51.5: 16.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 07 14.1540* 23 38 46.52 +58 40 51.5 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.23 23:11:14.02 +57:02:22.5
109.59176 -3.21402 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:11:14.02 +57:02:22.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:14.02 +57:02:22.5: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:14.02 +57:02:22.5: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 11 14.02 +57 02 22.5 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.28 23:03:50.10 +59:35:19.9
109.69153 -0.48797 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:03:50.10 +59:35:19.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:50.10 +59:35:19.9: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:50.10 +59:35:19.9: 15.73 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 03 50.10 +59 35 19.9 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.27 23:50:57.25 +60:53:51.4
115.64156 -1.11513 galactic Cas Second-epoch detections are separated by 1.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 | 23:50:57.25 +60:53:51.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:50:57.25 +60:53:51.4: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:50:57.25 +60:53:51.4: 15.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 07 14.1540* 23 50 57.25 +60 53 51.4 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.24 00:57:49.79 +65:21:33.5
123.59872 2.49583 galactic Cas Second-epoch detections are separated by 2.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:57:49.79 +65:21:33.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:57:49.79 +65:21:33.5: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:57:49.79 +65:21:33.5: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 57 49.79 +65 21 33.5 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.21 23:46:27.00 +61:57:35.4
115.37441 0.04542 galactic Cas Second-epoch detections are separated by 2.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 | Gaia DR3 2012886386639288320 | 23:46:28.65 +61:57:32.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:46:27.00 +61:57:35.4: 15.64 +/- 0.25 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:46:27.00 +61:57:35.4: 15.98 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.75 +/- 0.20
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 46 27.00 +61 57 35.4 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2012886386639288320,2461235.6540,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2012886386639288320 20260714.1540 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.96 00:51:42.51 +56:29:57.2
122.96949 -6.37251 galactic Cas Second-epoch detections are separated by 1.9" and 7.9 pix
The object was found in VSX21" Gaia DR3 423839987098568192
Type: ROT
# Max. Min./Amp. JD0 Period
14.750 G 14.810 G M
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:51:42.51 +56:29:57.2: 14.54 +/- 0.13 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:51:42.51 +56:29:57.2: 14.36 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.44 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 51 42.51 +56 29 57.2 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
Gaia DR3 423839987098568192,2461235.6540,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 423839987098568192 20260714.1540 12.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 07 14.1540 2461235.6540 13.25 23:33:01.34 +57:54:14.4
112.64452 -3.39298 galactic Cas Second-epoch detections are separated by 2.6" and 7.5 pix
The object was found in VSX12" Gaia DR3 1998890222088030720
Type: VAR
# Max. Min./Amp. JD0 Period
18.020 G 18.100 G 0.020468600000
ATTENTION: measured mag 13.25 is 4.8 mag brighter than the VSX record maximum brightness 18.02 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:01.34 +57:54:14.4: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:01.34 +57:54:14.4: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 33 01.34 +57 54 14.4 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998890222088030720,2461235.6540,13.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1998890222088030720 20260714.1540 13.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.35 23:17:51.79 +60:54:28.6
111.80109 0.07463 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:17:51.79 +60:54:28.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:17:51.79 +60:54:28.6: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:17:51.79 +60:54:28.6: 15.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 17 51.79 +60 54 28.6 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.36 23:10:37.62 +56:52:28.8
109.45256 -3.33536 galactic Cas Second-epoch detections are separated by 7.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:10:37.62 +56:52:28.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:10:37.62 +56:52:28.8: 14.65 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:10:37.62 +56:52:28.8: 14.85 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.73 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 10 37.62 +56 52 28.8 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,2461235.6540,13.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.19 23:58:59.23 +60:16:00.3
116.46772 -1.94505 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 | 23:58:59.23 +60:16:00.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:58:59.23 +60:16:00.3: 15.94 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:58:59.23 +60:16:00.3: 15.41 +/- 0.23 detection
Forced photometry reference-image weighted average: 15.41 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 58 59.23 +60 16 00.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
target,2461235.6540,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.24 00:01:20.81 +62:01:48.5
117.09514 -0.27262 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 | 00:01:20.81 +62:01:48.5 (user input) | T | P | (position from user input) J-Ks=0.889+/-0.032 (M)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:20.81 +62:01:48.5: 15.25 +/- 0.23 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:01:20.81 +62:01:48.5: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.25 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 01 20.81 +62 01 48.5 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.38 23:30:41.64 +57:58:12.5
112.36969 -3.23621 galactic Cas Second-epoch detections are separated by 4.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 2010886512420316928 | 23:30:42.71 +57:57:54.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:30:41.64 +57:58:12.5: 15.32 +/- 0.23 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:30:41.64 +57:58:12.5: 15.58 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.42 +/- 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 07 14.1540* 23 30 41.64 +57 58 12.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2010886512420316928,2461235.6540,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2010886512420316928 20260714.1540 13.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.18 01:03:05.02 +61:47:29.7
124.30787 -1.04905 galactic Cas Second-epoch detections are separated by 1.8" 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 | 01:03:05.02 +61:47:29.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 01:03:05.02 +61:47:29.7: 14.49 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 01:03:05.02 +61:47:29.7: 14.55 +/- 0.18 detection
Forced photometry reference-image weighted average: 14.51 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 01 03 05.02 +61 47 29.7 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.37 23:49:00.73 +61:15:08.9
115.49703 -0.71490 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:49:00.73 +61:15:08.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:49:00.73 +61:15:08.9: 16.07 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:00.73 +61:15:08.9: 16.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 07 14.1540* 23 49 00.73 +61 15 08.9 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.64 23:01:51.50 +63:11:35.4
110.94002 2.90160 galactic Cep Second-epoch detections are separated by 7.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:01:51.50 +63:11:35.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:51.50 +63:11:35.4: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:51.50 +63:11:35.4: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.53 23:30:16.44 +61:22:28.4
113.36846 0.01899 galactic Cas Second-epoch detections are separated by 5.1" 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:30:16.44 +61:22:28.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:30:16.44 +61:22:28.4: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:30:16.44 +61:22:28.4: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 30 16.44 +61 22 28.4 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.52 23:07:25.09 +59:13:15.3
109.96422 -1.00652 galactic Cas Second-epoch detections are separated by 3.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 | ATO J346.8403+59.2208 | 23:07:23.20 +59:13:33.5 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:07:25.09 +59:13:15.3: 15.42 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:07:25.09 +59:13:15.3: 14.76 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.90 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 07 25.09 +59 13 15.3 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J346.8403+59.2208,2461235.6540,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J346.8403+59.2208 20260714.1540 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.39 00:09:07.10 +65:00:38.3
118.47906 2.50541 galactic Cas Second-epoch detections are separated by 4.6" 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 | 00:09:07.10 +65:00:38.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:07.10 +65:00:38.3: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:09:07.10 +65:00:38.3: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 09 07.10 +65 00 38.3 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,2461235.6540,13.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.55 23:01:05.08 +59:37:26.5
109.38816 -0.31412 galactic Cas Second-epoch detections are separated by 4.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 | Gaia DR3 2013614916167854592 | 23:01:06.01 +59:37:22.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F5 1955IzKry..14....3B [B55b] 684
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:05.08 +59:37:26.5: 15.43 +/- 0.26 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:05.08 +59:37:26.5: 14.93 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.07 +/- 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 07 14.1540* 23 01 05.08 +59 37 26.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
Gaia DR3 2013614916167854592,2461235.6540,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2013614916167854592 20260714.1540 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.44 23:43:11.82 +61:32:34.8
114.89592 -0.25945 galactic Cas Second-epoch detections are separated by 4.2" 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:43:11.82 +61:32:34.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:43:11.82 +61:32:34.8: 15.56 +/- 0.26 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:43:11.82 +61:32:34.8: 15.83 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.66 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 43 11.82 +61 32 34.8 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,2461235.6540,13.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.46 00:12:34.35 +62:51:26.1
118.51601 0.31921 galactic Cas Second-epoch detections are separated by 2.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 | 00:12:34.35 +62:51:26.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:12:34.35 +62:51:26.1: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:12:34.35 +62:51:26.1: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 12 34.35 +62 51 26.1 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,2461235.6540,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.43 00:48:12.34 +65:04:57.0
122.59123 2.21289 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 | Gaia DR3 524449321128361984 | 00:48:11.71 +65:05:38.3 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:48:12.34 +65:04:57.0: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:48:12.34 +65:04:57.0: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 48 12.34 +65 04 57.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
Gaia DR3 524449321128361984,2461235.6540,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 524449321128361984 20260714.1540 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.62 23:32:06.18 +63:58:06.4
114.36079 2.42484 galactic Cep Second-epoch detections are separated by 3.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:32:06.18 +63:58:06.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:32:06.18 +63:58:06.4: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:32:06.18 +63:58:06.4: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.37 23:38:06.23 +57:31:45.0
113.18636 -3.94839 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:38:06.23 +57:31:45.0 (user input) | T | P | (position from user input) SpType: F7 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:06.23 +57:31:45.0: 14.58 +/- 0.11 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:06.23 +57:31:45.0: 14.38 +/- 0.09 detection
Forced photometry reference-image weighted average: 14.47 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 38 06.23 +57 31 45.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,2461235.6540,13.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.57 23:40:00.41 +61:29:05.2
114.51380 -0.21398 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:40:00.41 +61:29:05.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:40:00.41 +61:29:05.2: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:40:00.41 +61:29:05.2: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 40 00.41 +61 29 05.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,2461235.6540,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.51 00:40:39.59 +64:16:00.3
121.76200 1.41949 galactic Cas Second-epoch detections are separated by 1.8" 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:40:39.59 +64:16:00.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:40:39.59 +64:16:00.3: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:40:39.59 +64:16:00.3: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 40 39.59 +64 16 00.3 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.55 23:43:41.78 +62:53:07.2
115.30138 1.02151 galactic Cas Second-epoch detections are separated by 3.8" and 6.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:41.78 +62:53:07.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:43:41.78 +62:53:07.2: 16.07 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:43:41.78 +62:53:07.2: 16.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 07 14.1540* 23 43 41.78 +62 53 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
target,2461235.6540,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.61 23:04:17.49 +57:38:50.6
108.96519 -2.28954 galactic Cas Second-epoch detections are separated by 5.4" 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:04:17.49 +57:38:50.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:17.49 +57:38:50.6: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:17.49 +57:38:50.6: 15.73 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 04 17.49 +57 38 50.6 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.54 23:46:13.79 +61:56:50.2
115.34622 0.03972 galactic Cas Second-epoch detections are separated by 1.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 | 23:46:13.79 +61:56:50.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:46:13.79 +61:56:50.2: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:46:13.79 +61:56:50.2: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 46 13.79 +61 56 50.2 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,2461235.6540,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.63 23:49:11.86 +64:50:04.0
116.37438 2.75809 galactic Cas Second-epoch detections are separated by 3.5" and 7.0 pix
The object was found in VSX19" V0406 Cas
Type: EB/AR
# Max. Min./Amp. JD0 Period
16.200 pg 17.100 pg 2434623.39100 2.132420000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:49:11.86 +64:50:04.0: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:11.86 +64:50:04.0: 16.12 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 49 11.86 +64 50 04.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
V0406 Cas,2461235.6540,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0406 Cas 20260714.1540 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.52 23:59:19.88 +66:44:15.6
117.80956 4.38554 galactic Cep 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 | target | 23:59:19.88 +66:44:15.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:59:19.88 +66:44:15.6: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:59:19.88 +66:44:15.6: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.45 23:33:18.36 +59:56:49.4
113.28965 -1.45390 galactic Cas Second-epoch detections are separated by 3.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:33:18.36 +59:56:49.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:18.36 +59:56:49.4: 16.09 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:18.36 +59:56:49.4: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 33 18.36 +59 56 49.4 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.41 23:42:21.74 +57:16:34.1
113.67039 -4.34827 galactic Cas Second-epoch detections are separated by 3.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 J355.5616+57.2686 | 23:42:18.06 +57:16:19.2 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:42:21.74 +57:16:34.1: 14.26 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:21.74 +57:16:34.1: 14.56 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.37 +/- 0.08
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 42 21.74 +57 16 34.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
ATO J355.5616+57.2686,2461235.6540,13.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.5616+57.2686 20260714.1540 13.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.66 23:03:21.21 +59:50:13.2
109.73611 -0.23643 galactic Cep Second-epoch detections are separated by 5.4" 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:03:21.21 +59:50:13.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:21.21 +59:50:13.2: 15.56 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:21.21 +59:50:13.2: 15.58 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.46 23:57:08.33 +61:22:33.8
116.47517 -0.81313 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:57:08.33 +61:22:33.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:08.33 +61:22:33.8: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:08.33 +61:22:33.8: 15.64 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 57 08.33 +61 22 33.8 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.70 23:12:34.73 +62:50:28.9
111.92233 2.10214 galactic Cep Second-epoch detections are separated by 7.3" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:12:34.73 +62:50:28.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:12:34.73 +62:50:28.9: 15.76 +/- 0.31 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:12:34.73 +62:50:28.9: 15.66 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.71 +/- 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.59 23:33:18.33 +57:37:18.7
112.59621 -3.67352 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:33:18.33 +57:37:18.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:18.33 +57:37:18.7: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:18.33 +57:37:18.7: 15.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 33 18.33 +57 37 18.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,2461235.6540,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.66 23:47:56.56 +60:41:16.0
115.23473 -1.23156 galactic Cas Second-epoch detections are separated by 1.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 | 23:47:56.56 +60:41:16.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:47:56.56 +60:41:16.0: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:47:56.56 +60:41:16.0: 16.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 07 14.1540* 23 47 56.56 +60 41 16.0 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,2461235.6540,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.57 23:42:40.74 +61:26:59.2
114.81185 -0.33322 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:42:40.74 +61:26:59.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:42:40.74 +61:26:59.2: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:40.74 +61:26:59.2: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 42 40.74 +61 26 59.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,2461235.6540,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.82 00:09:14.22 +66:22:23.2
118.71415 3.84756 galactic Cas Second-epoch detections are separated by 4.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:09:14.22 +66:22:23.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:14.22 +66:22:23.2: 16.16 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:09:14.22 +66:22:23.2: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 09 14.22 +66 22 23.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.53 00:11:53.74 +63:00:02.9
118.46164 0.47277 galactic Cas Second-epoch detections are separated by 3.2" and 7.2 pix
The object was found in VSX16" ZTF J001153.63+625947.3
Type: EW
# Max. Min./Amp. JD0 Period
19.632 r Y 0.786 r 2458364.84760 0.346259000000
ATTENTION: measured mag 13.53 is 5.3 mag brighter than the VSX record maximum brightness 18.85 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:11:53.74 +63:00:02.9: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:11:53.74 +63:00:02.9: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 11 53.74 +63 00 02.9 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
ZTF J001153.63+625947.3,2461235.6540,13.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J001153.63+625947.3 20260714.1540 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 07 14.1540 2461235.6540 13.62 23:38:17.32 +58:06:21.7
113.37199 -3.40153 galactic Cas Second-epoch detections are separated by 4.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 | Gaia DR3 1998976220211249920 | 23:38:12.06 +58:06:33.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:17.32 +58:06:21.7: 16.04 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:17.32 +58:06:21.7: 16.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 07 14.1540* 23 38 17.32 +58 06 21.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
Gaia DR3 1998976220211249920,2461235.6540,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1998976220211249920 20260714.1540 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 07 14.1540 2461235.6540 13.57 00:15:01.55 +61:25:35.8
118.59138 -1.13789 galactic Cas Second-epoch detections are separated by 7.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:15:01.55 +61:25:35.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:01.55 +61:25:35.8: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:15:01.55 +61:25:35.8: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 15 01.55 +61 25 35.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.68 23:23:42.89 +57:11:14.6
111.23075 -3.67796 galactic Cas Second-epoch detections are separated by 6.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:42.89 +57:11:14.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:23:42.89 +57:11:14.6: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:23:42.89 +57:11:14.6: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 23 42.89 +57 11 14.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,2461235.6540,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.78 23:52:04.28 +63:10:49.7
116.29427 1.07635 galactic Cas Second-epoch detections are separated by 8.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:52:04.28 +63:10:49.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:52:04.28 +63:10:49.7: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:52:04.28 +63:10:49.7: 15.54 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 52 04.28 +63 10 49.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.67 23:45:38.57 +61:53:16.9
115.26448 -0.00031 galactic Cas Second-epoch detections are separated by 1.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 | target | 23:45:38.57 +61:53:16.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:45:38.57 +61:53:16.9: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:45:38.57 +61:53:16.9: 15.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 07 14.1540* 23 45 38.57 +61 53 16.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,2461235.6540,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:56:31.94 +66:45:54.6
117.54420 4.46949 galactic Cep Second-epoch detections are separated by 4.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:56:31.94 +66:45:54.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:56:31.94 +66:45:54.6: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:56:31.94 +66:45:54.6: 15.81 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.81 +/- 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.78 23:30:24.26 +61:22:53.1
113.38543 0.02071 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:30:24.26 +61:22:53.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:30:24.26 +61:22:53.1: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:30:24.26 +61:22:53.1: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 30 24.26 +61 22 53.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,2461235.6540,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.75 23:10:49.25 +58:08:56.3
109.96030 -2.16603 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 | Gaia DR3 2010384340543913984 | 23:10:47.82 +58:08:24.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:10:49.25 +58:08:56.3: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:10:49.25 +58:08:56.3: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 10 49.25 +58 08 56.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
Gaia DR3 2010384340543913984,2461235.6540,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2010384340543913984 20260714.1540 13.75CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.83 23:15:50.84 +62:49:32.2
112.26388 1.95073 galactic Cas Second-epoch detections are separated by 1.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:15:50.84 +62:49:32.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:15:50.84 +62:49:32.2: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:15:50.84 +62:49:32.2: 15.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 07 14.1540* 23 15 50.84 +62 49 32.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.62 23:57:31.13 +61:21:17.1
116.51526 -0.84345 galactic Cas Second-epoch detections are separated by 7.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 | 23:57:31.13 +61:21:17.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:31.13 +61:21:17.1: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:31.13 +61:21:17.1: 15.58 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 57 31.13 +61 21 17.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.88 23:24:20.11 +60:29:55.0
112.40523 -0.58063 galactic Cas Second-epoch detections are separated by 4.0" 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:24:20.11 +60:29:55.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:24:20.11 +60:29:55.0: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:24:20.11 +60:29:55.0: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 24 20.11 +60 29 55.0 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.95 23:18:34.77 +63:55:21.4
112.94106 2.86688 galactic Cep Second-epoch detections are separated by 6.3" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:18:34.77 +63:55:21.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:18:34.77 +63:55:21.4: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:18:34.77 +63:55:21.4: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.65 23:56:56.74 +61:21:57.5
116.45043 -0.81815 galactic Cas Second-epoch detections are separated by 4.3" and 7.2 pix
The object was found in VSX16" Gaia DR3 2011951389439394816
Type: RS
# Max. Min./Amp. JD0 Period
17.490 G 17.670 G F
ATTENTION: measured mag 13.65 is 3.8 mag brighter than the VSX record maximum brightness 17.49 - possible unusual activity of a known variable! (Alternatively, this may be a new object that coincides with the known variable's position just by chance.)
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:56:56.74 +61:21:57.5: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:56:56.74 +61:21:57.5: 15.43 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 56 56.74 +61 21 57.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
Gaia DR3 2011951389439394816,2461235.6540,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2011951389439394816 20260714.1540 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.72 23:42:02.33 +62:52:58.9
115.11850 1.06884 galactic Cas Second-epoch detections are separated by 4.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 | target | 23:42:02.33 +62:52:58.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:42:02.33 +62:52:58.9: 16.19 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:42:02.33 +62:52:58.9: 16.16 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 42 02.33 +62 52 58.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,2461235.6540,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:43:14.39 +62:36:22.2
115.17829 0.76555 galactic Cas Second-epoch detections are separated by 4.2" and 6.7 pix
The object was found in VSX11" Gaia DR3 2016004429814746112
Type: S
# Max. Min./Amp. JD0 Period
16.470 G 17.290 G A
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:43:14.39 +62:36:22.2: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:43:14.39 +62:36:22.2: 15.34 +/- 0.19 detection
Forced photometry reference-image weighted average: 15.34 +/- 0.19
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 43 14.39 +62 36 22.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
Gaia DR3 2016004429814746112,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2016004429814746112 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:15:09.65 +63:06:31.4
112.29367 2.24288 galactic Cep Second-epoch detections are separated by 6.0" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:15:09.65 +63:06:31.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:15:09.65 +63:06:31.4: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:15:09.65 +63:06:31.4: 15.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.71 23:53:09.68 +61:56:08.0
116.13532 -0.16474 galactic Cas Second-epoch detections are separated by 1.8" 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:53:09.68 +61:56:08.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:53:09.68 +61:56:08.0: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:53:09.68 +61:56:08.0: 15.38 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.38 +/- 0.31
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 53 09.68 +61 56 08.0 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,2461235.6540,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.87 23:27:39.70 +63:28:51.9
113.74182 2.11408 galactic Cas Second-epoch detections are separated by 5.8" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:39.70 +63:28:51.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:27:39.70 +63:28:51.9: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:27:39.70 +63:28:51.9: 16.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 07 14.1540* 23 27 39.70 +63 28 51.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.67 23:54:11.43 +60:49:59.5
116.01078 -1.26695 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 | target | 23:54:11.43 +60:49:59.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:54:11.43 +60:49:59.5: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:54:11.43 +60:49:59.5: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 54 11.43 +60 49 59.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,2461235.6540,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.73 23:39:38.44 +60:11:27.7
114.11684 -1.44615 galactic Cas Second-epoch detections are separated by 4.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:39:38.44 +60:11:27.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:39:38.44 +60:11:27.7: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:39:38.44 +60:11:27.7: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 39 38.44 +60 11 27.7 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.97 23:00:12.42 +63:02:53.7
110.70990 2.84668 galactic Cep Second-epoch detections are separated by 4.1" 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:00:12.42 +63:02:53.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:00:12.42 +63:02:53.7: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:00:12.42 +63:02:53.7: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.80 23:25:53.58 +57:10:53.1
111.50803 -3.78074 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 | Gaia DR3 1997342659471777024 | 23:25:58.23 +57:10:27.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F8 (LAMOST DR5) J-Ks=0.516+/-0.276 (K)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:53.58 +57:10:53.1: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:53.58 +57:10:53.1: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 25 53.58 +57 10 53.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 1997342659471777024,2461235.6540,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 1997342659471777024 20260714.1540 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.76 23:21:04.75 +57:15:40.6
110.91936 -3.48792 galactic Cas Second-epoch detections are separated by 7.1" 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:21:04.75 +57:15:40.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:04.75 +57:15:40.6: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:21:04.75 +57:15:40.6: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 21 04.75 +57 15 40.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.87 23:28:41.74 +61:08:39.1
113.11641 -0.14080 galactic Cas Second-epoch detections are separated by 5.7" 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:28:41.74 +61:08:39.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:28:41.74 +61:08:39.1: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:28:41.74 +61:08:39.1: 15.48 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.48 +/- 0.24
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 28 41.74 +61 08 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
target,2461235.6540,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.90 23:39:52.09 +62:01:48.1
114.64697 0.31501 galactic Cas Second-epoch detections are separated by 3.2" 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:39:52.09 +62:01:48.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:39:52.09 +62:01:48.1: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:39:52.09 +62:01:48.1: 16.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 07 14.1540* 23 39 52.09 +62 01 48.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,2461235.6540,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.78 23:50:43.97 +62:08:09.3
115.90393 0.09535 galactic Cas Second-epoch detections are separated by 3.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:50:43.97 +62:08:09.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:50:43.97 +62:08:09.3: 15.45 +/- 0.25 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:50:43.97 +62:08:09.3: 15.46 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.46 +/- 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 07 14.1540* 23 50 43.97 +62 08 09.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,2461235.6540,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.02 23:49:49.45 +61:04:02.2
115.54808 -0.91808 galactic Cas Second-epoch detections are separated by 2.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 | 23:49:49.45 +61:04:02.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:49:49.45 +61:04:02.2: 16.13 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:49.45 +61:04:02.2: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 49 49.45 +61 04 02.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,2461235.6540,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.84 01:06:34.81 +65:33:30.2
124.49909 2.73273 galactic Cas Second-epoch detections are separated by 3.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 | 01:06:34.81 +65:33:30.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 01:06:34.81 +65:33:30.2: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 01:06:34.81 +65:33:30.2: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 01 06 34.81 +65 33 30.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.19 23:04:13.46 +61:29:08.8
110.49801 1.22966 galactic Cep 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:04:13.46 +61:29:08.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:13.46 +61:29:08.8: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:13.46 +61:29:08.8: 15.67 +/- 0.30 detection
Forced photometry reference-image weighted average: 15.67 +/- 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.03 23:41:58.55 +62:42:12.9
115.06389 0.89775 galactic Cas Second-epoch detections are separated by 3.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:41:58.55 +62:42:12.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:41:58.55 +62:42:12.9: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:41:58.55 +62:42:12.9: 15.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 07 14.1540* 23 41 58.55 +62 42 12.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,2461235.6540,14.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.84 23:39:51.02 +62:01:31.5
114.64370 0.31114 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 | 23:39:51.02 +62:01:31.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:39:51.02 +62:01:31.5: 16.13 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:39:51.02 +62:01:31.5: 16.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 07 14.1540* 23 39 51.02 +62 01 31.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,2461235.6540,13.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.05 23:12:07.92 +64:51:57.7
112.63380 3.99871 galactic Cep Second-epoch detections are separated by 0.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 | target | 23:12:07.92 +64:51:57.7 (user input) | T | P | (position from user input) J-Ks=0.520+/-0.075 (K)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:12:07.92 +64:51:57.7: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:12:07.92 +64:51:57.7: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.89 00:28:19.06 +63:41:25.9
120.37323 0.93370 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 | target | 00:28:19.06 +63:41:25.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:28:19.06 +63:41:25.9: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:28:19.06 +63:41:25.9: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 28 19.06 +63 41 25.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.79 23:51:30.44 +59:07:56.7
115.30035 -2.84845 galactic Cas Second-epoch detections are separated by 2.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 | 23:51:30.44 +59:07:56.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:51:30.44 +59:07:56.7: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:51:30.44 +59:07:56.7: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 51 30.44 +59 07 56.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.91 23:44:47.65 +58:34:54.7
114.32330 -3.17156 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 | target | 23:44:47.65 +58:34:54.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:44:47.65 +58:34:54.7: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:44:47.65 +58:34:54.7: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 44 47.65 +58 34 54.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,2461235.6540,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.87 23:55:06.24 +58:46:31.2
115.67300 -3.30019 galactic Cas Second-epoch detections are separated by 1.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 J358.7941+58.7821 | 23:55:06.24 +58:46:31.2 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:55:06.24 +58:46:31.2: 16.11 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:55:06.24 +58:46:31.2: 16.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 07 14.1540* 23 55 06.24 +58 46 31.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
ATO J358.7941+58.7821,2461235.6540,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.7941+58.7821 20260714.1540 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.16 23:44:12.58 +63:56:30.5
115.62997 2.02727 galactic Cas Second-epoch detections are separated by 4.2" 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:12.58 +63:56:30.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:44:12.58 +63:56:30.5: 16.09 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:44:12.58 +63:56:30.5: 16.17 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 44 12.58 +63 56 30.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,2461235.6540,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.22 23:29:24.12 +63:47:43.6
114.02447 2.35151 galactic Cep Second-epoch detections are separated by 6.5" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:24.12 +63:47:43.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:29:24.12 +63:47:43.6: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:29:24.12 +63:47:43.6: 16.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.07 00:14:56.77 +63:42:19.7
118.90356 1.11951 galactic Cas Second-epoch detections are separated by 8.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 | 00:14:56.77 +63:42:19.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:14:56.77 +63:42:19.7: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:14:56.77 +63:42:19.7: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 14 56.77 +63 42 19.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,2461235.6540,14.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.88 23:38:48.86 +58:38:52.1
113.58950 -2.90042 galactic Cas Second-epoch detections are separated by 2.0" and 7.3 pix
The object was found in VSX 8" Gaia DR3 2011037557824809728
Type: E
# Max. Min./Amp. JD0 Period
18.300 G 18.530 G 0.312743000000
ATTENTION: measured mag 13.88 is 4.4 mag brighter than the VSX record maximum brightness 18.30 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:48.86 +58:38:52.1: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:38:48.86 +58:38:52.1: 16.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 07 14.1540* 23 38 48.86 +58 38 52.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
Gaia DR3 2011037557824809728,2461235.6540,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 2011037557824809728 20260714.1540 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.45 23:01:58.73 +63:13:35.4
110.96610 2.92645 galactic Cep Second-epoch detections are separated by 4.1" 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:01:58.73 +63:13:35.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:01:58.73 +63:13:35.4: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:01:58.73 +63:13:35.4: 15.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.20 23:37:23.27 +62:43:25.5
114.56367 1.06130 galactic Cas Second-epoch detections are separated by 4.9" 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 | 23:37:23.27 +62:43:25.5 (user input) | T | P | (position from user input) J-Ks=0.966+/-0.143 (M)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:37:23.27 +62:43:25.5: 16.13 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:37:23.27 +62:43:25.5: 16.12 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 37 23.27 +62 43 25.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,2461235.6540,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 14.06 23:52:34.12 +61:27:52.6
115.96092 -0.60781 galactic Cas Second-epoch detections are separated by 2.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:52:34.12 +61:27:52.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:52:34.12 +61:27:52.6: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:52:34.12 +61:27:52.6: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 52 34.12 +61 27 52.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,2461235.6540,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.26 23:33:18.75 +61:00:15.7
113.60511 -0.44474 galactic Cas Second-epoch detections are separated by 5.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:33:18.75 +61:00:15.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:18.75 +61:00:15.7: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:18.75 +61:00:15.7: 15.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 07 14.1540* 23 33 18.75 +61 00 15.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,2461235.6540,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.31 23:32:31.78 +61:10:25.8
113.56549 -0.25473 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:32:31.78 +61:10:25.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:32:31.78 +61:10:25.8: 15.94 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:32:31.78 +61:10:25.8: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 32 31.78 +61 10 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,2461235.6540,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 14.71 23:05:15.68 +60:01:04.4
110.02759 -0.16658 galactic Cep Second-epoch detections are separated by 4.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:05:15.68 +60:01:04.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:05:15.68 +60:01:04.4: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:05:15.68 +60:01:04.4: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.90 23:58:35.93 +58:25:50.0
116.04615 -3.73300 galactic Cas Second-epoch detections are separated by 3.0" and 7.3 pix
The object was found in VSX 6" 2MASS J23583604+5825441
Type: SR
# Max. Min./Amp. JD0 Period
13.282 r Y 0.957 r 2458284.44080 313.397654500000 C
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:58:35.93 +58:25:50.0: 14.27 +/- 0.07 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:58:35.93 +58:25:50.0: 14.58 +/- 0.09 detection
Forced photometry reference-image weighted average: 14.40 +/- 0.06
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 58 35.93 +58 25 50.0 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
2MASS J23583604+5825441,2461235.6540,12.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
2MASS J23583604+5825441 20260714.1540 12.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.37 00:34:16.54 +64:30:54.5
121.08639 1.70491 galactic Cas Second-epoch detections are separated by 2.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 | 00:34:16.54 +64:30:54.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:16.54 +64:30:54.5: 15.42 +/- 0.20 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:34:16.54 +64:30:54.5: 15.56 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.48 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 34 16.54 +64 30 54.5 11.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.79 00:07:39.33 +64:40:01.5
118.26842 2.19250 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 | 00:07:39.33 +64:40:01.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:07:39.33 +64:40:01.5: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:07:39.33 +64:40:01.5: 16.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 07 14.1540* 00 07 39.33 +64 40 01.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.59 00:29:24.51 +60:49:55.1
120.24942 -1.92499 galactic Cas Second-epoch detections are separated by 5.2" and 6.9 pix
The object was found in VSX19" NSVS J0029273+604956
Type: M
# Max. Min./Amp. JD0 Period
16.607 g Y 2.044 g 2458522.52250 258.863730600000 M6.5
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:29:24.51 +60:49:55.1: 14.96 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:29:24.51 +60:49:55.1: 15.04 +/- 0.15 detection
Forced photometry reference-image weighted average: 15.00 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 29 24.51 +60 49 55.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0029273+604956,2461235.6540,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0029273+604956 20260714.1540 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.35 23:17:41.89 +60:25:56.5
111.61399 -0.36307 galactic Cas Second-epoch detections are separated by 8.8" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:17:41.89 +60:25:56.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:17:41.89 +60:25:56.5: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:17:41.89 +60:25:56.5: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 17 41.89 +60 25 56.5 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,13.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 13.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 07 14.1540 2461235.6540 13.27 23:49:03.75 +59:23:54.4
115.05895 -2.51649 galactic Cas Second-epoch detections are separated by 2.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 | ATO J357.2606+59.4014 | 23:49:03.75 +59:23:54.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:49:03.75 +59:23:54.4: 16.01 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:49:03.75 +59:23:54.4: 15.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 49 03.75 +59 23 54.4 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.2606+59.4014,2461235.6540,13.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.2606+59.4014 20260714.1540 13.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.74 23:51:12.50 +62:06:54.7
115.95318 0.06230 galactic Cas Second-epoch detections are separated by 1.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:51:12.50 +62:06:54.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:51:12.50 +62:06:54.7: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:51:12.50 +62:06:54.7: 16.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 07 14.1540* 23 51 12.50 +62 06 54.7 11.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 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 07 14.1540 2461235.6540 13.31 00:36:49.26 +59:12:19.5
121.05830 -3.61315 galactic Cas Second-epoch detections are separated by 4.5" and 7.3 pix
The object was found in VSX 6" ASASSN-V J003649.56+591213.4
Type: SR
# Max. Min./Amp. JD0 Period
14.890 V 15.900 V 2458343.91400 114.839655100000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:36:49.26 +59:12:19.5: 14.47 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:36:49.26 +59:12:19.5: 14.80 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.59 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 36 49.26 +59 12 19.5 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J003649.56+591213.4,2461235.6540,13.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J003649.56+591213.4 20260714.1540 13.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 10.92 23:12:32.93 +62:56:10.6
111.95453 2.19150 galactic Cep Second-epoch detections are separated by 3.4" and 6.6 pix
The object was found in VSX21" ZTF J231231.13+625627.0
Type: EW
# Max. Min./Amp. JD0 Period
18.958 r Y 0.268 r 2458494.58950 0.284313400000
ATTENTION: measured mag 10.92 is 7.8 mag brighter than the VSX record maximum brightness 18.69 - 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:12:32.93 +62:56:10.6: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:12:32.93 +62:56:10.6: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J231231.13+625627.0,2461235.6540,10.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J231231.13+625627.0 20260714.1540 10.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 13.57 00:05:32.97 +63:52:04.1
117.90475 1.44486 galactic Cas Second-epoch detections are separated by 5.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 | ZTF J000532.56+635242.7 | 00:05:32.55 +63:52:42.6 (Gaia DR3) | SR (local) | 267.824211300000 (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:32.97 +63:52:04.1: 15.01 +/- 0.16 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:05:32.97 +63:52:04.1: 14.49 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.63 +/- 0.08
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 05 32.97 +63 52 04.1 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000532.56+635242.7,2461235.6540,13.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 J000532.56+635242.7 20260714.1540 13.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.83 23:33:34.97 +58:28:11.7
112.88405 -2.87479 galactic Cas Second-epoch detections are separated by 3.6" 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.3858+58.4672 | 23:33:34.97 +58:28:11.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:34.97 +58:28:11.7: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:33:34.97 +58:28:11.7: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 33 34.97 +58 28 11.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
ATO J353.3858+58.4672,2461235.6540,12.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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.3858+58.4672 20260714.1540 12.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.27 00:04:39.25 +60:22:06.3
117.17617 -1.97946 galactic Cas Second-epoch detections are separated by 1.9" and 7.2 pix
The object was found in VSX10" FF Cas
Type: LB
# Max. Min./Amp. JD0 Period
15.600 pg 16.500 pg 172.000000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:39.25 +60:22:06.3: 13.25 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:04:39.25 +60:22:06.3: 13.28 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.27 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 00 04 39.25 +60 22 06.3 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
FF Cas,2461235.6540,12.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
FF Cas 20260714.1540 12.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 07 14.1540 2461235.6540 11.34 23:51:44.65 +62:49:13.2
116.17577 0.73424 galactic Cas Second-epoch detections are separated by 5.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:51:44.65 +62:49:13.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:51:44.65 +62:49:13.2: 15.86 +/- 0.32 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:51:44.65 +62:49:13.2: 15.95 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.86 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 51 44.65 +62 49 13.2 11.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,11.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 11.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 11.87 23:57:21.15 +58:25:10.0
115.88387 -3.71024 galactic Cas Second-epoch detections are separated by 3.1" and 7.2 pix
The object was found in VSX 6" V0653 Cas
Type: SR
# Max. Min./Amp. JD0 Period
13.900 V 15.400 V 2458343.63840 220.561628600000 S:C:
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:21.15 +58:25:10.0: 12.97 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:57:21.15 +58:25:10.0: 12.99 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.98 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 57 21.15 +58 25 10.0 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0653 Cas,2461235.6540,11.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0653 Cas 20260714.1540 11.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 07 14.1540 2461235.6540 12.68 23:06:29.57 +56:58:16.1
108.96897 -3.02821 galactic Cas Second-epoch detections are separated by 3.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 | target | 23:06:29.57 +56:58:16.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:06:29.57 +56:58:16.1: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:06:29.57 +56:58:16.1: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 07 14.1540* 23 06 29.57 +56 58 16.1 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461235.6540,12.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260714.1540 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461061.56485073 21.01.2026 01:33:13.103 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
First image: 2461061.56485073 21.01.2026 01:33:13.103 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Last image: 2461235.65438920 14.07.2026 03:42:09.227 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 21
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.70
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: 20 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 28263
Objects passed selection criteria: 28193
Measurements per detected object (mean, median, min, max): 3.2 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.2 4.0 2 4
Average stars detected per image: 23504.5
Average stars matched: 22856.5 (97.2431 %)
Memory usage VmPeak: 135032 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Mon Jul 13 18:59:08 CDT 2026
VaST build number 1.0rc89-151-g9f3411f7
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-13)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Tue Jul 14 02:09:46 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: 2461061.56485073 21.01.2026 01:33:13.103 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
First image: 2461061.56485073 21.01.2026 01:33:13.103 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Last image: 2461235.65438920 14.07.2026 03:42:09.227 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 422
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.40
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: 127 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 2.0 # minimum number of pixels above threshold
DETECT_THRESH 3.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 3.0 # or , in mag.arcsec-2
SATUR_LEVEL 57000.0 # level (in ADUs) at which arises saturation
GAIN 0.83 # detector gain in e-/ADU
WEIGHT_TYPE BACKGROUND
Total objects detected (at least 2 times): 197763
Objects passed selection criteria: 197270
Measurements per detected object (mean, median, min, max): 3.2 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.2 4.0 2 4
Average stars detected per image: 166836
Average stars matched: 161390 (96.7356 %)
Memory usage VmPeak: 2031044 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Mon Jul 13 18:59:08 CDT 2026
VaST build number 1.0rc89-151-g9f3411f7
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-07-13)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Tue Jul 14 02:45:56 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/TTUQ1b1x1/TTUQ1_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
SExtractor catalog cache: saved Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.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: 2461235.65364067
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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits exists and is non-empty
Saving wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits to local_wcs_cache/
'wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits' -> 'local_wcs_cache/wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits'
wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits exists and is non-empty
Saving wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits to local_wcs_cache/
'wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits' -> 'local_wcs_cache/wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits'
wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits'
wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits (1st reference image)
verification OK: wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Image size: 943.6'x628.6' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.91"/pix along the X axis and 5.90"/pix along the Y axis
Image center: 23:59:59.383 +61:58:52.42 J2000 4789.000 3195.000
###################################
The image scale is 5.91"/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-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Image size: 939.2'x617.2' 15.7(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.80"/pix along the Y axis
Image center: 00:00:10.324 +61:58:24.30 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 23:59:59.383 +61:58:52.42
Second-epoch image center 00:00:10.324 +61:58:24.30
Angular distance between the image centers 0.0228 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Image size: 939.2'x617.2' 15.7(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.80"/pix along the Y axis
Image center: 00:00:07.485 +61:57:46.60 J2000 4789.000 3195.000
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 23:59:59.383 +61:58:52.42
Second-epoch image center 00:00:07.485 +61:57:46.60
Angular distance between the image centers 0.0242 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 00:00:10.324 +61:58:24.30
Second-epoch second image center 00:00:07.485 +61:57:46.60
Angular distance between the image centers 0.01186 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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits &> /tmp/tmp.o24K4N2VRX
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits &> /tmp/tmp.IAO3uX5wAh
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits &> /tmp/tmp.dglARiHDaR
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits &> /tmp/tmp.RyKyFAb6bL
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits and wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits and wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat
Found non-empty wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits and wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat
The reference image (wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits) and catalog (wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat) found
'wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat' -> 'wcsmag.cat'
Read 30191 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 359.9985 deg, Dec +55.2732 to +67.4066 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0001 to 359.9985 deg, Dec 55.2732 to 67.4066 deg
Loaded 134187 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): 2225 out of 2505 total matches.
Matched with Tycho-2 2505 out of 30191 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.944500
a=0.000000 b=1.000000 c=22.944500
From vast_summary.log: estimated ref. image limiting mag.: -7.70
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.24
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.24
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 30191 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0001 to 359.9985 deg, Dec +55.2732 to +67.4066 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0001 to 359.9985 deg, Dec 55.2732 to 67.4066 deg
Loaded 134187 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): 2225 out of 2505 total matches.
Matched with Tycho-2 2505 out of 30191 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits -> calib.txt_param_ref_wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits (aperture=6.0)
Read 30227 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0004 to 359.9985 deg, Dec +55.3299 to +67.4069 deg
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.00
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.01
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.02
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.03
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.04
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.05
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.06
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.07
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.08
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.09
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.10
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.11
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.12
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.13
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.14
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.15
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.16
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.17
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.18
Reading Tycho2 catalog file lib/catalogs/tycho2/tyc2.dat.19
Tycho-2 catalog search boundaries: RA 0.0004 to 359.9985 deg, Dec 55.3299 to 67.4069 deg
Loaded 133369 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): 1543 out of 1717 total matches.
Matched with Tycho-2 1717 out of 30227 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits -> calib.txt_param_ref_wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits (aperture=6.0)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 21 candidate transients before the final filtering. (Hard limit: 10000)
Median FWHM seeing for isolated stars:
2.1 pix Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
2.1 pix Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
2.5 pix fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
2.5 pix fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
2.1 pix wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
2.1 pix wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Limiting magnitude estimates:
15.2 mag. Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
15.2 mag. Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
14.4 mag. fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
14.4 mag. fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
All-image limiting magnitude estimate: 14.4 (SNR ) 11.6 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.5 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.o24K4N2VRX (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.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-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits' -> 'wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS-calibrated image found: wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Checking if the catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat corresponding to the image wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat corresponding to the image wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS catalog name: wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 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=3591, bad_region=0, passed=30191
Got 30191 stars (including 26565 good ones) from the SExtractor catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat
util/solve_plate_with_UCAC5 got 30191 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 943.6'
Seting catalog search parameters based on the expected field of view 943.6 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013106 (47.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010484 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.1617 through 0 to 20.0679, gap 20.0679 to 341.1617
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 943 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 901 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.31"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 27209 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.57"
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 341.1680 through 0 to 20.0648, gap 20.0648 to 341.1680
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 969 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 963 matched stars entering correct_measured_positions(), 27228 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.53"
Accuracy estimation diagnostic: 963 matched stars entering correct_measured_positions(), 28093 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.24"
Excluding outliers - 963 stars left (next iteration limit 1030)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits N_match=963 sigma_overall_arcsec=1.986 sigma_q1_arcsec=1.748 sigma_q2_arcsec=1.552 sigma_q3_arcsec=1.325 sigma_q4_arcsec=1.462 n_q1=158 n_q2=269 n_q3=235 n_q4=301 worst_quadrant_to_overall_ratio=0.880
The image catalog is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits -region wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.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.IAO3uX5wAh (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.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-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits' -> 'wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS-calibrated image found: wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
Checking if the catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat corresponding to the image wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat corresponding to the image wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits
WCS catalog name: wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=4, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3557, bad_region=1, passed=30223
Got 30223 stars (including 26629 good ones) from the SExtractor catalog wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat
util/solve_plate_with_UCAC5 got 30223 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 943.5'
Seting catalog search parameters based on the expected field of view 943.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013104 (47.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010483 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 341.1650 through 0 to 19.9057, gap 19.9057 to 341.1650
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 948 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 939 matched stars entering correct_measured_positions(), 905 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 937 matched stars entering correct_measured_positions(), 27480 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.60"
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 341.1694 through 0 to 19.9053, gap 19.9053 to 341.1694
Reading UCAC5 zone files...
Searching UCAC5 zones 726 to 789 (Dec 55.3 to 67.4)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 27495 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.56"
Accuracy estimation diagnostic: 967 matched stars entering correct_measured_positions(), 28288 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.26"
Excluding outliers - 967 stars left (next iteration limit 1030)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits N_match=967 sigma_overall_arcsec=2.121 sigma_q1_arcsec=1.575 sigma_q2_arcsec=1.684 sigma_q3_arcsec=1.362 sigma_q4_arcsec=1.545 n_q1=166 n_q2=270 n_q3=234 n_q4=297 worst_quadrant_to_overall_ratio=0.794
The image catalog is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits -region wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.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.dglARiHDaR (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Checking if the catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
WCS catalog name: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 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=1269, bad_region=0, passed=17098
Got 17098 stars (including 15813 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat
util/solve_plate_with_UCAC5 got 17098 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 939.2'
Seting catalog search parameters based on the expected field of view 939.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013044 (47.0 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010436 (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 341.5402 through 0 to 19.6694, gap 19.6694 to 341.5402
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 397 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 295 matched stars entering correct_measured_positions(), 233 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 274 matched stars entering correct_measured_positions(), 5104 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.30"
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 341.5385 through 0 to 19.6811, gap 19.6811 to 341.5385
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 431 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 372 matched stars entering correct_measured_positions(), 5128 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.22"
Accuracy estimation diagnostic: 371 matched stars entering correct_measured_positions(), 6441 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.72"
Excluding outliers - 371 stars left (next iteration limit 301)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits N_match=371 sigma_overall_arcsec=9.864 sigma_q1_arcsec=24.652 sigma_q2_arcsec=4.923 sigma_q3_arcsec=27.505 sigma_q4_arcsec=17.210 n_q1=45 n_q2=222 n_q3=30 n_q4=74 worst_quadrant_to_overall_ratio=2.788
The image catalog is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits -region wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.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.RyKyFAb6bL (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Checking if the catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
WCS catalog name: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 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=1205, bad_region=0, passed=17113
Got 17113 stars (including 15894 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat
util/solve_plate_with_UCAC5 got 17113 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 939.2'
Seting catalog search parameters based on the expected field of view 939.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013044 (47.0 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010436 (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 341.5266 through 0 to 19.6696, gap 19.6696 to 341.5266
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 294 matched stars entering correct_measured_positions(), 234 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.59"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 272 matched stars entering correct_measured_positions(), 5071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.46"
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 341.5214 through 0 to 19.6804, gap 19.6804 to 341.5214
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 430 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 366 matched stars entering correct_measured_positions(), 5101 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.24"
Accuracy estimation diagnostic: 365 matched stars entering correct_measured_positions(), 6505 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.95"
Excluding outliers - 365 stars left (next iteration limit 299)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits N_match=365 sigma_overall_arcsec=10.219 sigma_q1_arcsec=22.348 sigma_q2_arcsec=5.367 sigma_q3_arcsec=30.179 sigma_q4_arcsec=18.205 n_q1=42 n_q2=220 n_q3=29 n_q4=74 worst_quadrant_to_overall_ratio=2.953
The image catalog is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits -region wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
###################################
# Pre-local-correction WCS quality summary (see WCS_QUALITY_DIAG lines above)
ref1=Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits sigma_overall=1.986 worst_q_ratio=0.880
ref2=Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits sigma_overall=2.121 worst_q_ratio=0.794
new1=fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits sigma_overall=9.864 worst_q_ratio=2.788
new2=fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits sigma_overall=10.219 worst_q_ratio=2.953
reference average sigma_overall=2.0535 worst_q_ratio=0.837
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits) flagged: sigma=9.864 (ref avg 2.0535), ratio=2.788 (ref avg 0.837), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00003.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/lib/make_outxyls_for_astrometric_calibration found 16111 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.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: "out2869224.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2869224.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
log-odds ratio 22.3691 (5.18523e+09), 11 match, 0 conflict, 45 distractors, 106 index.
RA,Dec = (0.143901,61.9632), pixel scale 5.92789 arcsec/pix.
Hit/miss: Hit/miss: -------+-------+---+---+------++---+---+---+---+-------+(best)------+----+-------+---+-------+------------
Field 1: solved with index index-4114.fits.
Field 1 solved: writing to file ./out2869224.solved to indicate this.
Field: out2869224.xyls
Field center: (RA,Dec) = (0.145734, 61.963940) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:34.976, +61:57:50.183).
Field size: 15.4573 x 10.4057 degrees
Field rotation angle: up is 14.4295 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits' -> 'fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 14 02:17 fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
-rw-r--r-- 1 apache apache 8.5K Jul 14 02:17 out2869224.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits (fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.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: "out2869224.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2869224.axy"...
Only searching for solutions within 15.445 degrees of RA,Dec (0.147567,61.9647)
log-odds ratio 25.8051 (1.61062e+11), 7 match, 0 conflict, 23 distractors, 28 index.
RA,Dec = (0.0393126,61.9719), pixel scale 5.95555 arcsec/pix.
Hit/miss: Hit/miss: ---+-+-------------+-----+++-+(best)----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2869224.solved to indicate this.
Field: out2869224.xyls
Field center: (RA,Dec) = (0.041165, 61.972642) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:09.879, +61:58:21.511).
Field size: 15.6425 x 10.4812 degrees
Field rotation angle: up is 9.80209 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 14 02:17 fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
-rw-r--r-- 1 apache apache 8.5K Jul 14 02:17 out2869224.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
The field of view is large: we'll try to run Astromety.net code on the image itself rather than a star list
Reading input file "wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 83508 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.axy"...
Verifying WCS using indices with quads of size [63.4067, 950.505] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS using indices with quads of size [63.4067, 950.505] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Generating wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits created.
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
Image size: 939.2'x617.2' 15.7(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.80"/pix along the Y axis
Image center: 00:00:10.324 +61:58:24.30 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 17098 stars ###
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/correct_sextractor_wcs_catalog_usingxy2sky899009.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
WCS catalog name: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 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=1269, bad_region=0, passed=17098
Got 17098 stars (including 15813 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat
util/solve_plate_with_UCAC5 got 17098 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 939.2'
Seting catalog search parameters based on the expected field of view 939.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013044 (47.0 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010436 (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 341.5402 through 0 to 19.6694, gap 19.6694 to 341.5402
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 397 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 295 matched stars entering correct_measured_positions(), 233 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 274 matched stars entering correct_measured_positions(), 5104 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.30"
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 341.5385 through 0 to 19.6811, gap 19.6811 to 341.5385
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 431 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 372 matched stars entering correct_measured_positions(), 5128 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.22"
Accuracy estimation diagnostic: 371 matched stars entering correct_measured_positions(), 6441 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.72"
Excluding outliers - 371 stars left (next iteration limit 301)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits N_match=371 sigma_overall_arcsec=9.864 sigma_q1_arcsec=24.652 sigma_q2_arcsec=4.923 sigma_q3_arcsec=27.505 sigma_q4_arcsec=17.210 n_q1=45 n_q2=222 n_q3=30 n_q4=74 worst_quadrant_to_overall_ratio=2.788
The image catalog is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits -region wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.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-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits): sigma 9.864->9.864, ratio 2.788->2.788; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits) flagged: sigma=10.219 (ref avg 2.0535), ratio=2.953 (ref avg 0.837), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00004.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/lib/make_outxyls_for_astrometric_calibration found 16178 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.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: "out904107.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out904107.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
log-odds ratio 18.7608 (1.40515e+08), 16 match, 0 conflict, 72 distractors, 106 index.
RA,Dec = (0.131799,61.9527), pixel scale 5.92791 arcsec/pix.
Field 1 did not solve (index index-4114.fits, field objects 1-10).
log-odds ratio 1419.05 (inf), 204 match, 3 conflict, 311 distractors, 212 index.
RA,Dec = (0.147507,61.9847), pixel scale 5.97988 arcsec/pix.
Hit/miss: Hit/miss: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-++++++++++-++++-++++++-+++
Field 1: solved with index index-4113.fits.
Field 1 solved: writing to file ./out904107.solved to indicate this.
Field: out904107.xyls
Field center: (RA,Dec) = (0.007153, 61.983727) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:01.717, +61:59:01.416).
Field size: 15.8069 x 10.5779 degrees
Field rotation angle: up is 3.38928 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits' -> 'fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 14 02:29 fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
-rw-r--r-- 1 apache apache 12K Jul 14 02:29 out904107.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits (fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.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: "out904107.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out904107.axy"...
Only searching for solutions within 15.7433 degrees of RA,Dec (0.00902083,61.9845)
log-odds ratio 23.5393 (1.67112e+10), 7 match, 0 conflict, 26 distractors, 28 index.
RA,Dec = (0.0274849,61.9614), pixel scale 5.95551 arcsec/pix.
Hit/miss: Hit/miss: ---+-+-----------+---+-----+-+--+(best)-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out904107.solved to indicate this.
Field: out904107.xyls
Field center: (RA,Dec) = (0.029336, 61.962170) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:07.041, +61:57:43.812).
Field size: 15.6424 x 10.4813 degrees
Field rotation angle: up is 9.81122 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jul 14 02:29 fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
-rw-r--r-- 1 apache apache 8.5K Jul 14 02:29 out904107.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits)... done!
done!
All done!
The WCS header appears to be added with no errors.
Keyword does not exist
Keyword has been changed to:
VAST001 = 'wcs_image_calibration.sh' / VaST script name
Keyword does not exist
Keyword has been changed to:
VAST002 = 'local ' / ASTROMETRYNET_LOCAL_OR_REMOTE
Keyword does not exist
Keyword has been changed to:
VAST003 = 'local ' / PLATE_SOLVE_SERVER
Keyword does not exist
Keyword has been changed to:
VAST004 = 'iteration02' / astrometry.net run
The field of view is large: we'll try to run Astromety.net code on the image itself rather than a star list
Reading input file "wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 83916 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.axy"...
Verifying WCS using indices with quads of size [63.4063, 950.499] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 3.78355
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 3.0904
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 2.43362
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 1.74978
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 1.1094
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0.471963
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS using indices with quads of size [63.4063, 950.499] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 3.78355
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 3.0904
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 2.43362
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 1.74978
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 1.1094
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0.471963
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Generating wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits created.
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
verification OK: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
Image size: 939.2'x617.2' 15.7(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.88"/pix along the X axis and 5.80"/pix along the Y axis
Image center: 00:00:07.485 +61:57:46.60 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 17113 stars ###
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/correct_sextractor_wcs_catalog_usingxy2sky2095429.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
WCS catalog name: wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat
Excluding image region: 190.0 1039.0 192.0 1041.0 (defined in bad_region.lst)
Excluding image region: 226.0 1548.0 228.0 1550.0 (defined in bad_region.lst)
Excluding image region: 351.0 1875.0 353.0 1877.0 (defined in bad_region.lst)
Excluding image region: 501.0 5912.0 503.0 5914.0 (defined in bad_region.lst)
Excluding image region: 638.0 5545.0 640.0 5547.0 (defined in bad_region.lst)
Excluding image region: 724.0 2731.0 726.0 2733.0 (defined in bad_region.lst)
Excluding image region: 883.0 1376.0 885.0 1378.0 (defined in bad_region.lst)
Excluding image region: 901.0 3972.0 903.0 3974.0 (defined in bad_region.lst)
Excluding image region: 1151.0 918.0 1153.0 920.0 (defined in bad_region.lst)
Excluding image region: 1157.0 135.0 1159.0 137.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 50 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=1205, bad_region=0, passed=17113
Got 17113 stars (including 15894 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat
util/solve_plate_with_UCAC5 got 17113 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 939.2'
Seting catalog search parameters based on the expected field of view 939.2 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013044 (47.0 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010436 (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 341.5266 through 0 to 19.6696, gap 19.6696 to 341.5266
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 294 matched stars entering correct_measured_positions(), 234 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.59"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 272 matched stars entering correct_measured_positions(), 5071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.46"
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 341.5214 through 0 to 19.6804, gap 19.6804 to 341.5214
Reading UCAC5 zone files...
Searching UCAC5 zones 727 to 787 (Dec 55.5 to 67.2)
Done reading UCAC5 zone files...
Matched 430 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 366 matched stars entering correct_measured_positions(), 5101 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.24"
Accuracy estimation diagnostic: 365 matched stars entering correct_measured_positions(), 6505 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.95"
Excluding outliers - 365 stars left (next iteration limit 299)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits N_match=365 sigma_overall_arcsec=10.219 sigma_q1_arcsec=22.348 sigma_q2_arcsec=5.367 sigma_q3_arcsec=30.179 sigma_q4_arcsec=18.205 n_q1=42 n_q2=220 n_q3=29 n_q4=74 worst_quadrant_to_overall_ratio=2.953
The image catalog is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits -region wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.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-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits): sigma 10.219->10.219, ratio 2.953->2.953; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=9.864 -- 4.80x the reference average (2.0535); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=10.219 -- 4.98x the reference average (2.0535); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=2.788 -- 3.33x the reference average (0.837); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=2.953 -- 3.53x the reference average (0.837); plate solution may be of low accuracy
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014_astrometric_residuals.png (963 matched stars from wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 1.03 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015_astrometric_residuals.png (967 matched stars from wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 1.03 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052_astrometric_residuals.png (371 matched stars from wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.13 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053_astrometric_residuals.png (365 matched stars from wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.42 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-41-04_20.00sec_-0.00C_LIGHTs_0052.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-07-13_CI_Cas-02-Q1b1x1_224311_TTUQ1b1x1_3900186_8XsvlDP2/wcs_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053.fits'
Preparing the HTML report for the field Cas-02-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:55:16.91 +56:53:58.3: 99.00 +/- 99.00 edge
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:55:16.91 +56:53:58.3: 99.00 +/- 99.00 edge
Forced photometry filter REJECTED candidate at 00:55:16.91 +56:53:58.3: at least one reference image reported edge (off-image or aperture/annulus past image boundary); cannot perform the forced-photometry cross-check
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:36:51.69 +63:07:02.1: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:41.92 +62:16:34.8: 15.71 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:04:18.14 +64:23:31.0: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:16:27.43 +64:56:10.0: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:11:57.43 +60:33:55.8: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:18.96 +64:31:04.4: 15.37 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:21.81 +61:29:34.4: 13.06 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:36:51.69 +63:07:02.1: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:16:27.43 +64:56:10.0: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:11:57.43 +60:33:55.8: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:25:41.92 +62:16:34.8: 15.68 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:04:18.14 +64:23:31.0: 15.69 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:54:55.87 +58:33:48.0: 9.96 +/- 0.00 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:34:18.96 +64:31:04.4: 15.77 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.49 +/- 0.18
Forced photometry filter KEPT candidate at 00:34:18.96 +64:31:04.4: ref_mag=15.49 +/- 0.18 new_mean_mag=11.2128 delta=4.28 (need > 0.90)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:03:27.30 +57:56:22.5: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:04:21.81 +61:29:34.4: 12.93 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.99 +/- 0.02
Forced photometry filter KEPT candidate at 00:04:21.81 +61:29:34.4: ref_mag=12.99 +/- 0.02 new_mean_mag=11.8949 delta=1.09 (need > 0.90)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 00:54:55.87 +58:33:48.0: 10.57 +/- 0.00 detection
Forced photometry reference-image weighted average: 10.11 +/- 0.00
Forced photometry filter KEPT candidate at 00:54:55.87 +58:33:48.0: ref_mag=10.11 +/- 0.00 new_mean_mag=8.3476 delta=1.76 (need > 0.90)
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:03:27.30 +57:56:22.5: 15.49 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:39:54.53 +59:34:56.9: 15.70 +/- 0.33 detection
Forced photometry on wcs_Cas-02-Q1b1x1_2026-01-20_19-34-13_20.00sec_-14.90C_LIGHT_0015.fits at 23:39:54.53 +59:34:56.9: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.70 +/- 0.33
Forced photometry filter KEPT candidate at 23:39:54.53 +59:34:56.9: ref_mag=15.70 +/- 0.33 new_mean_mag=10.7901 delta=4.91 (need > 0.90)
Adding exclusion_list_local.txt__out18628.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out20685.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out26957.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52152.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52157.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52197.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52256.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52292.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52335.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52486.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 16s
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 52152_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52152_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52153_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52153_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52157_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52157_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52197_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52197_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52208_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52208_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:01.24 +57:54:43.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52215_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52215_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52250_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52250_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52256_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52256_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52263_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52263_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52292_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52292_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52319_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52319_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52335_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52335_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52363_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52363_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52372_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52372_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:56:28.19 +60:47:06.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52395_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 52395_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 52486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18628_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 18628_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 26289_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 26289_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:10:48.88 +57:29:26.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 26957_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 26957_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 20685_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 20685_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 51654_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 51654_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (32.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242765_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242765_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242778_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242778_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242785_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242785_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242795_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242795_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242804_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242804_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242807_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242807_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242811_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242811_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242819_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242819_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242820_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242820_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (24.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242821_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242821_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242824_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242824_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242825_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242825_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242828_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242828_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242831_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242831_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242843_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242843_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242847_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242847_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242851_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242851_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242853_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242853_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242854_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242854_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242857_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242857_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242859_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242859_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242860_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242860_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242862_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242862_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242863_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242863_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242864_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242864_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242865_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242865_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242871_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242871_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242872_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242872_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (18.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (26.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242883_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242883_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242886_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242886_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242887_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242887_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242888_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242888_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242890_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242890_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242895_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242895_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242896_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242896_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (22.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242897_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242897_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242899_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242899_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242900_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242900_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242901_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242901_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242904_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242904_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242906_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242906_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242913_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242913_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242916_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242916_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242917_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242917_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242920_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242920_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242921_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242921_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242923_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242923_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242925_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242925_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242927_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242927_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242928_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242928_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (32.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242931_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242931_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242932_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242932_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242933_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242933_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (32.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242936_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242936_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242937_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242937_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242938_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242938_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242939_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242939_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242942_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242942_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (35.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242944_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242944_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242945_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242945_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242946_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242946_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (32.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242947_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242947_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242948_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242948_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242950_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242950_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242951_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242951_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242952_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242952_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242953_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242953_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (32.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242954_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242954_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242957_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242957_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242958_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242958_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242959_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242959_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242960_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242960_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242963_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242963_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242966_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242966_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242967_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242967_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242968_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242968_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242969_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242969_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (16.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242971_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242971_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242972_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242972_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242973_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242973_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242975_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242975_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242977_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242977_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (18.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242979_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242979_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242980_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242980_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242981_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242981_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242982_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242982_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242983_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242983_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242985_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242985_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242986_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242986_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242987_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242987_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242988_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242988_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242990_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242990_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242991_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 242991_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:09:38.56 +59:18:14.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 242996_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 242996_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243001_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243001_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243003_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243003_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243004_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243004_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243005_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243005_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (29.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243007_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243007_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243008_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243008_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243010_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243010_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:15:52.55 +59:25:22.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243011_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243011_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243012_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243012_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243015_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243015_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243019_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243019_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243020_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243020_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:13:14.16 +57:15:56.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243021_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243021_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243022_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243022_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:58:34.89 +61:12:21.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243023_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243023_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243025_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243025_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243026_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243026_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243029_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243029_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243030_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243030_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243032_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243032_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243033_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243033_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243034_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243034_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243035_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243035_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243037_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243037_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243038_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243038_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243041_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243041_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243043_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243043_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243045_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243045_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (31.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243046_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243046_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243047_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243047_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243048_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243048_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243052_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243052_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243053_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243053_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243054_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243054_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243058_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243058_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243059_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243059_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243060_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243060_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243061_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243061_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243062_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243062_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243064_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243064_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243065_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243065_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243066_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243066_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:16:13.11 +60:59:35.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243067_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243067_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243068_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243068_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243071_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243071_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243127_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243127_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243168_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243168_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:16:27.27 +64:56:14.4 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243241_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243241_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243293_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243293_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243300_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243300_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243303_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243303_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243390_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243390_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:48:47.21 +62:12:43.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243399_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243399_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243444_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243444_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243504_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243504_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243542_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243542_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243550_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243550_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:40:15.52 +56:32:51.1 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243553_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243553_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243570_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243570_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:56:20.68 +60:44:49.9 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243585_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243585_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:19.07 +60:18:19.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243624_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243624_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243637_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243637_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243651_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243651_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243655_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243655_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243662_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243662_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243672_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243672_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243684_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243684_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243692_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243692_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 01:03:47.43 +61:03:21.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243695_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243695_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243696_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243696_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243702_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243702_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243705_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243705_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (33.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243724_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243724_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:40:11.49 +59:31:22.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243757_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243757_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243761_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243761_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243785_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243785_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243793_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243793_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243809_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243809_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243827_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243827_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243838_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243838_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:26:04.11 +56:47:32.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243846_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243846_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243853_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243853_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243857_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243857_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243861_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243861_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243864_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243864_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:54:36.59 +57:28:25.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243866_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243866_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:56:23.39 +60:44:26.5 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243934_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243934_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243938_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243938_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243942_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243942_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243943_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243943_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243949_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243949_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243965_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 243965_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243973_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243973_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:56:23.55 +59:10:40.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243988_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243988_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:03:39.02 +58:54:33.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243996_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 243996_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 01:02:51.25 +62:35:30.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244009_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244009_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:21:25.49 +59:13:59.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244018_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244018_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 01:04:16.31 +61:36:16.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244040_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244040_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244051_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244051_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244054_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244054_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 01:03:37.09 +61:03:04.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244056_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244056_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244058_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244058_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244078_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244078_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244087_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244087_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244096_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244096_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244104_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244104_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:24:36.36 +56:59:03.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244111_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244111_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244120_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244120_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:06.38 +57:18:56.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244122_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244122_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244142_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244142_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244145_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244145_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (29.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244160_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244160_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244163_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244163_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244167_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244167_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244179_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244179_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244197_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244197_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244199_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244199_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244210_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244210_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:52:20.31 +59:45:02.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244216_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244216_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244222_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244222_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244223_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244223_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244227_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244227_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244230_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244230_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244233_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244233_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244245_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244245_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244251_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244251_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244257_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244257_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244260_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244260_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244261_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244261_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:10:42.91 +59:41:55.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244269_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244269_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:49:56.71 +60:46:28.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244271_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244271_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244278_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244278_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244289_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244289_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:17:55.76 +59:09:19.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244308_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244308_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244314_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244314_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244315_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244315_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (22.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244322_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244322_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244326_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244326_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244338_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244338_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244341_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244341_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (31.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244345_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244345_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (21.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244361_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244361_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244367_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244367_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244368_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244368_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244375_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244375_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244378_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244378_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244380_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244380_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:53.81 +60:30:12.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244384_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244384_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244389_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244389_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:30:12.32 +58:32:10.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244407_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244407_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244421_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244421_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244423_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244423_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244428_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244428_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244429_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244429_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244433_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244433_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244438_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244438_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244443_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244443_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244445_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244445_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244453_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244453_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244455_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244455_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:23:52.56 +60:22:47.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244462_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244462_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244470_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244470_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244471_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244471_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:05:42.23 +58:17:45.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244479_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244479_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244484_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244484_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244490_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244490_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244494_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244494_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244495_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244495_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244498_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244498_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244508_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244508_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:09:15.16 +59:06:08.8 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244513_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244513_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:10:41.05 +59:41:37.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244515_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244515_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:11:54.52 +57:16:26.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244519_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244519_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244522_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244522_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:23:55.61 +60:58:56.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244528_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244528_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244533_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244533_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244535_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244535_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244537_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244537_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (29.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244541_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244541_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:55:01.72 +58:11:03.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244566_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244566_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244570_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244570_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244574_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244574_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244586_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244586_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244591_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244591_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:01:37.58 +60:28:09.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244596_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244596_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244597_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244597_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244603_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244603_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:10:24.67 +60:01:06.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244605_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244605_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244607_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244607_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244613_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244613_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244635_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244635_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244640_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244640_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244646_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244646_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244648_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244648_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244649_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244649_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244651_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244651_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (28.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244666_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244666_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:24:18.22 +57:40:54.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244678_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244678_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244686_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244686_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244688_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244688_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244706_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244706_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244707_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244707_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244712_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244712_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244718_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244718_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:40:01.50 +60:10:56.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244719_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244719_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244725_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244725_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244736_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244736_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244744_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244744_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244746_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244746_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:19:04.10 +59:42:42.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244760_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244760_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244776_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244776_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244778_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244778_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (31.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244780_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244780_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244781_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244781_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244787_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244787_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244788_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244788_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244789_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244789_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244791_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244791_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244794_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244794_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244796_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244796_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244797_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244797_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244798_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244798_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:21:46.24 +61:02:51.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244804_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244804_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244805_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244805_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244811_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244811_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244812_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244812_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244818_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244818_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244820_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244820_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:47:10.10 +57:25:27.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244827_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244827_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:23:43.85 +59:32:02.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244834_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244834_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244835_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244835_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244849_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244849_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244851_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244851_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244865_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244865_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:48:58.68 +59:59:14.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244870_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244870_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244887_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244887_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244903_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244903_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244909_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244909_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244910_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244910_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244916_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244916_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244935_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244935_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244962_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244962_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (29.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244968_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 244968_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244995_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244995_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244998_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 244998_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (23.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245017_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245017_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245030_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245030_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245047_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245047_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245051_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245051_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245067_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245067_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245091_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245091_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245110_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245110_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245112_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245112_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (17.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245121_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245121_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245122_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245122_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245127_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245127_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245141_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245141_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245144_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245144_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245150_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245150_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245154_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245154_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (31.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245175_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245175_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245179_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245179_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (14.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245181_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245181_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245184_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245184_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245194_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245194_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245225_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245225_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245233_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245233_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245243_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245243_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245256_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245256_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:07:40.65 +57:11:29.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245273_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245273_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245282_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245282_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245304_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245304_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245328_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245328_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245392_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245392_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245398_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245398_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245424_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245424_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245427_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245427_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (34.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245486_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245494_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245494_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245532_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 245532_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245539_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 245539_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 188873_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194106_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 194106_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:54:37.18 +58:43:45.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24006_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 24006_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 232923_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 232923_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 18194_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 18194_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 29900_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 29900_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 107364_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 107364_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 129729_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 129729_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 133872_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 133872_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 157440_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 157440_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194440_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 194440_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:00.89 +57:54:46.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181028_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 181028_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:38:06.70 +57:12:03.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 90661_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 90661_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 155154_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 155154_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 23:39:54.51 +59:35:02.0 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141556_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 141556_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69458_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 69458_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 45691_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 45691_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 172282_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 172282_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:10:48.43 +57:29:30.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 228987_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 228987_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 108449_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 108449_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (12.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 228248_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 228248_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 188308_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 188308_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:24:11.94 +57:57:10.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 132246_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 132246_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 73832_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 73832_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 187739_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 187739_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143017_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 143017_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:54:56.12 +58:33:46.7 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 95042_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 95042_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 48699_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
The candidate 48699_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053 did not pass the final checks
**** FOUND 00:36:51.31 +63:07:03.0 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 205774_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
Preparing report for the candidate 205774_fd_Cas-02-Q1b1x1_2026-07-13_22-42-09_20.00sec_-0.00C_LIGHTs_0053
make_report_in_HTML.sh Phase 2 (HTML assembly): 20s
make_report_in_HTML.sh TOTAL: 557s
Prepared the HTML report for the field Cas-02-Q1b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:54:55.87 +58:33:48.0
23:39:54.53 +59:34:56.9
23:03:27.30 +57:56:22.5
23:04:18.14 +64:23:31.0
23:11:57.43 +60:33:55.8
00:36:51.69 +63:07:02.1
23:16:27.43 +64:56:10.0
23:25:41.92 +62:16:34.8
00:34:18.96 +64:31:04.4
00:04:21.81 +61:29:34.4
00:29:24.51 +60:49:55.1
00:04:39.25 +60:22:06.3
23:17:41.89 +60:25:56.5
00:36:49.26 +59:12:19.5
23:49:03.75 +59:23:54.4
23:57:21.15 +58:25:10.0
23:58:35.93 +58:25:50.0
23:06:29.57 +56:58:16.1
23:33:34.97 +58:28:11.7
00:34:16.54 +64:30:54.5
23:29:12.13 +61:01:50.8
00:09:36.37 +63:15:35.9
23:05:38.20 +63:30:31.9
23:19:09.37 +63:08:34.7
23:56:15.10 +60:36:10.9
23:33:36.03 +60:24:35.3
23:18:19.01 +60:57:16.5
23:04:27.13 +61:01:48.2
23:21:30.92 +62:54:45.9
23:03:46.58 +63:01:32.2
23:20:02.87 +59:12:28.3
23:28:43.33 +60:24:59.0
23:31:40.51 +61:01:06.9
23:35:19.57 +61:06:50.7
23:52:26.42 +63:10:05.8
23:05:48.67 +64:40:34.1
23:27:46.92 +60:55:56.4
23:50:52.68 +60:43:30.3
23:34:43.26 +60:59:52.1
23:18:46.65 +63:31:48.6
23:59:12.70 +64:48:34.5
23:24:26.91 +60:12:31.9
23:28:50.07 +62:35:47.0
23:29:14.05 +61:01:26.4
00:01:54.00 +61:33:05.1
23:25:54.71 +60:40:05.1
23:02:26.54 +61:09:11.4
23:05:17.91 +61:01:43.4
23:40:02.01 +63:26:39.6
23:10:13.53 +61:18:15.3
23:25:05.95 +59:40:49.1
23:35:45.33 +61:28:25.0
23:04:57.61 +57:15:14.2
23:02:28.03 +60:46:00.3
23:35:46.39 +59:56:05.4
23:25:23.63 +63:24:25.0
00:21:53.86 +61:32:10.3
23:13:11.08 +56:53:51.6
23:04:17.98 +59:38:08.8
23:05:39.09 +59:18:22.8
23:01:46.97 +60:35:18.6
00:05:04.37 +63:58:28.1
23:11:02.90 +61:17:38.3
23:36:56.22 +61:41:19.5
23:00:47.26 +58:49:15.8
23:11:54.98 +61:50:30.4
23:18:41.66 +63:02:16.1
22:56:44.12 +61:32:18.3
23:00:31.92 +58:53:47.4
23:05:51.09 +59:09:57.1
23:07:53.63 +58:08:43.7
23:06:12.29 +58:59:20.5
00:09:30.61 +62:33:39.9
23:04:51.92 +59:25:31.3
23:21:47.23 +60:58:11.1
23:28:44.27 +57:14:04.1
23:47:19.80 +65:40:28.2
23:07:12.81 +56:45:12.0
00:50:31.33 +64:11:25.0
23:21:17.94 +61:29:33.2
22:59:35.70 +59:25:59.6
23:11:01.83 +58:31:23.1
23:05:35.39 +65:07:07.0
00:24:11.96 +61:50:06.3
23:08:50.50 +59:39:19.1
23:26:34.03 +61:18:56.1
23:21:18.07 +57:14:06.9
22:55:47.27 +63:45:33.4
23:01:46.49 +58:21:55.9
00:34:15.48 +62:34:11.1
23:13:42.62 +59:30:39.1
23:09:49.80 +59:48:09.8
23:16:39.20 +62:20:15.4
23:01:03.13 +60:41:20.9
23:11:56.93 +60:47:40.2
23:51:29.41 +66:17:25.5
23:25:07.96 +61:33:21.6
23:10:01.64 +61:30:39.1
23:37:56.85 +57:20:48.0
23:13:24.20 +57:52:02.7
23:04:18.78 +59:42:36.4
00:01:34.47 +61:37:17.0
23:05:45.82 +60:42:39.7
23:16:28.54 +57:51:00.6
23:07:47.86 +58:52:02.4
23:57:24.41 +61:22:12.3
23:23:35.45 +60:08:13.9
23:16:21.30 +59:47:18.8
23:25:06.86 +61:36:46.8
23:03:47.92 +59:20:56.8
23:02:42.31 +59:03:08.8
23:06:41.98 +59:06:53.3
23:08:00.76 +61:02:02.5
23:25:32.63 +61:34:52.9
00:33:09.08 +62:53:16.1
23:25:37.74 +61:35:07.5
00:56:26.90 +60:47:12.3
23:11:18.29 +58:26:37.1
00:20:26.06 +61:51:27.2
23:25:20.59 +61:35:47.5
23:13:46.29 +57:12:01.7
23:25:05.93 +61:36:17.0
23:25:03.81 +61:34:50.3
23:31:36.46 +61:01:45.3
23:25:46.25 +61:34:26.0
23:42:16.71 +57:16:44.2
01:10:28.12 +64:11:40.8
23:57:37.86 +61:02:13.5
00:41:31.53 +65:48:40.9
23:24:06.13 +61:58:40.5
23:53:14.48 +61:56:10.0
23:13:03.38 +57:07:09.4
23:05:07.28 +60:05:42.6
23:17:12.73 +64:44:37.7
23:21:06.09 +65:26:40.2
00:16:34.64 +65:57:06.0
23:26:22.97 +60:42:16.0
23:03:43.23 +59:32:32.8
22:57:14.98 +62:15:45.2
23:04:37.70 +59:50:33.7
23:21:57.66 +62:00:09.7
23:41:29.65 +61:42:37.5
23:29:41.09 +60:54:36.5
23:13:08.83 +57:06:05.8
23:38:48.35 +60:51:21.1
23:24:27.62 +60:27:27.4
23:38:46.52 +58:40:51.5
23:11:14.02 +57:02:22.5
23:03:50.10 +59:35:19.9
23:50:57.25 +60:53:51.4
00:57:49.79 +65:21:33.5
23:46:27.00 +61:57:35.4
00:51:42.51 +56:29:57.2
23:33:01.34 +57:54:14.4
23:17:51.79 +60:54:28.6
23:10:37.62 +56:52:28.8
23:58:59.23 +60:16:00.3
00:01:20.81 +62:01:48.5
23:30:41.64 +57:58:12.5
01:03:05.02 +61:47:29.7
23:49:00.73 +61:15:08.9
23:01:51.50 +63:11:35.4
23:30:16.44 +61:22:28.4
23:07:25.09 +59:13:15.3
00:09:07.10 +65:00:38.3
23:01:05.08 +59:37:26.5
23:43:11.82 +61:32:34.8
00:12:34.35 +62:51:26.1
00:48:12.34 +65:04:57.0
23:32:06.18 +63:58:06.4
23:38:06.23 +57:31:45.0
23:40:00.41 +61:29:05.2
00:40:39.59 +64:16:00.3
23:43:41.78 +62:53:07.2
23:04:17.49 +57:38:50.6
23:46:13.79 +61:56:50.2
23:49:11.86 +64:50:04.0
23:59:19.88 +66:44:15.6
23:33:18.36 +59:56:49.4
23:42:21.74 +57:16:34.1
23:03:21.21 +59:50:13.2
23:57:08.33 +61:22:33.8
23:12:34.73 +62:50:28.9
23:33:18.33 +57:37:18.7
23:47:56.56 +60:41:16.0
23:42:40.74 +61:26:59.2
00:09:14.22 +66:22:23.2
00:11:53.74 +63:00:02.9
23:38:17.32 +58:06:21.7
00:15:01.55 +61:25:35.8
23:23:42.89 +57:11:14.6
23:52:04.28 +63:10:49.7
23:45:38.57 +61:53:16.9
23:56:31.94 +66:45:54.6
23:30:24.26 +61:22:53.1
23:10:49.25 +58:08:56.3
23:15:50.84 +62:49:32.2
23:57:31.13 +61:21:17.1
23:24:20.11 +60:29:55.0
23:18:34.77 +63:55:21.4
23:56:56.74 +61:21:57.5
23:42:02.33 +62:52:58.9
23:43:14.39 +62:36:22.2
23:15:09.65 +63:06:31.4
23:53:09.68 +61:56:08.0
23:27:39.70 +63:28:51.9
23:54:11.43 +60:49:59.5
23:39:38.44 +60:11:27.7
23:00:12.42 +63:02:53.7
23:25:53.58 +57:10:53.1
23:21:04.75 +57:15:40.6
23:28:41.74 +61:08:39.1
23:39:52.09 +62:01:48.1
23:50:43.97 +62:08:09.3
23:49:49.45 +61:04:02.2
01:06:34.81 +65:33:30.2
23:04:13.46 +61:29:08.8
23:41:58.55 +62:42:12.9
23:39:51.02 +62:01:31.5
23:12:07.92 +64:51:57.7
00:28:19.06 +63:41:25.9
23:51:30.44 +59:07:56.7
23:44:47.65 +58:34:54.7
23:55:06.24 +58:46:31.2
23:44:12.58 +63:56:30.5
23:29:24.12 +63:47:43.6
00:14:56.77 +63:42:19.7
23:38:48.86 +58:38:52.1
23:01:58.73 +63:13:35.4
23:37:23.27 +62:43:25.5
23:52:34.12 +61:27:52.6
23:33:18.75 +61:00:15.7
23:32:31.78 +61:10:25.8
23:05:15.68 +60:01:04.4
00:07:39.33 +64:40:01.5
00:05:32.97 +63:52:04.1
23:12:32.93 +62:56:10.6
23:51:44.65 +62:49:13.2
23:51:12.50 +62:06:54.7
########### Completed Cas-02-Q1b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ1.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
23:04:18.14 +64:23:31.0
23:11:57.43 +60:33:55.8
00:36:51.69 +63:07:02.1
23:16:27.43 +64:56:10.0
23:25:41.92 +62:16:34.8
00:34:18.96 +64:31:04.4
00:04:21.81 +61:29:34.4
00:54:55.87 +58:33:48.0
23:03:27.30 +57:56:22.5
23:39:54.53 +59:34:56.9
23:29:12.13 +61:01:50.8
00:09:36.37 +63:15:35.9
23:05:38.20 +63:30:31.9
23:19:09.37 +63:08:34.7
23:56:15.10 +60:36:10.9
23:33:36.03 +60:24:35.3
23:18:19.01 +60:57:16.5
23:04:27.13 +61:01:48.2
23:21:30.92 +62:54:45.9
23:03:46.58 +63:01:32.2
23:20:02.87 +59:12:28.3
23:28:43.33 +60:24:59.0
23:31:40.51 +61:01:06.9
23:35:19.57 +61:06:50.7
23:52:26.42 +63:10:05.8
23:05:48.67 +64:40:34.1
23:27:46.92 +60:55:56.4
23:50:52.68 +60:43:30.3
23:34:43.26 +60:59:52.1
23:18:46.65 +63:31:48.6
23:59:12.70 +64:48:34.5
23:24:26.91 +60:12:31.9
23:28:50.07 +62:35:47.0
23:29:14.05 +61:01:26.4
00:01:54.00 +61:33:05.1
23:25:54.71 +60:40:05.1
23:02:26.54 +61:09:11.4
23:05:17.91 +61:01:43.4
23:40:02.01 +63:26:39.6
23:10:13.53 +61:18:15.3
23:25:05.95 +59:40:49.1
23:35:45.33 +61:28:25.0
23:04:57.61 +57:15:14.2
23:02:28.03 +60:46:00.3
23:35:46.39 +59:56:05.4
23:25:23.63 +63:24:25.0
00:21:53.86 +61:32:10.3
23:13:11.08 +56:53:51.6
23:04:17.98 +59:38:08.8
23:05:39.09 +59:18:22.8
23:01:46.97 +60:35:18.6
00:05:04.37 +63:58:28.1
23:11:02.90 +61:17:38.3
23:36:56.22 +61:41:19.5
23:00:47.26 +58:49:15.8
23:11:54.98 +61:50:30.4
23:18:41.66 +63:02:16.1
22:56:44.12 +61:32:18.3
23:00:31.92 +58:53:47.4
23:05:51.09 +59:09:57.1
23:07:53.63 +58:08:43.7
23:06:12.29 +58:59:20.5
00:09:30.61 +62:33:39.9
23:04:51.92 +59:25:31.3
23:21:47.23 +60:58:11.1
23:28:44.27 +57:14:04.1
23:47:19.80 +65:40:28.2
23:07:12.81 +56:45:12.0
00:50:31.33 +64:11:25.0
23:21:17.94 +61:29:33.2
22:59:35.70 +59:25:59.6
23:11:01.83 +58:31:23.1
23:05:35.39 +65:07:07.0
00:24:11.96 +61:50:06.3
23:08:50.50 +59:39:19.1
23:26:34.03 +61:18:56.1
23:21:18.07 +57:14:06.9
22:55:47.27 +63:45:33.4
23:01:46.49 +58:21:55.9
00:34:15.48 +62:34:11.1
23:13:42.62 +59:30:39.1
23:09:49.80 +59:48:09.8
23:16:39.20 +62:20:15.4
23:01:03.13 +60:41:20.9
23:11:56.93 +60:47:40.2
23:51:29.41 +66:17:25.5
23:25:07.96 +61:33:21.6
23:10:01.64 +61:30:39.1
23:37:56.85 +57:20:48.0
23:13:24.20 +57:52:02.7
23:04:18.78 +59:42:36.4
00:01:34.47 +61:37:17.0
23:05:45.82 +60:42:39.7
23:16:28.54 +57:51:00.6
23:07:47.86 +58:52:02.4
23:57:24.41 +61:22:12.3
23:23:35.45 +60:08:13.9
23:16:21.30 +59:47:18.8
23:25:06.86 +61:36:46.8
23:03:47.92 +59:20:56.8
23:02:42.31 +59:03:08.8
23:06:41.98 +59:06:53.3
23:08:00.76 +61:02:02.5
23:25:32.63 +61:34:52.9
00:33:09.08 +62:53:16.1
23:25:37.74 +61:35:07.5
00:56:26.90 +60:47:12.3
23:11:18.29 +58:26:37.1
00:20:26.06 +61:51:27.2
23:25:20.59 +61:35:47.5
23:13:46.29 +57:12:01.7
23:25:05.93 +61:36:17.0
23:25:03.81 +61:34:50.3
23:31:36.46 +61:01:45.3
23:25:46.25 +61:34:26.0
23:42:16.71 +57:16:44.2
01:10:28.12 +64:11:40.8
23:57:37.86 +61:02:13.5
00:41:31.53 +65:48:40.9
23:24:06.13 +61:58:40.5
23:53:14.48 +61:56:10.0
23:13:03.38 +57:07:09.4
23:05:07.28 +60:05:42.6
23:17:12.73 +64:44:37.7
23:21:06.09 +65:26:40.2
00:16:34.64 +65:57:06.0
23:26:22.97 +60:42:16.0
23:03:43.23 +59:32:32.8
22:57:14.98 +62:15:45.2
23:04:37.70 +59:50:33.7
23:21:57.66 +62:00:09.7
23:41:29.65 +61:42:37.5
23:29:41.09 +60:54:36.5
23:13:08.83 +57:06:05.8
23:38:48.35 +60:51:21.1
23:24:27.62 +60:27:27.4
23:38:46.52 +58:40:51.5
23:11:14.02 +57:02:22.5
23:03:50.10 +59:35:19.9
23:50:57.25 +60:53:51.4
00:57:49.79 +65:21:33.5
23:46:27.00 +61:57:35.4
00:51:42.51 +56:29:57.2
23:33:01.34 +57:54:14.4
23:17:51.79 +60:54:28.6
23:10:37.62 +56:52:28.8
23:58:59.23 +60:16:00.3
00:01:20.81 +62:01:48.5
23:30:41.64 +57:58:12.5
01:03:05.02 +61:47:29.7
23:49:00.73 +61:15:08.9
23:01:51.50 +63:11:35.4
23:30:16.44 +61:22:28.4
23:07:25.09 +59:13:15.3
00:09:07.10 +65:00:38.3
23:01:05.08 +59:37:26.5
23:43:11.82 +61:32:34.8
00:12:34.35 +62:51:26.1
00:48:12.34 +65:04:57.0
23:32:06.18 +63:58:06.4
23:38:06.23 +57:31:45.0
23:40:00.41 +61:29:05.2
00:40:39.59 +64:16:00.3
23:43:41.78 +62:53:07.2
23:04:17.49 +57:38:50.6
23:46:13.79 +61:56:50.2
23:49:11.86 +64:50:04.0
23:59:19.88 +66:44:15.6
23:33:18.36 +59:56:49.4
23:42:21.74 +57:16:34.1
23:03:21.21 +59:50:13.2
23:57:08.33 +61:22:33.8
23:12:34.73 +62:50:28.9
23:33:18.33 +57:37:18.7
23:47:56.56 +60:41:16.0
23:42:40.74 +61:26:59.2
00:09:14.22 +66:22:23.2
00:11:53.74 +63:00:02.9
23:38:17.32 +58:06:21.7
00:15:01.55 +61:25:35.8
23:23:42.89 +57:11:14.6
23:52:04.28 +63:10:49.7
23:45:38.57 +61:53:16.9
23:56:31.94 +66:45:54.6
23:30:24.26 +61:22:53.1
23:10:49.25 +58:08:56.3
23:15:50.84 +62:49:32.2
23:57:31.13 +61:21:17.1
23:24:20.11 +60:29:55.0
23:18:34.77 +63:55:21.4
23:56:56.74 +61:21:57.5
23:42:02.33 +62:52:58.9
23:43:14.39 +62:36:22.2
23:15:09.65 +63:06:31.4
23:53:09.68 +61:56:08.0
23:27:39.70 +63:28:51.9
23:54:11.43 +60:49:59.5
23:39:38.44 +60:11:27.7
23:00:12.42 +63:02:53.7
23:25:53.58 +57:10:53.1
23:21:04.75 +57:15:40.6
23:28:41.74 +61:08:39.1
23:39:52.09 +62:01:48.1
23:50:43.97 +62:08:09.3
23:49:49.45 +61:04:02.2
01:06:34.81 +65:33:30.2
23:04:13.46 +61:29:08.8
23:41:58.55 +62:42:12.9
23:39:51.02 +62:01:31.5
23:12:07.92 +64:51:57.7
00:28:19.06 +63:41:25.9
23:51:30.44 +59:07:56.7
23:44:47.65 +58:34:54.7
23:55:06.24 +58:46:31.2
23:44:12.58 +63:56:30.5
23:29:24.12 +63:47:43.6
00:14:56.77 +63:42:19.7
23:38:48.86 +58:38:52.1
23:01:58.73 +63:13:35.4
23:37:23.27 +62:43:25.5
23:52:34.12 +61:27:52.6
23:33:18.75 +61:00:15.7
23:32:31.78 +61:10:25.8
23:05:15.68 +60:01:04.4
23:58:35.93 +58:25:50.0
00:34:16.54 +64:30:54.5
00:07:39.33 +64:40:01.5
00:29:24.51 +60:49:55.1
23:17:41.89 +60:25:56.5
23:49:03.75 +59:23:54.4
23:51:12.50 +62:06:54.7
00:36:49.26 +59:12:19.5
23:12:32.93 +62:56:10.6
00:05:32.97 +63:52:04.1
23:33:34.97 +58:28:11.7
00:04:39.25 +60:22:06.3
23:51:44.65 +62:49:13.2
23:57:21.15 +58:25:10.0
23:06:29.57 +56:58:16.1
###################################################################################
23:04:18.14 +64:23:31.0 -- not an asteroid (will add it to exclusion list)
23:11:57.43 +60:33:55.8 -- not an asteroid (will add it to exclusion list)
00:36:51.69 +63:07:02.1 -- not an asteroid (will add it to exclusion list)
23:16:27.43 +64:56:10.0 -- not an asteroid (will add it to exclusion list)
23:25:41.92 +62:16:34.8 -- not an asteroid (will add it to exclusion list)
00:34:18.96 +64:31:04.4 -- not an asteroid (will add it to exclusion list)
00:04:21.81 +61:29:34.4 -- not an asteroid (will add it to exclusion list)
00:54:55.87 +58:33:48.0 -- not an asteroid (will add it to exclusion list)
23:03:27.30 +57:56:22.5 -- not an asteroid (will add it to exclusion list)
23:39:54.53 +59:34:56.9 -- not an asteroid (will add it to exclusion list)
23:29:12.13 +61:01:50.8 -- not an asteroid (will add it to exclusion list)
00:09:36.37 +63:15:35.9 -- not an asteroid (will add it to exclusion list)
23:05:38.20 +63:30:31.9 -- not an asteroid (will add it to exclusion list)
23:19:09.37 +63:08:34.7 -- not an asteroid (will add it to exclusion list)
23:56:15.10 +60:36:10.9 -- not an asteroid (will add it to exclusion list)
23:33:36.03 +60:24:35.3 -- not an asteroid (will add it to exclusion list)
23:18:19.01 +60:57:16.5 -- not an asteroid (will add it to exclusion list)
23:04:27.13 +61:01:48.2 -- not an asteroid (will add it to exclusion list)
23:21:30.92 +62:54:45.9 -- not an asteroid (will add it to exclusion list)
23:03:46.58 +63:01:32.2 -- not an asteroid (will add it to exclusion list)
23:20:02.87 +59:12:28.3 -- not an asteroid (will add it to exclusion list)
23:28:43.33 +60:24:59.0 -- not an asteroid (will add it to exclusion list)
23:31:40.51 +61:01:06.9 -- not an asteroid (will add it to exclusion list)
23:35:19.57 +61:06:50.7 -- not an asteroid (will add it to exclusion list)
23:52:26.42 +63:10:05.8 -- not an asteroid (will add it to exclusion list)
23:05:48.67 +64:40:34.1 -- not an asteroid (will add it to exclusion list)
23:27:46.92 +60:55:56.4 -- not an asteroid (will add it to exclusion list)
23:50:52.68 +60:43:30.3 -- not an asteroid (will add it to exclusion list)
23:34:43.26 +60:59:52.1 -- not an asteroid (will add it to exclusion list)
23:18:46.65 +63:31:48.6 -- not an asteroid (will add it to exclusion list)
23:59:12.70 +64:48:34.5 -- not an asteroid (will add it to exclusion list)
23:24:26.91 +60:12:31.9 -- not an asteroid (will add it to exclusion list)
23:28:50.07 +62:35:47.0 -- not an asteroid (will add it to exclusion list)
23:29:14.05 +61:01:26.4 -- not an asteroid (will add it to exclusion list)
00:01:54.00 +61:33:05.1 -- not an asteroid (will add it to exclusion list)
23:25:54.71 +60:40:05.1 -- not an asteroid (will add it to exclusion list)
23:02:26.54 +61:09:11.4 -- not an asteroid (will add it to exclusion list)
23:05:17.91 +61:01:43.4 -- not an asteroid (will add it to exclusion list)
23:40:02.01 +63:26:39.6 -- not an asteroid (will add it to exclusion list)
23:10:13.53 +61:18:15.3 -- not an asteroid (will add it to exclusion list)
23:25:05.95 +59:40:49.1 -- not an asteroid (will add it to exclusion list)
23:35:45.33 +61:28:25.0 -- not an asteroid (will add it to exclusion list)
23:04:57.61 +57:15:14.2 -- not an asteroid (will add it to exclusion list)
23:02:28.03 +60:46:00.3 -- not an asteroid (will add it to exclusion list)
23:35:46.39 +59:56:05.4 -- not an asteroid (will add it to exclusion list)
23:25:23.63 +63:24:25.0 -- not an asteroid (will add it to exclusion list)
00:21:53.86 +61:32:10.3 -- not an asteroid (will add it to exclusion list)
23:13:11.08 +56:53:51.6 -- not an asteroid (will add it to exclusion list)
23:04:17.98 +59:38:08.8 -- not an asteroid (will add it to exclusion list)
23:05:39.09 +59:18:22.8 -- not an asteroid (will add it to exclusion list)
23:01:46.97 +60:35:18.6 -- not an asteroid (will add it to exclusion list)
00:05:04.37 +63:58:28.1 -- not an asteroid (will add it to exclusion list)
23:11:02.90 +61:17:38.3 -- not an asteroid (will add it to exclusion list)
23:36:56.22 +61:41:19.5 -- not an asteroid (will add it to exclusion list)
23:00:47.26 +58:49:15.8 -- not an asteroid (will add it to exclusion list)
23:11:54.98 +61:50:30.4 -- not an asteroid (will add it to exclusion list)
23:18:41.66 +63:02:16.1 -- not an asteroid (will add it to exclusion list)
22:56:44.12 +61:32:18.3 -- not an asteroid (will add it to exclusion list)
23:00:31.92 +58:53:47.4 -- not an asteroid (will add it to exclusion list)
23:05:51.09 +59:09:57.1 -- not an asteroid (will add it to exclusion list)
23:07:53.63 +58:08:43.7 -- not an asteroid (will add it to exclusion list)
23:06:12.29 +58:59:20.5 -- not an asteroid (will add it to exclusion list)
00:09:30.61 +62:33:39.9 -- not an asteroid (will add it to exclusion list)
23:04:51.92 +59:25:31.3 -- not an asteroid (will add it to exclusion list)
23:21:47.23 +60:58:11.1 -- not an asteroid (will add it to exclusion list)
23:28:44.27 +57:14:04.1 -- not an asteroid (will add it to exclusion list)
23:47:19.80 +65:40:28.2 -- not an asteroid (will add it to exclusion list)
23:07:12.81 +56:45:12.0 -- not an asteroid (will add it to exclusion list)
00:50:31.33 +64:11:25.0 -- not an asteroid (will add it to exclusion list)
23:21:17.94 +61:29:33.2 -- not an asteroid (will add it to exclusion list)
22:59:35.70 +59:25:59.6 -- not an asteroid (will add it to exclusion list)
23:11:01.83 +58:31:23.1 -- not an asteroid (will add it to exclusion list)
23:05:35.39 +65:07:07.0 -- not an asteroid (will add it to exclusion list)
00:24:11.96 +61:50:06.3 -- not an asteroid (will add it to exclusion list)
23:08:50.50 +59:39:19.1 -- not an asteroid (will add it to exclusion list)
23:26:34.03 +61:18:56.1 -- not an asteroid (will add it to exclusion list)
23:21:18.07 +57:14:06.9 -- not an asteroid (will add it to exclusion list)
22:55:47.27 +63:45:33.4 -- not an asteroid (will add it to exclusion list)
23:01:46.49 +58:21:55.9 -- not an asteroid (will add it to exclusion list)
00:34:15.48 +62:34:11.1 -- not an asteroid (will add it to exclusion list)
23:13:42.62 +59:30:39.1 -- not an asteroid (will add it to exclusion list)
23:09:49.80 +59:48:09.8 -- not an asteroid (will add it to exclusion list)
23:16:39.20 +62:20:15.4 -- not an asteroid (will add it to exclusion list)
23:01:03.13 +60:41:20.9 -- not an asteroid (will add it to exclusion list)
23:11:56.93 +60:47:40.2 -- not an asteroid (will add it to exclusion list)
23:51:29.41 +66:17:25.5 -- not an asteroid (will add it to exclusion list)
23:25:07.96 +61:33:21.6 -- not an asteroid (will add it to exclusion list)
23:10:01.64 +61:30:39.1 -- not an asteroid (will add it to exclusion list)
23:37:56.85 +57:20:48.0 -- not an asteroid (will add it to exclusion list)
23:13:24.20 +57:52:02.7 -- not an asteroid (will add it to exclusion list)
23:04:18.78 +59:42:36.4 -- not an asteroid (will add it to exclusion list)
00:01:34.47 +61:37:17.0 -- not an asteroid (will add it to exclusion list)
23:05:45.82 +60:42:39.7 -- not an asteroid (will add it to exclusion list)
23:16:28.54 +57:51:00.6 -- not an asteroid (will add it to exclusion list)
23:07:47.86 +58:52:02.4 -- not an asteroid (will add it to exclusion list)
23:57:24.41 +61:22:12.3 -- not an asteroid (will add it to exclusion list)
23:23:35.45 +60:08:13.9 -- not an asteroid (will add it to exclusion list)
23:16:21.30 +59:47:18.8 -- not an asteroid (will add it to exclusion list)
23:25:06.86 +61:36:46.8 -- not an asteroid (will add it to exclusion list)
23:03:47.92 +59:20:56.8 -- not an asteroid (will add it to exclusion list)
23:02:42.31 +59:03:08.8 -- not an asteroid (will add it to exclusion list)
23:06:41.98 +59:06:53.3 -- not an asteroid (will add it to exclusion list)
23:08:00.76 +61:02:02.5 -- not an asteroid (will add it to exclusion list)
23:25:32.63 +61:34:52.9 -- not an asteroid (will add it to exclusion list)
00:33:09.08 +62:53:16.1 -- not an asteroid (will add it to exclusion list)
23:25:37.74 +61:35:07.5 -- not an asteroid (will add it to exclusion list)
00:56:26.90 +60:47:12.3 -- not an asteroid (will add it to exclusion list)
23:11:18.29 +58:26:37.1 -- not an asteroid (will add it to exclusion list)
00:20:26.06 +61:51:27.2 -- not an asteroid (will add it to exclusion list)
23:25:20.59 +61:35:47.5 -- not an asteroid (will add it to exclusion list)
23:13:46.29 +57:12:01.7 -- not an asteroid (will add it to exclusion list)
23:25:05.93 +61:36:17.0 -- not an asteroid (will add it to exclusion list)
23:25:03.81 +61:34:50.3 -- not an asteroid (will add it to exclusion list)
23:31:36.46 +61:01:45.3 -- not an asteroid (will add it to exclusion list)
23:25:46.25 +61:34:26.0 -- not an asteroid (will add it to exclusion list)
23:42:16.71 +57:16:44.2 -- not an asteroid (will add it to exclusion list)
01:10:28.12 +64:11:40.8 -- not an asteroid (will add it to exclusion list)
23:57:37.86 +61:02:13.5 -- not an asteroid (will add it to exclusion list)
00:41:31.53 +65:48:40.9 -- not an asteroid (will add it to exclusion list)
23:24:06.13 +61:58:40.5 -- not an asteroid (will add it to exclusion list)
23:53:14.48 +61:56:10.0 -- not an asteroid (will add it to exclusion list)
23:13:03.38 +57:07:09.4 -- not an asteroid (will add it to exclusion list)
23:05:07.28 +60:05:42.6 -- not an asteroid (will add it to exclusion list)
23:17:12.73 +64:44:37.7 -- not an asteroid (will add it to exclusion list)
23:21:06.09 +65:26:40.2 -- not an asteroid (will add it to exclusion list)
00:16:34.64 +65:57:06.0 -- not an asteroid (will add it to exclusion list)
23:26:22.97 +60:42:16.0 -- not an asteroid (will add it to exclusion list)
23:03:43.23 +59:32:32.8 -- not an asteroid (will add it to exclusion list)
22:57:14.98 +62:15:45.2 -- not an asteroid (will add it to exclusion list)
23:04:37.70 +59:50:33.7 -- not an asteroid (will add it to exclusion list)
23:21:57.66 +62:00:09.7 -- not an asteroid (will add it to exclusion list)
23:41:29.65 +61:42:37.5 -- not an asteroid (will add it to exclusion list)
23:29:41.09 +60:54:36.5 -- not an asteroid (will add it to exclusion list)
23:13:08.83 +57:06:05.8 -- not an asteroid (will add it to exclusion list)
23:38:48.35 +60:51:21.1 -- not an asteroid (will add it to exclusion list)
23:24:27.62 +60:27:27.4 -- not an asteroid (will add it to exclusion list)
23:38:46.52 +58:40:51.5 -- not an asteroid (will add it to exclusion list)
23:11:14.02 +57:02:22.5 -- not an asteroid (will add it to exclusion list)
23:03:50.10 +59:35:19.9 -- not an asteroid (will add it to exclusion list)
23:50:57.25 +60:53:51.4 -- not an asteroid (will add it to exclusion list)
00:57:49.79 +65:21:33.5 -- not an asteroid (will add it to exclusion list)
23:46:27.00 +61:57:35.4 -- not an asteroid (will add it to exclusion list)
00:51:42.51 +56:29:57.2 -- not an asteroid (will add it to exclusion list)
23:33:01.34 +57:54:14.4 -- not an asteroid (will add it to exclusion list)
23:17:51.79 +60:54:28.6 -- not an asteroid (will add it to exclusion list)
23:10:37.62 +56:52:28.8 -- not an asteroid (will add it to exclusion list)
23:58:59.23 +60:16:00.3 -- not an asteroid (will add it to exclusion list)
00:01:20.81 +62:01:48.5 -- not an asteroid (will add it to exclusion list)
23:30:41.64 +57:58:12.5 -- not an asteroid (will add it to exclusion list)
01:03:05.02 +61:47:29.7 -- not an asteroid (will add it to exclusion list)
23:49:00.73 +61:15:08.9 -- not an asteroid (will add it to exclusion list)
23:01:51.50 +63:11:35.4 -- not an asteroid (will add it to exclusion list)
23:30:16.44 +61:22:28.4 -- not an asteroid (will add it to exclusion list)
23:07:25.09 +59:13:15.3 -- not an asteroid (will add it to exclusion list)
00:09:07.10 +65:00:38.3 -- not an asteroid (will add it to exclusion list)
23:01:05.08 +59:37:26.5 -- not an asteroid (will add it to exclusion list)
23:43:11.82 +61:32:34.8 -- not an asteroid (will add it to exclusion list)
00:12:34.35 +62:51:26.1 -- not an asteroid (will add it to exclusion list)
00:48:12.34 +65:04:57.0 -- not an asteroid (will add it to exclusion list)
23:32:06.18 +63:58:06.4 -- not an asteroid (will add it to exclusion list)
23:38:06.23 +57:31:45.0 -- not an asteroid (will add it to exclusion list)
23:40:00.41 +61:29:05.2 -- not an asteroid (will add it to exclusion list)
00:40:39.59 +64:16:00.3 -- not an asteroid (will add it to exclusion list)
23:43:41.78 +62:53:07.2 -- not an asteroid (will add it to exclusion list)
23:04:17.49 +57:38:50.6 -- not an asteroid (will add it to exclusion list)
23:46:13.79 +61:56:50.2 -- not an asteroid (will add it to exclusion list)
23:49:11.86 +64:50:04.0 -- not an asteroid (will add it to exclusion list)
23:59:19.88 +66:44:15.6 -- not an asteroid (will add it to exclusion list)
23:33:18.36 +59:56:49.4 -- not an asteroid (will add it to exclusion list)
23:42:21.74 +57:16:34.1 -- not an asteroid (will add it to exclusion list)
23:03:21.21 +59:50:13.2 -- not an asteroid (will add it to exclusion list)
23:57:08.33 +61:22:33.8 -- not an asteroid (will add it to exclusion list)
23:12:34.73 +62:50:28.9 -- not an asteroid (will add it to exclusion list)
23:33:18.33 +57:37:18.7 -- not an asteroid (will add it to exclusion list)
23:47:56.56 +60:41:16.0 -- not an asteroid (will add it to exclusion list)
23:42:40.74 +61:26:59.2 -- not an asteroid (will add it to exclusion list)
00:09:14.22 +66:22:23.2 -- not an asteroid (will add it to exclusion list)
00:11:53.74 +63:00:02.9 -- not an asteroid (will add it to exclusion list)
23:38:17.32 +58:06:21.7 -- not an asteroid (will add it to exclusion list)
00:15:01.55 +61:25:35.8 -- not an asteroid (will add it to exclusion list)
23:23:42.89 +57:11:14.6 -- not an asteroid (will add it to exclusion list)
23:52:04.28 +63:10:49.7 -- not an asteroid (will add it to exclusion list)
23:45:38.57 +61:53:16.9 -- not an asteroid (will add it to exclusion list)
23:56:31.94 +66:45:54.6 -- not an asteroid (will add it to exclusion list)
23:30:24.26 +61:22:53.1 -- not an asteroid (will add it to exclusion list)
23:10:49.25 +58:08:56.3 -- not an asteroid (will add it to exclusion list)
23:15:50.84 +62:49:32.2 -- not an asteroid (will add it to exclusion list)
23:57:31.13 +61:21:17.1 -- not an asteroid (will add it to exclusion list)
23:24:20.11 +60:29:55.0 -- not an asteroid (will add it to exclusion list)
23:18:34.77 +63:55:21.4 -- not an asteroid (will add it to exclusion list)
23:56:56.74 +61:21:57.5 -- not an asteroid (will add it to exclusion list)
23:42:02.33 +62:52:58.9 -- not an asteroid (will add it to exclusion list)
23:43:14.39 +62:36:22.2 -- not an asteroid (will add it to exclusion list)
23:15:09.65 +63:06:31.4 -- not an asteroid (will add it to exclusion list)
23:53:09.68 +61:56:08.0 -- not an asteroid (will add it to exclusion list)
23:27:39.70 +63:28:51.9 -- not an asteroid (will add it to exclusion list)
23:54:11.43 +60:49:59.5 -- not an asteroid (will add it to exclusion list)
23:39:38.44 +60:11:27.7 -- not an asteroid (will add it to exclusion list)
23:00:12.42 +63:02:53.7 -- not an asteroid (will add it to exclusion list)
23:25:53.58 +57:10:53.1 -- not an asteroid (will add it to exclusion list)
23:21:04.75 +57:15:40.6 -- not an asteroid (will add it to exclusion list)
23:28:41.74 +61:08:39.1 -- not an asteroid (will add it to exclusion list)
23:39:52.09 +62:01:48.1 -- not an asteroid (will add it to exclusion list)
23:50:43.97 +62:08:09.3 -- not an asteroid (will add it to exclusion list)
23:49:49.45 +61:04:02.2 -- not an asteroid (will add it to exclusion list)
01:06:34.81 +65:33:30.2 -- not an asteroid (will add it to exclusion list)
23:04:13.46 +61:29:08.8 -- not an asteroid (will add it to exclusion list)
23:41:58.55 +62:42:12.9 -- not an asteroid (will add it to exclusion list)
23:39:51.02 +62:01:31.5 -- not an asteroid (will add it to exclusion list)
23:12:07.92 +64:51:57.7 -- not an asteroid (will add it to exclusion list)
00:28:19.06 +63:41:25.9 -- not an asteroid (will add it to exclusion list)
23:51:30.44 +59:07:56.7 -- not an asteroid (will add it to exclusion list)
23:44:47.65 +58:34:54.7 -- not an asteroid (will add it to exclusion list)
23:55:06.24 +58:46:31.2 -- not an asteroid (will add it to exclusion list)
23:44:12.58 +63:56:30.5 -- not an asteroid (will add it to exclusion list)
23:29:24.12 +63:47:43.6 -- not an asteroid (will add it to exclusion list)
00:14:56.77 +63:42:19.7 -- not an asteroid (will add it to exclusion list)
23:38:48.86 +58:38:52.1 -- not an asteroid (will add it to exclusion list)
23:01:58.73 +63:13:35.4 -- not an asteroid (will add it to exclusion list)
23:37:23.27 +62:43:25.5 -- not an asteroid (will add it to exclusion list)
23:52:34.12 +61:27:52.6 -- not an asteroid (will add it to exclusion list)
23:33:18.75 +61:00:15.7 -- not an asteroid (will add it to exclusion list)
23:32:31.78 +61:10:25.8 -- not an asteroid (will add it to exclusion list)
23:05:15.68 +60:01:04.4 -- not an asteroid (will add it to exclusion list)
23:58:35.93 +58:25:50.0 -- not an asteroid (will add it to exclusion list)
00:34:16.54 +64:30:54.5 -- not an asteroid (will add it to exclusion list)
00:07:39.33 +64:40:01.5 -- not an asteroid (will add it to exclusion list)
00:29:24.51 +60:49:55.1 -- not an asteroid (will add it to exclusion list)
23:17:41.89 +60:25:56.5 -- not an asteroid (will add it to exclusion list)
23:49:03.75 +59:23:54.4 -- not an asteroid (will add it to exclusion list)
23:51:12.50 +62:06:54.7 -- not an asteroid (will add it to exclusion list)
00:36:49.26 +59:12:19.5 -- not an asteroid (will add it to exclusion list)
23:12:32.93 +62:56:10.6 -- not an asteroid (will add it to exclusion list)
00:05:32.97 +63:52:04.1 -- not an asteroid (will add it to exclusion list)
23:33:34.97 +58:28:11.7 -- not an asteroid (will add it to exclusion list)
00:04:39.25 +60:22:06.3 -- not an asteroid (will add it to exclusion list)
23:51:44.65 +62:49:13.2 -- not an asteroid (will add it to exclusion list)
23:57:21.15 +58:25:10.0 -- not an asteroid (will add it to exclusion list)
23:06:29.57 +56:58:16.1 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:01:20.81 +62:01:48.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:34.47 +61:37:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:54.00 +61:33:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:21.81 +61:29:34.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:39.25 +60:22:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:04.37 +63:58:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:32.97 +63:52:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:39.33 +64:40:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:07.10 +65:00:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:14.22 +66:22:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:30.61 +62:33:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:36.37 +63:15:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:53.74 +63:00:02.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:34.35 +62:51:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:56.77 +63:42:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:01.55 +61:25:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:34.64 +65:57:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:26.06 +61:51:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:53.86 +61:32:10.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:11.96 +61:50:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:19.06 +63:41:25.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:24.51 +60:49:55.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:33:09.08 +62:53:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:15.48 +62:34:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:16.54 +64:30:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:18.96 +64:31:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:49.26 +59:12:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:51.69 +63:07:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:40:39.59 +64:16:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:31.53 +65:48:40.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:48:12.34 +65:04:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:50:31.33 +64:11:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:51:42.51 +56:29:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:54:55.87 +58:33:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:56:26.90 +60:47:12.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:57:49.79 +65:21:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
01:03:05.02 +61:47:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
01:06:34.81 +65:33:30.2 -- does not seem to be a hot pixel (will add it to exclusion list)
01:10:28.12 +64:11:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
22:55:47.27 +63:45:33.4 -- does not seem to be a hot pixel (will add it to exclusion list)
22:56:44.12 +61:32:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
22:57:14.98 +62:15:45.2 -- does not seem to be a hot pixel (will add it to exclusion list)
22:59:35.70 +59:25:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:00:12.42 +63:02:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:00:31.92 +58:53:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:00:47.26 +58:49:15.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:03.13 +60:41:20.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:05.08 +59:37:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:46.49 +58:21:55.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:46.97 +60:35:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:51.50 +63:11:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:01:58.73 +63:13:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:02:26.54 +61:09:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:02:28.03 +60:46:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:02:42.31 +59:03:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:21.21 +59:50:13.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:27.30 +57:56:22.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:43.23 +59:32:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:46.58 +63:01:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:47.92 +59:20:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:03:50.10 +59:35:19.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:13.46 +61:29:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:17.49 +57:38:50.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:17.98 +59:38:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:18.14 +64:23:31.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:18.78 +59:42:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:27.13 +61:01:48.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:37.70 +59:50:33.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:51.92 +59:25:31.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:04:57.61 +57:15:14.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:07.28 +60:05:42.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:15.68 +60:01:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:17.91 +61:01:43.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:35.39 +65:07:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:38.20 +63:30:31.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:39.09 +59:18:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:45.82 +60:42:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:48.67 +64:40:34.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:05:51.09 +59:09:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:06:12.29 +58:59:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:06:29.57 +56:58:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:06:41.98 +59:06:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:07:12.81 +56:45:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:07:25.09 +59:13:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:07:47.86 +58:52:02.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:07:53.63 +58:08:43.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:08:00.76 +61:02:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:08:50.50 +59:39:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:09:49.80 +59:48:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:01.64 +61:30:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:13.53 +61:18:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:37.62 +56:52:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:10:49.25 +58:08:56.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:01.83 +58:31:23.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:02.90 +61:17:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:14.02 +57:02:22.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:18.29 +58:26:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:54.98 +61:50:30.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:56.93 +60:47:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:11:57.43 +60:33:55.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:07.92 +64:51:57.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:32.93 +62:56:10.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:12:34.73 +62:50:28.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:03.38 +57:07:09.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:08.83 +57:06:05.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:11.08 +56:53:51.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:24.20 +57:52:02.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:42.62 +59:30:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:13:46.29 +57:12:01.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:09.65 +63:06:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:15:50.84 +62:49:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:21.30 +59:47:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:27.43 +64:56:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:28.54 +57:51:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:16:39.20 +62:20:15.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:12.73 +64:44:37.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:41.89 +60:25:56.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:17:51.79 +60:54:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:19.01 +60:57:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:34.77 +63:55:21.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:41.66 +63:02:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:18:46.65 +63:31:48.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:19:09.37 +63:08:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:20:02.87 +59:12:28.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:04.75 +57:15:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:06.09 +65:26:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:17.94 +61:29:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:18.07 +57:14:06.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:30.92 +62:54:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:47.23 +60:58:11.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:57.66 +62:00:09.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:35.45 +60:08:13.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:42.89 +57:11:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:06.13 +61:58:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:20.11 +60:29:55.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:26.91 +60:12:31.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:27.62 +60:27:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:03.81 +61:34:50.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:05.93 +61:36:17.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:05.95 +59:40:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:06.86 +61:36:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:07.96 +61:33:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:20.59 +61:35:47.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:23.63 +63:24:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:32.63 +61:34:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:37.74 +61:35:07.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:41.92 +62:16:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:46.25 +61:34:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:53.58 +57:10:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:54.71 +60:40:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:22.97 +60:42:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:34.03 +61:18:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:39.70 +63:28:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:46.92 +60:55:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:41.74 +61:08:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:43.33 +60:24:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:44.27 +57:14:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:50.07 +62:35:47.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:12.13 +61:01:50.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:14.05 +61:01:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:24.12 +63:47:43.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:41.09 +60:54:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:16.44 +61:22:28.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:24.26 +61:22:53.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:41.64 +57:58:12.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:36.46 +61:01:45.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:40.51 +61:01:06.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:06.18 +63:58:06.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:31.78 +61:10:25.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:01.34 +57:54:14.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:18.33 +57:37:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:18.36 +59:56:49.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:18.75 +61:00:15.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:34.97 +58:28:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:36.03 +60:24:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:43.26 +60:59:52.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:19.57 +61:06:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:45.33 +61:28:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:46.39 +59:56:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:56.22 +61:41:19.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:23.27 +62:43:25.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:56.85 +57:20:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:06.23 +57:31:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:17.32 +58:06:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:46.52 +58:40:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:48.35 +60:51:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:48.86 +58:38:52.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:38.44 +60:11:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:51.02 +62:01:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:52.09 +62:01:48.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:54.53 +59:34:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:00.41 +61:29:05.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:02.01 +63:26:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:29.65 +61:42:37.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:58.55 +62:42:12.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:02.33 +62:52:58.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:16.71 +57:16:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:21.74 +57:16:34.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:40.74 +61:26:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:11.82 +61:32:34.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:14.39 +62:36:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:41.78 +62:53:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:12.58 +63:56:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:47.65 +58:34:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:45:38.57 +61:53:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:13.79 +61:56:50.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:27.00 +61:57:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:19.80 +65:40:28.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:56.56 +60:41:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:00.73 +61:15:08.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:03.75 +59:23:54.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:11.86 +64:50:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:49.45 +61:04:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:43.97 +62:08:09.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:52.68 +60:43:30.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:57.25 +60:53:51.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:12.50 +62:06:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:29.41 +66:17:25.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:30.44 +59:07:56.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:44.65 +62:49:13.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:04.28 +63:10:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:26.42 +63:10:05.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:34.12 +61:27:52.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:09.68 +61:56:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:14.48 +61:56:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:11.43 +60:49:59.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:06.24 +58:46:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:15.10 +60:36:10.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:31.94 +66:45:54.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:56.74 +61:21:57.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:08.33 +61:22:33.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:21.15 +58:25:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:24.41 +61:22:12.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:31.13 +61:21:17.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:37.86 +61:02:13.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:35.93 +58:25:50.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:59.23 +60:16:00.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:12.70 +64:48:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:19.88 +66:44:15.6 -- 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:01:20.81 +62:01:48.5 -- not a known variable star
00:01:34.47 +61:37:17.0 -- not a known variable star
00:01:54.00 +61:33:05.1 -- not a known variable star
00:04:21.81 +61:29:34.4 -- a known variable star
00:04:39.25 +60:22:06.3 -- a known variable star
00:05:04.37 +63:58:28.1 -- not a known variable star
00:05:32.97 +63:52:04.1 -- not a known variable star
00:07:39.33 +64:40:01.5 -- not a known variable star
00:09:07.10 +65:00:38.3 -- not a known variable star
00:09:14.22 +66:22:23.2 -- not a known variable star
00:09:30.61 +62:33:39.9 -- not a known variable star
00:09:36.37 +63:15:35.9 -- not a known variable star
00:11:53.74 +63:00:02.9 -- a known variable star
00:12:34.35 +62:51:26.1 -- not a known variable star
00:14:56.77 +63:42:19.7 -- not a known variable star
00:15:01.55 +61:25:35.8 -- not a known variable star
00:16:34.64 +65:57:06.0 -- not a known variable star
00:20:26.06 +61:51:27.2 -- not a known variable star
00:21:53.86 +61:32:10.3 -- not a known variable star
00:24:11.96 +61:50:06.3 -- not a known variable star
00:28:19.06 +63:41:25.9 -- not a known variable star
00:29:24.51 +60:49:55.1 -- a known variable star
00:33:09.08 +62:53:16.1 -- not a known variable star
00:34:15.48 +62:34:11.1 -- not a known variable star
00:34:16.54 +64:30:54.5 -- not a known variable star
00:34:18.96 +64:31:04.4 -- not a known variable star
00:36:49.26 +59:12:19.5 -- a known variable star
00:36:51.69 +63:07:02.1 -- not a known variable star
00:40:39.59 +64:16:00.3 -- not a known variable star
00:41:31.53 +65:48:40.9 -- a known variable star
00:48:12.34 +65:04:57.0 -- not a known variable star
00:50:31.33 +64:11:25.0 -- not a known variable star
00:51:42.51 +56:29:57.2 -- a known variable star
00:54:55.87 +58:33:48.0 -- a known variable star
00:56:26.90 +60:47:12.3 -- a known variable star
00:57:49.79 +65:21:33.5 -- not a known variable star
01:03:05.02 +61:47:29.7 -- not a known variable star
01:06:34.81 +65:33:30.2 -- not a known variable star
01:10:28.12 +64:11:40.8 -- not a known variable star
22:55:47.27 +63:45:33.4 -- not a known variable star
22:56:44.12 +61:32:18.3 -- not a known variable star
22:57:14.98 +62:15:45.2 -- a known variable star
22:59:35.70 +59:25:59.6 -- a known variable star
23:00:12.42 +63:02:53.7 -- not a known variable star
23:00:31.92 +58:53:47.4 -- not a known variable star
23:00:47.26 +58:49:15.8 -- not a known variable star
23:01:03.13 +60:41:20.9 -- not a known variable star
23:01:05.08 +59:37:26.5 -- not a known variable star
23:01:46.49 +58:21:55.9 -- a known variable star
23:01:46.97 +60:35:18.6 -- not a known variable star
23:01:51.50 +63:11:35.4 -- not a known variable star
23:01:58.73 +63:13:35.4 -- not a known variable star
23:02:26.54 +61:09:11.4 -- not a known variable star
23:02:28.03 +60:46:00.3 -- not a known variable star
23:02:42.31 +59:03:08.8 -- not a known variable star
23:03:21.21 +59:50:13.2 -- not a known variable star
23:03:27.30 +57:56:22.5 -- not a known variable star
23:03:43.23 +59:32:32.8 -- not a known variable star
23:03:46.58 +63:01:32.2 -- not a known variable star
23:03:47.92 +59:20:56.8 -- not a known variable star
23:03:50.10 +59:35:19.9 -- not a known variable star
23:04:13.46 +61:29:08.8 -- not a known variable star
23:04:17.49 +57:38:50.6 -- not a known variable star
23:04:17.98 +59:38:08.8 -- not a known variable star
23:04:18.14 +64:23:31.0 -- a known variable star
23:04:18.78 +59:42:36.4 -- not a known variable star
23:04:27.13 +61:01:48.2 -- not a known variable star
23:04:37.70 +59:50:33.7 -- not a known variable star
23:04:51.92 +59:25:31.3 -- not a known variable star
23:04:57.61 +57:15:14.2 -- a known variable star
23:05:07.28 +60:05:42.6 -- not a known variable star
23:05:15.68 +60:01:04.4 -- not a known variable star
23:05:17.91 +61:01:43.4 -- not a known variable star
23:05:35.39 +65:07:07.0 -- not a known variable star
23:05:38.20 +63:30:31.9 -- not a known variable star
23:05:39.09 +59:18:22.8 -- not a known variable star
23:05:45.82 +60:42:39.7 -- not a known variable star
23:05:48.67 +64:40:34.1 -- a known variable star
23:05:51.09 +59:09:57.1 -- not a known variable star
23:06:12.29 +58:59:20.5 -- a known variable star
23:06:29.57 +56:58:16.1 -- not a known variable star
23:06:41.98 +59:06:53.3 -- not a known variable star
23:07:12.81 +56:45:12.0 -- not a known variable star
23:07:25.09 +59:13:15.3 -- not a known variable star
23:07:47.86 +58:52:02.4 -- not a known variable star
23:07:53.63 +58:08:43.7 -- not a known variable star
23:08:00.76 +61:02:02.5 -- not a known variable star
23:08:50.50 +59:39:19.1 -- not a known variable star
23:09:49.80 +59:48:09.8 -- not a known variable star
23:10:01.64 +61:30:39.1 -- not a known variable star
23:10:13.53 +61:18:15.3 -- not a known variable star
23:10:37.62 +56:52:28.8 -- not a known variable star
23:10:49.25 +58:08:56.3 -- not a known variable star
23:11:01.83 +58:31:23.1 -- not a known variable star
23:11:02.90 +61:17:38.3 -- not a known variable star
23:11:14.02 +57:02:22.5 -- not a known variable star
23:11:18.29 +58:26:37.1 -- not a known variable star
23:11:54.98 +61:50:30.4 -- not a known variable star
23:11:56.93 +60:47:40.2 -- not a known variable star
23:11:57.43 +60:33:55.8 -- not a known variable star
23:12:07.92 +64:51:57.7 -- not a known variable star
23:12:32.93 +62:56:10.6 -- a known variable star
23:12:34.73 +62:50:28.9 -- not a known variable star
23:13:03.38 +57:07:09.4 -- not a known variable star
23:13:08.83 +57:06:05.8 -- not a known variable star
23:13:11.08 +56:53:51.6 -- a known variable star
23:13:24.20 +57:52:02.7 -- not a known variable star
23:13:42.62 +59:30:39.1 -- not a known variable star
23:13:46.29 +57:12:01.7 -- not a known variable star
23:15:09.65 +63:06:31.4 -- not a known variable star
23:15:50.84 +62:49:32.2 -- not a known variable star
23:16:21.30 +59:47:18.8 -- not a known variable star
23:16:27.43 +64:56:10.0 -- not a known variable star
23:16:28.54 +57:51:00.6 -- a known variable star
23:16:39.20 +62:20:15.4 -- not a known variable star
23:17:12.73 +64:44:37.7 -- not a known variable star
23:17:41.89 +60:25:56.5 -- not a known variable star
23:17:51.79 +60:54:28.6 -- not a known variable star
23:18:19.01 +60:57:16.5 -- not a known variable star
23:18:34.77 +63:55:21.4 -- not a known variable star
23:18:41.66 +63:02:16.1 -- not a known variable star
23:18:46.65 +63:31:48.6 -- not a known variable star
23:19:09.37 +63:08:34.7 -- not a known variable star
23:20:02.87 +59:12:28.3 -- not a known variable star
23:21:04.75 +57:15:40.6 -- not a known variable star
23:21:06.09 +65:26:40.2 -- not a known variable star
23:21:17.94 +61:29:33.2 -- not a known variable star
23:21:18.07 +57:14:06.9 -- not a known variable star
23:21:30.92 +62:54:45.9 -- not a known variable star
23:21:47.23 +60:58:11.1 -- not a known variable star
23:21:57.66 +62:00:09.7 -- not a known variable star
23:23:35.45 +60:08:13.9 -- not a known variable star
23:23:42.89 +57:11:14.6 -- not a known variable star
23:24:06.13 +61:58:40.5 -- not a known variable star
23:24:20.11 +60:29:55.0 -- not a known variable star
23:24:26.91 +60:12:31.9 -- not a known variable star
23:24:27.62 +60:27:27.4 -- a known variable star
23:25:03.81 +61:34:50.3 -- a known variable star
23:25:05.93 +61:36:17.0 -- a known variable star
23:25:05.95 +59:40:49.1 -- not a known variable star
23:25:06.86 +61:36:46.8 -- not a known variable star
23:25:07.96 +61:33:21.6 -- a known variable star
23:25:20.59 +61:35:47.5 -- not a known variable star
23:25:23.63 +63:24:25.0 -- not a known variable star
23:25:32.63 +61:34:52.9 -- not a known variable star
23:25:37.74 +61:35:07.5 -- not a known variable star
23:25:41.92 +62:16:34.8 -- not a known variable star
23:25:46.25 +61:34:26.0 -- not a known variable star
23:25:53.58 +57:10:53.1 -- not a known variable star
23:25:54.71 +60:40:05.1 -- not a known variable star
23:26:22.97 +60:42:16.0 -- a known variable star
23:26:34.03 +61:18:56.1 -- not a known variable star
23:27:39.70 +63:28:51.9 -- not a known variable star
23:27:46.92 +60:55:56.4 -- not a known variable star
23:28:41.74 +61:08:39.1 -- not a known variable star
23:28:43.33 +60:24:59.0 -- not a known variable star
23:28:44.27 +57:14:04.1 -- not a known variable star
23:28:50.07 +62:35:47.0 -- not a known variable star
23:29:12.13 +61:01:50.8 -- not a known variable star
23:29:14.05 +61:01:26.4 -- not a known variable star
23:29:24.12 +63:47:43.6 -- not a known variable star
23:29:41.09 +60:54:36.5 -- not a known variable star
23:30:16.44 +61:22:28.4 -- not a known variable star
23:30:24.26 +61:22:53.1 -- not a known variable star
23:30:41.64 +57:58:12.5 -- not a known variable star
23:31:36.46 +61:01:45.3 -- a known variable star
23:31:40.51 +61:01:06.9 -- not a known variable star
23:32:06.18 +63:58:06.4 -- not a known variable star
23:32:31.78 +61:10:25.8 -- not a known variable star
23:33:01.34 +57:54:14.4 -- a known variable star
23:33:18.33 +57:37:18.7 -- not a known variable star
23:33:18.36 +59:56:49.4 -- not a known variable star
23:33:18.75 +61:00:15.7 -- not a known variable star
23:33:34.97 +58:28:11.7 -- not a known variable star
23:33:36.03 +60:24:35.3 -- not a known variable star
23:34:43.26 +60:59:52.1 -- not a known variable star
23:35:19.57 +61:06:50.7 -- not a known variable star
23:35:45.33 +61:28:25.0 -- not a known variable star
23:35:46.39 +59:56:05.4 -- not a known variable star
23:36:56.22 +61:41:19.5 -- not a known variable star
23:37:23.27 +62:43:25.5 -- not a known variable star
23:37:56.85 +57:20:48.0 -- not a known variable star
23:38:06.23 +57:31:45.0 -- not a known variable star
23:38:17.32 +58:06:21.7 -- not a known variable star
23:38:46.52 +58:40:51.5 -- not a known variable star
23:38:48.35 +60:51:21.1 -- not a known variable star
23:38:48.86 +58:38:52.1 -- a known variable star
23:39:38.44 +60:11:27.7 -- not a known variable star
23:39:51.02 +62:01:31.5 -- not a known variable star
23:39:52.09 +62:01:48.1 -- not a known variable star
23:39:54.53 +59:34:56.9 -- a known variable star
23:40:00.41 +61:29:05.2 -- not a known variable star
23:40:02.01 +63:26:39.6 -- not a known variable star
23:41:29.65 +61:42:37.5 -- not a known variable star
23:41:58.55 +62:42:12.9 -- not a known variable star
23:42:02.33 +62:52:58.9 -- not a known variable star
23:42:16.71 +57:16:44.2 -- not a known variable star
23:42:21.74 +57:16:34.1 -- not a known variable star
23:42:40.74 +61:26:59.2 -- not a known variable star
23:43:11.82 +61:32:34.8 -- not a known variable star
23:43:14.39 +62:36:22.2 -- a known variable star
23:43:41.78 +62:53:07.2 -- not a known variable star
23:44:12.58 +63:56:30.5 -- not a known variable star
23:44:47.65 +58:34:54.7 -- not a known variable star
23:45:38.57 +61:53:16.9 -- not a known variable star
23:46:13.79 +61:56:50.2 -- not a known variable star
23:46:27.00 +61:57:35.4 -- not a known variable star
23:47:19.80 +65:40:28.2 -- a known variable star
23:47:56.56 +60:41:16.0 -- not a known variable star
23:49:00.73 +61:15:08.9 -- not a known variable star
23:49:03.75 +59:23:54.4 -- not a known variable star
23:49:11.86 +64:50:04.0 -- a known variable star
23:49:49.45 +61:04:02.2 -- not a known variable star
23:50:43.97 +62:08:09.3 -- not a known variable star
23:50:52.68 +60:43:30.3 -- not a known variable star
23:50:57.25 +60:53:51.4 -- not a known variable star
23:51:12.50 +62:06:54.7 -- not a known variable star
23:51:29.41 +66:17:25.5 -- not a known variable star
23:51:30.44 +59:07:56.7 -- not a known variable star
23:51:44.65 +62:49:13.2 -- not a known variable star
23:52:04.28 +63:10:49.7 -- not a known variable star
23:52:26.42 +63:10:05.8 -- not a known variable star
23:52:34.12 +61:27:52.6 -- not a known variable star
23:53:09.68 +61:56:08.0 -- not a known variable star
23:53:14.48 +61:56:10.0 -- a known variable star
23:54:11.43 +60:49:59.5 -- not a known variable star
23:55:06.24 +58:46:31.2 -- not a known variable star
23:56:15.10 +60:36:10.9 -- not a known variable star
23:56:31.94 +66:45:54.6 -- not a known variable star
23:56:56.74 +61:21:57.5 -- a known variable star
23:57:08.33 +61:22:33.8 -- not a known variable star
23:57:21.15 +58:25:10.0 -- a known variable star
23:57:24.41 +61:22:12.3 -- a known variable star
23:57:31.13 +61:21:17.1 -- not a known variable star
23:57:37.86 +61:02:13.5 -- not a known variable star
23:58:35.93 +58:25:50.0 -- a known variable star
23:58:59.23 +60:16:00.3 -- not a known variable star
23:59:12.70 +64:48:34.5 -- not a known variable star
23:59:19.88 +66:44:15.6 -- not a known variable star
Found 203 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
239 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 239 (excluding asteroids and hot pixels, 203 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)2461235.65364067 -observatory V36
07:22:01.15 +17:08:50.9 Mercury (5.5mag)
10:27:24.89 +10:59:18.8 Venus (-4.1mag)
04:35:26.60 +21:52:19.8 Mars (1.3mag)
08:20:08.06 +20:00:27.8 Jupiter (-1.8mag)
00:56:13.34 +03:21:40.6 Saturn (0.7mag)
04:07:56.80 +20:46:58.6 Uranus (5.8mag)
00:16:59.60 +00:20:15.9 Neptune (7.7mag)
20:30:33.77 -23:19:41.0 Pluto (14.4mag)
07:16:32.74 +24:56:43.3 Moon (99.9mag)
-rw-r--r-- 1 apache apache 361 Jul 14 02:09 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461235.65364067:
08:20:15.43 +20:00:00.0 Io (6.1mag)
08:20:14.91 +20:00:03.1 Europa (6.3mag)
08:19:53.37 +20:01:23.9 Ganymede (5.6mag)
08:20:03.04 +20:00:42.3 Callisto (6.8mag)
08:18:29.23 +19:46:15.6 Himalia (15.7mag)
08:20:08.84 +20:00:25.6 Thebe (16.6mag)
08:17:49.96 +19:49:52.9 Elara (17.7mag)
08:23:47.15 +19:52:35.9 Pasiphae (17.8mag)
08:24:52.79 +20:06:06.1 Carme (19.0mag)
00:56:19.38 +03:21:10.5 Titan (8.5mag)
00:56:10.38 +03:21:51.5 Rhea (9.8mag)
00:55:39.22 +03:20:07.7 Iapetus (11.2mag)
00:56:06.08 +03:22:08.2 Hyperion (14.5mag)
00:56:09.00 +03:18:21.1 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jul 14 02:09 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461235.65364067:
17:52:19.43 -32:08:55.5 JWST
18:39:15.32 +23:41:56.7 Chandra
19:17:13.00 -01:10:54.8 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jul 14 02:09 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461235.65364067 -observatory V36
02:41:38.37 +14:52:31.9 17.9mag P/1996 R2 (Lagerkvist)
18:15:04.27 -34:27:40.8 13.8mag P/2010 H2 (Vales)
06:29:28.54 -68:12:12.2 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
06:02:07.14 +32:30:43.7 17.6mag C/2017 K2 (PANSTARRS)
02:08:25.95 +15:11:03.0 15.6mag P/2021 N1 (ZTF)
22:57:12.20 +32:16:14.6 17.3mag C/2022 E2 (ATLAS)
06:16:43.28 +26:53:28.0 16.7mag C/2022 N2 (PANSTARRS)
09:58:50.30 +29:36:38.0 16.9mag C/2022 QE78 (ATLAS)
09:12:11.77 +05:04:08.7 17.8mag C/2022 R6 (PANSTARRS)
18:04:55.73 +21:08:29.2 18.0mag C/2023 A3 (Tsuchinshan-ATLAS)
15:11:15.25 -11:28:39.4 17.7mag P/2023 B1 (PANSTARRS)
21:44:34.81 +67:34:52.6 17.8mag C/2023 H5 (Lemmon)
16:23:33.69 -10:28:28.1 13.9mag C/2023 R1 (PANSTARRS)
08:07:16.82 +65:54:55.6 17.9mag C/2024 A1 (ATLAS)
07:37:46.16 +30:11:43.0 14.7mag C/2024 E1 (Wierzchos)
15:14:32.76 +15:25:19.6 17.6mag C/2024 G6 (ATLAS)
19:36:25.77 +40:06:48.6 13.8mag C/2024 J3 (ATLAS)
21:43:33.74 +46:33:52.6 17.8mag C/2024 R4 (PANSTARRS)
04:53:12.79 -13:37:44.8 15.7mag C/2024 T5 (ATLAS)
06:37:42.13 +28:26:07.9 18.0mag C/2025 J1 (Borisov)
07:16:57.86 -13:14:01.7 16.7mag C/2025 R3 (PANSTARRS)
10:00:32.30 +22:16:15.0 17.6mag C/2025 V2 (Rankin)
12:45:56.07 +03:46:16.3 17.1mag C/2025 Y1 (ATLAS)
16:41:27.45 +79:10:06.4 17.3mag C/2026 A2 (Bok)
02:50:12.97 +45:24:05.5 16.7mag C/2026 B2 (Sun-Gao)
11:27:58.15 +05:12:17.1 17.0mag A/2026 E1
21:24:58.51 -16:28:22.4 7.2mag 10P/Tempel
11:15:15.69 -02:03:10.7 16.2mag 29P/Schwassmann-Wachmann
04:05:38.00 +29:57:50.4 17.9mag 47P/Ashbrook-Jackson
10:16:00.78 +12:47:51.1 17.1mag 63P/Wild
00:49:56.61 -05:03:24.6 15.5mag 65P/Gunn
04:36:35.18 +20:21:54.7 13.7mag 78P/Gehrels
02:28:24.68 +11:07:30.5 16.3mag 88P/Howell
06:46:48.18 +30:17:45.2 15.7mag 93P/Lovas
04:33:22.46 +31:15:37.1 16.8mag 114P/Wiseman-Skiff
08:17:59.14 +30:16:16.2 15.2mag 123P/West-Hartley
10:55:14.35 -00:21:28.6 16.8mag 124P/Mrkos
04:57:49.64 +20:55:01.1 16.2mag 128P/Shoemaker-Holt
05:43:24.72 +19:40:40.0 17.8mag 131P/Mueller
00:02:30.86 +03:04:37.6 17.9mag 139P/Vaisala-Oterma
07:27:24.24 +16:11:22.5 16.0mag 141P-D/Machholz
03:18:23.30 -20:47:43.5 15.3mag 161P/Hartley-IRAS
05:46:46.10 +34:44:25.0 15.4mag 162P/SidingSpring
18:53:57.01 +17:30:55.7 14.4mag 169P/NEAT
01:50:03.32 +08:00:46.0 17.7mag 220P/McNaught
16:35:34.41 -08:32:36.8 17.1mag 235P/LINEAR
08:53:16.80 +32:56:39.8 18.0mag 240P/NEAT
20:40:24.65 -50:22:36.5 17.8mag 259P/Garradd
02:09:58.36 +13:52:23.5 15.6mag 260P/McNaught
05:48:46.67 +37:07:55.9 17.4mag 295P/LINEAR
15:06:28.79 +05:42:50.2 17.6mag 391P/Kowalski
08:38:01.40 +19:31:15.9 17.9mag 450P/LONEOS
07:57:43.61 +38:53:58.4 18.0mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.6K Jul 14 02:09 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
11:06:55.46 -04:07:04.50 AT2026qqg 2026-07-5.01 16.82
19:07:23.69 -74:13:37.30 AT2026qly 2026-07-5.02 17.31
17:57:43.80 +27:18:40.10 ASASSN-26ea 2026-07-5.07 16.67
19:59:01.43 -32:07:34.30 ASASSN-26eb 2026-07-4.97 15.52
18:46:50.35 -57:44:13.20 SN 2026qqp 2026-07-5.03 -0.92
19:17:31.69 -39:55:29.90 ASASSN-26dz 2026-07-5.14 15.91
19:14:31.37 +12:03:52.90 AT 2026rdg 2026-07-3.43 11.81
04:05:50.09 -70:24:34.40 AT 2026qpr 2026-06-30.4 15.96
13:45:37.49 -05:59:35.80 SN 2026pub 2026-06-30.09 16.01
16:41:15.63 +39:17:14.70 SN 2026pel 2026-06-26.38 16.07
10:14:40.19 -35:38:21.30 ASASSN-26dy 2026-06-25.99 15.63
14:47:21.56 -40:15:51.30 ASASSN-26dv 2026-06-23.03 14.62
13:38:49.79 -77:21:06.70 ASASSN-26dw 2026-06-23.04 16.09
00:59:27.90 +33:08:13.20 SN 2026mke 2026-06-22.39 17.13
11:10:44.73 -30:20:45.50 SN 2026nmv 2026-06-22.06 16.56
21:36:15.68 -21:19:12.50 AT2026oxh 2026-06-22.15 17.14
17:31:38.38 -56:05:51.90 ASASSN-26dx 2026-06-22.02 14.72
14:10:13.44 -38:46:46.10 AT2026pvk 2026-06-22.06 16.53
20:56:47.23 -18:31:05.20 AT2026plb 2026-06-21.31 16.4
15:44:29.68 +21:00:59.30 SN2026ore 2026-06-21.29 17.57
23:50:05.98 -14:01:41.30 AT2026oxl 2026-06-21.52 17.64
17:36:54.73 -18:10:04.20 AT2026ouj 2026-06-20.92 15.15
00:34:04.08 -30:22:09.20 AT2026ntk 2026-06-18.09 17.34
20:49:13.39 +25:17:59.20 ASASSN-26du 2026-06-15.39 15.93
23:09:30.84 +32:40:42.00 SN2026oxc 2026-06-14.35 16.83
02:02:26.78 +32:04:21.30 AT2026ovz 2026-06-14.59 15.39
21:26:28.11 -72:31:19.50 AT2026nwc 2026-06-11 17.05
17:54:57.33 +26:32:34.20 SN 2026odc 2026-06-11.23 17.62
13:55:59.94 +17:30:37.20 SN 2026nyq 2026-06-11.1 16.24
00:50:45.14 -71:38:36.90 ASASSN-26dt 2026-06-11.13 10.22
14:42:19.73 +19:11:35.60 SN2026nyp 2026-06-10.3 16.32
12:23:23.92 +12:56:43.50 SN2026mta 2026-06-8.29 16.69
12:30:18.51 +47:12:33.20 SN2026oao 2026-06-9.32 17.02
10:51:05.21 -42:28:56.60 AT2026nvf 2026-06-8.12 16.75
13:50:22.48 -07:35:00.00 SN2026npn 2026-06-8.02 17.58
00:56:07.17 +43:01:43.20 ASASSN-26dq 2026-06-7.43 13.58
01:07:49.46 +41:59:43.70 SN 2026obc 2026-06-7.43 15.15
21:11:25.22 +14:14:31.90 ASASSN-26dr 2026-06-7.24 16.24
06:21:27.06 -65:16:42.00 ASASSN-26ds 2026-06-2.97 15.02
20:07:38.15 -21:07:05.40 SN2026mho 2026-05-25.18 -1.12
11:29:42.55 +79:01:03.10 AT2026min 2026-05-24.21 16.63
11:44:33.11 -68:48:32.90 ASASSN-26no 2026-05-24.03 8.35
19:00:42.82 -48:31:01.60 ASASSN-26dp 2026-05-22.31 -3.28
14:23:56.72 -58:37:47.60 ASASSN-26dn 2026-05-20.01 14.64
11:24:54.06 +47:57:01.60 AT2026nma 2026-05-20.29 15.46
21:27:08.58 +33:24:38.10 AT2026lli 2026-05-19.34 15.86
00:31:01.41 -13:38:51.70 AT2026nad 2026-05-19.39 15.34
15:16:06.61 -79:16:32.40 ASASSN-26dm 2026-05-19.03 14.44
11:24:25.21 -59:23:19.10 ASASSN-26dl 2026-05-18.02 13.55
13:45:51.52 -53:16:01.00 ASASSN-26dk 2026-05-18.16 12.96
02:05:49.69 -30:29:09.60 ASASSN-26dh 2026-05-18.43 15.37
17:50:22.87 -39:42:33.90 ASASSN-26dj 2026-05-17.05 15.7
01:13:11.60 -33:25:16.10 ASASSN-26dg 2026-05-13.41 16.8
16:44:31.77 -27:15:18.40 AT2026mhn 2026-05-12.33 15.8
09:46:31.08 -33:41:51.00 ASASSN-26di 2026-05-12.14 14.63
21:23:11.57 -19:09:45.00 AT2026kwu 2026-05-12.26 16.9
14:20:14.30 -30:20:51.90 AT2026ktm 2026-05-12.06 17.21
14:41:39.01 -37:13:46.40 AT2026lkm 2026-05-11.18 16.89
12:59:50.45 -10:58:38.80 SN2026kep 2026-05-9.06 17.5
13:37:29.61 -29:50:30.90 AT2026lkd 2026-05-9.09 17.23
09:46:42.01 -14:52:03.60 SN2026kmo 2026-05-8.99 17.51
15:03:05.28 +22:02:03.80 AT2026lxf 2026-05-8.34 13.72
10:23:49.41 -20:57:25.30 ASASSN-26df 2026-05-8.21 16.52
22:14:40.56 +05:04:51.60 2026lda 2026-05-7.56 16.2
21:35:33.81 -14:05:16.30 ASASSN-26de 2026-05-6.29 14.51
16:21:48.82 -61:36:13.20 ASASSN-26dd 2026-05-5.21 15.15
14:26:40.22 -24:48:37.50 AT2026lig 2026-05-4.27 14.63
13:17:51.04 +30:25:13.50 SN2026kcp 2026-05-4.46 16.43
11:27:55.57 -13:38:56.90 SN2026kza 2026-05-1.08 15.59
22:28:27.10 +30:17:54.30 SN 2026fov 2026-04-29.6 14.36
21:00:10.71 -32:17:03.90 AT2026kis 2026-04-27.36 16.15
14:32:57.37 -58:13:26.40 ASASSN-26dc 2026-04-27.27 13.42
15:32:05.35 -43:54:34.60 ASASSN-26db 2026-04-27.37 16.06
16:34:34.97 -54:34:58.00 ASASSN-26da 2026-04-25.32 16.11
10:06:55.04 -01:13:49.70 SN2026jsg 2026-04-24.99 16.28
15:15:57.17 +56:18:32.80 SN2026kid 2026-04-24.52 -3.65
07:58:28.45 +57:03:42.40 AT2026kcf 2026-04-24.2 16.89
11:38:21.80 -50:43:06.50 SN2026jkb 2026-04-24.24 15.38
10:06:11.41 -39:41:04.20 AT2026dil 2026-04-24.2 16.85
14:21:40.08 +13:13:46.30 SN2026jlm 2026-04-22.16 15.12
10:53:55.47 -16:06:07.00 ASASSN-26cz 2026-04-22.24 16.32
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
13:45:02.03 +15:17:14.50 ASASSN-26cy 2026-04-21.27 15.78
13:20:52.22 -35:57:03.60 AT2026jcm 2026-04-19.01 16.65
13:36:15.66 -36:53:48.40 SN 2026iqy 2026-04-18.92 17.31
06:34:01.33 -40:07:34.00 ASASSN-26cx 2026-04-19.07 16.16
23:33:57.97 -45:12:11.90 SN 2026idu 2026-04-19.41 15.9
12:10:50.92 +66:55:31.20 SN 2026icv 2026-04-17.14 16.03
21:36:59.06 -60:43:35.90 ASASSN-26cv 2026-04-17.35 -1.18
08:13:26.26 -27:07:30.50 ASASSN-26cw 2026-04-17.07 -1.01
14:49:14.13 -27:29:20.60 ASASSN-26cu 2026-04-16.06 14.03
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
11:06:55.46 -04:07:04.50 2026-07-5.01 16.82
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
-rw-r--r-- 1 apache apache 5.6K Jul 14 02:09 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
00:43:01.82 +41:18:16.6 PNV J00430182+4118166 2026-05-21.8651 18.83Cmag
00:42:51.20 +41:16:59.4 PNV J00425120+4116594 2022-10-26.135 19.3mag
12:24:25.10 +28:47:12.0 TCP J12242510+2847120 2026-05-31.6015 14.8mag
00:56:07.13 +43:01:40.6 TCP J00560713+4301406 2026-06-01.4135 12.2mag
00:42:41.64 +41:15:16.2 PNV J00424164+4115162 2026-06-02.029 17.4mag
00:42:38.68 +41:15:58.2 PNV J00423868+4115582 2026-06-05.1224 19.97Umag
19:00:42.95 -48:31:01.7 PNV J19004295-4831017 2026-05-25.0752 14.2mag
09:55:21.28 +69:02:52.6 PNV J09552128+6902526 2026-06-13.933 18.9mag
19:51:21.42 +37:06:40.0 TCP J19512142+3706400 2026-06-17.2942 16.8mag
19:57:03.87 +37:41:46.4 TCP J19570387+3741464 2026-06-18.2638 17.5mag
00:42:32.04 +41:10:28.3 PNV J00423204+4110283 2026-06-26.059 16.6mag
02:19:17.36 +28:57:15.8 TCP J02191736+2857158 2026-07-12.3549 12.5mag
-rw-r--r-- 1 apache apache 189K Jul 14 02:09 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
22:28:27.030 -03:35:42.74 AT 2026tuc 2026-07-09.34 21.5762
22:32:50.698 -04:44:49.26 AT 2026tub 2026-07-09.34 21.4143
22:22:30.197 -05:16:57.20 AT 2026tua 2026-07-09.34 22.2726
22:28:03.757 -02:04:50.07 AT 2026ttz 2026-07-09.34 21.7676
22:28:44.738 -02:46:18.12 AT 2026tty 2026-07-09.34 22.9915
22:20:46.753 -10:45:21.00 AT 2026ttx 2026-07-07.39 22.4769
22:14:51.717 -14:51:45.88 AT 2026ttw 2026-07-07.42 22.8608
21:49:49.081 -15:37:58.81 AT 2026ttv 2026-07-07.42 22.5231
22:09:31.526 -19:49:15.36 AT 2026ttu 2026-07-07.39 22.923
22:25:43.683 -07:27:16.72 AT 2026ttt 2026-07-07.42 23.2007
22:23:06.784 -18:25:04.82 AT 2026tts 2026-07-07.40 22.4323
22:26:47.693 -12:06:02.25 AT 2026ttr 2026-07-07.39 22.0467
22:21:26.920 -11:44:02.24 AT 2026ttq 2026-07-07.39 22.6154
22:09:19.482 -13:54:04.50 AT 2026ttp 2026-07-07.42 22.4569
21:41:38.537 -22:07:37.94 AT 2026tto 2026-07-07.43 23.0233
22:14:46.325 -08:42:09.31 AT 2026ttn 2026-07-07.42 23.044
22:00:34.428 -18:29:27.16 AT 2026ttm 2026-07-07.42 22.0271
22:17:33.139 -16:54:49.09 AT 2026ttl 2026-07-07.42 23.3518
22:19:22.064 -20:33:27.16 AT 2026ttk 2026-07-07.40 22.5487
21:40:11.965 -23:21:51.55 AT 2026ttj 2026-07-07.40 22.0779
-rw-r--r-- 1 apache apache 30K Jul 14 02:09 tns_transients_list.txt
