This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 11.31 00:34:23.96 +64:31:45.8
121.10062 1.71824 galactic Cas Second-epoch detections are separated by 4.5" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:34:23.96 +64:31:45.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:34:23.96 +64:31:45.8: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:23.96 +64:31:45.8: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 34 23.96 +64 31 45.8 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,2461212.7242,11.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 11.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.24 00:05:04.17 +62:16:30.5
117.56784 -0.11272 galactic Cas Second-epoch detections are separated by 3.9" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:04.17 +62:16:30.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:04.17 +62:16:30.5: 16.14 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:04.17 +62:16:30.5: 16.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 05 04.17 +62 16 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,2461212.7242,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.36 00:01:02.67 +63:08:17.9
117.27549 0.82133 galactic Cas Second-epoch detections are separated by 5.2" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:02.67 +63:08:17.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:01:02.67 +63:08:17.9: 16.01 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:02.67 +63:08:17.9: 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 06 21.2242* 00 01 02.67 +63 08 17.9 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 14.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.16 23:21:32.26 +65:22:39.1
113.74326 4.12221 galactic Cep Second-epoch detections are separated by 6.5" and 6.2 pix
The object was found in VSX14" ZTF J232134.20+652232.3
Type: BY
# Max. Min./Amp. JD0 Period
13.820 r Y 0.034 r 2458303.96000 6.191812300000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:21:32.26 +65:22:39.1: 15.98 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:32.26 +65:22:39.1: 15.86 +/- 0.32 detection
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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J232134.20+652232.3,2461212.7242,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J232134.20+652232.3 20260621.2242 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.09 23:31:43.98 +63:17:24.9
114.11608 1.79094 galactic Cas Second-epoch detections are separated by 4.2" and 6.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:43.98 +63:17:24.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:31:43.98 +63:17:24.9: 15.98 +/- 0.34 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:31:43.98 +63:17:24.9: 15.18 +/- 0.15 detection
Forced photometry reference-image weighted average: 15.31 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 31 43.98 +63 17 24.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,2461212.7242,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 14.20 23:58:05.41 +63:14:26.8
116.96951 0.98827 galactic Cas Second-epoch detections are separated by 3.8" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:58:05.41 +63:14:26.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:58:05.41 +63:14:26.8: 15.87 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:58:05.41 +63:14:26.8: 16.06 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.87 +/- 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 06 21.2242* 23 58 05.41 +63 14 26.8 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 14.33 23:55:26.41 +62:57:17.5
116.61627 0.77180 galactic Cas Second-epoch detections are separated by 7.7" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:26.41 +62:57:17.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:55:26.41 +62:57:17.5: 16.08 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:55:26.41 +62:57:17.5: 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!
TCP 2026 06 21.2242* 23 55 26.41 +62 57 17.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 14.15 00:23:14.08 +62:26:41.2
119.67663 -0.24858 galactic Cas Second-epoch detections are separated by 4.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:14.08 +62:26:41.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:14.08 +62:26:41.2: 16.06 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:23:14.08 +62:26:41.2: 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 06 21.2242* 00 23 14.08 +62 26 41.2 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 14.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.00 00:20:22.93 +60:15:48.4
119.08649 -2.37623 galactic Cas Second-epoch detections are separated by 2.6" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:20:22.93 +60:15:48.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:20:22.93 +60:15:48.4: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:20:22.93 +60:15:48.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!
TCP 2026 06 21.2242* 00 20 22.93 +60 15 48.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.04 23:57:08.74 +62:42:27.6
116.75411 0.48894 galactic Cas Second-epoch detections are separated by 7.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:57:08.74 +62:42:27.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:57:08.74 +62:42:27.6: 16.19 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:08.74 +62:42:27.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!
TCP 2026 06 21.2242* 23 57 08.74 +62 42 27.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,2461212.7242,14.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.88 00:23:32.36 +60:00:49.8
119.44873 -2.66910 galactic Cas Second-epoch detections are separated by 4.6" and 6.2 pix
The object was found in VSX19" ASASSN-V J002329.88+600050.1
Type: SR
# Max. Min./Amp. JD0 Period
14.020 V 14.120 V 2457370.00000 200.000000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:32.36 +60:00:49.8: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:23:32.36 +60:00:49.8: 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!
TCP 2026 06 21.2242* 00 23 32.36 +60 00 49.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J002329.88+600050.1,2461212.7242,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J002329.88+600050.1 20260621.2242 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 06 21.2242 2461212.7242 13.91 00:14:44.88 +62:54:27.4
118.76861 0.33282 galactic Cas Second-epoch detections are separated by 5.4" and 6.4 pix
The object was found in VSX16" Gaia DR3 431287116795487488
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.040 G 14.060 G B
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:14:44.88 +62:54:27.4: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:14:44.88 +62:54:27.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 06 21.2242* 00 14 44.88 +62 54 27.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431287116795487488,2461212.7242,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431287116795487488 20260621.2242 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 06 21.2242 2461212.7242 13.96 00:09:37.10 +63:17:37.5
118.25369 0.80249 galactic Cas Second-epoch detections are separated by 3.2" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:37.10 +63:17:37.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:37.10 +63:17:37.5: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:37.10 +63:17:37.5: 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 06 21.2242* 00 09 37.10 +63 17 37.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,2461212.7242,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.13 00:13:32.08 +63:01:26.6
118.64897 0.46793 galactic Cas Second-epoch detections are separated by 3.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:32.08 +63:01:26.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:13:32.08 +63:01:26.6: 16.01 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:13:32.08 +63:01:26.6: 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 06 21.2242* 00 13 32.08 +63 01 26.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,2461212.7242,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.78 23:57:20.18 +59:53:22.3
116.18865 -2.27200 galactic Cas Second-epoch detections are separated by 2.3" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1999566971495821952 | 23:57:15.49 +59:53:20.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:57:20.18 +59:53:22.3: 14.89 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:20.18 +59:53:22.3: 14.93 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.91 +/- 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 06 21.2242* 23 57 20.18 +59 53 22.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 1999566971495821952,2461212.7242,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1999566971495821952 20260621.2242 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 06 21.2242 2461212.7242 13.89 00:05:44.49 +63:49:46.3
117.91881 1.40345 galactic Cas Second-epoch detections are separated by 3.6" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:44.49 +63:49:46.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:44.49 +63:49:46.3: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:44.49 +63:49:46.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!
TCP 2026 06 21.2242* 00 05 44.49 +63 49 46.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,2461212.7242,13.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.59 00:22:08.72 +63:58:07.8
119.72435 1.27967 galactic Cas Second-epoch detections are separated by 3.8" and 6.4 pix
The object was found in VSX15" Gaia DR3 431071990473840000
Type: S
# Max. Min./Amp. JD0 Period
16.740 G 17.530 G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:22:08.72 +63:58:07.8: 16.07 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:22:08.72 +63:58:07.8: 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 06 21.2242* 00 22 08.72 +63 58 07.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431071990473840000,2461212.7242,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431071990473840000 20260621.2242 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 06 21.2242 2461212.7242 13.55 00:15:49.72 +63:10:16.1
118.92675 0.57664 galactic Cas Second-epoch detections are separated by 5.5" and 6.2 pix
The object was found in VSX11" ASASSN-V J001548.22+631018.7
Type: SR
# Max. Min./Amp. JD0 Period
14.180 V 14.420 V 2457365.79900 32.440000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:49.72 +63:10:16.1: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:49.72 +63:10:16.1: 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 06 21.2242* 00 15 49.72 +63 10 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
ASASSN-V J001548.22+631018.7,2461212.7242,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J001548.22+631018.7 20260621.2242 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 06 21.2242 2461212.7242 13.52 23:35:24.40 +57:34:22.0
112.85132 -3.80328 galactic Cas Second-epoch detections are separated by 4.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1998900117691032192 | 23:35:23.90 +57:34:02.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G3 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:35:24.40 +57:34:22.0: 14.84 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:35:24.40 +57:34:22.0: 14.72 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.78 +/- 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 06 21.2242* 23 35 24.40 +57 34 22.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
Gaia DR3 1998900117691032192,2461212.7242,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998900117691032192 20260621.2242 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 06 21.2242 2461212.7242 13.71 00:17:54.84 +59:11:56.0
118.64413 -3.39348 galactic Cas Second-epoch detections are separated by 0.1" 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 | Gaia DR3 428227309066816384 | 00:17:52.44 +59:11:38.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:54.84 +59:11:56.0: 15.60 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:54.84 +59:11:56.0: 15.08 +/- 0.19 detection
Forced photometry reference-image weighted average: 15.23 +/- 0.16
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 17 54.84 +59 11 56.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
Gaia DR3 428227309066816384,2461212.7242,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428227309066816384 20260621.2242 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 06 21.2242 2461212.7242 13.54 00:18:20.39 +58:11:24.5
118.56848 -4.40092 galactic Cas Second-epoch detections are separated by 3.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 | Gaia DR3 422162956987452928 | 00:18:22.09 +58:12:01.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F0 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:18:20.39 +58:11:24.5: 15.05 +/- 0.16 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:18:20.39 +58:11:24.5: 15.24 +/- 0.18 detection
Forced photometry reference-image weighted average: 15.13 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 18 20.39 +58 11 24.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422162956987452928,2461212.7242,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422162956987452928 20260621.2242 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 06 21.2242 2461212.7242 13.66 23:59:12.04 +64:51:31.8
117.41763 2.54783 galactic Cas Second-epoch detections are separated by 3.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:59:12.04 +64:51:31.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:59:12.04 +64:51:31.8: 15.96 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:59:12.04 +64:51:31.8: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 59 12.04 +64 51 31.8 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.53 00:05:11.49 +61:07:04.8
117.37536 -1.25383 galactic Cas Second-epoch detections are separated by 3.7" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:11.49 +61:07:04.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:11.49 +61:07:04.8: 15.59 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:11.49 +61:07:04.8: 15.33 +/- 0.18 detection
Forced photometry reference-image weighted average: 15.44 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 05 11.49 +61 07 04.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,2461212.7242,13.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.36 00:02:05.99 +62:08:21.7
117.20257 -0.18230 galactic Cas 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 | Gaia DR3 429912211864030720 | 00:02:00.64 +62:08:44.6 (Gaia DR3) | DSCT/GDOR (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: A2 1955IzKry..14....3B [B55b] 5694
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:02:05.99 +62:08:21.7: 15.46 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:02:05.99 +62:08:21.7: 15.44 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.45 +/- 0.16
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 02 05.99 +62 08 21.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429912211864030720,2461212.7242,13.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429912211864030720 20260621.2242 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 06 21.2242 2461212.7242 13.34 00:29:43.96 +58:56:37.3
120.12946 -3.80990 galactic Cas Second-epoch detections are separated by 2.9" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:29:43.96 +58:56:37.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:29:43.96 +58:56:37.3: 15.52 +/- 0.25 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:29:43.96 +58:56:37.3: 15.10 +/- 0.16 detection
Forced photometry reference-image weighted average: 15.22 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 29 43.96 +58 56 37.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,2461212.7242,13.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.38 00:02:24.80 +57:55:40.1
116.44126 -4.32480 galactic Cas 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 | ATO J000.5923+57.9252 | 00:02:24.80 +57:55:40.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:02:24.80 +57:55:40.1: 14.96 +/- 0.13 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:02:24.80 +57:55:40.1: 15.06 +/- 0.14 detection
Forced photometry reference-image weighted average: 15.00 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 02 24.80 +57 55 40.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 J000.5923+57.9252,2461212.7242,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.5923+57.9252 20260621.2242 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 06 21.2242 2461212.7242 13.29 00:27:12.32 +61:09:29.6
120.01259 -1.57610 galactic Cas Second-epoch detections are separated by 3.8" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 428873684467355392 | 00:27:07.02 +61:09:34.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE J-Ks=0.797+/-0.189 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:27:12.32 +61:09:29.6: 15.72 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:27:12.32 +61:09:29.6: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 27 12.32 +61 09 29.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 428873684467355392,2461212.7242,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428873684467355392 20260621.2242 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 06 21.2242 2461212.7242 13.29 00:11:17.00 +57:47:49.4
117.58406 -4.65715 galactic Cas Second-epoch detections are separated by 4.6" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422474221858262656 | 00:11:15.16 +57:48:07.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:11:17.00 +57:47:49.4: 15.50 +/- 0.26 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:11:17.00 +57:47:49.4: 15.52 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.51 +/- 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 06 21.2242* 00 11 17.00 +57 47 49.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
Gaia DR3 422474221858262656,2461212.7242,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422474221858262656 20260621.2242 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 06 21.2242 2461212.7242 13.40 00:17:17.39 +62:50:56.1
119.04754 0.23500 galactic Cas Second-epoch detections are separated by 2.1" and 5.9 pix
The object was found in VSX 9" Gaia DR3 431272269083225472
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.600 G 13.660 G 1.159660000000 B
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:17.39 +62:50:56.1: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:17.39 +62:50:56.1: 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 06 21.2242* 00 17 17.39 +62 50 56.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
Gaia DR3 431272269083225472,2461212.7242,13.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431272269083225472 20260621.2242 13.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.30 23:52:29.20 +63:11:39.6
116.34304 1.07921 galactic Cas Second-epoch detections are separated by 8.2" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:29.20 +63:11:39.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:52:29.20 +63:11:39.6: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:52:29.20 +63:11:39.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 06 21.2242* 23 52 29.20 +63 11 39.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,2461212.7242,13.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.20 23:27:44.26 +57:24:28.2
111.81747 -3.64658 galactic Cas Second-epoch detections are separated by 2.3" and 7.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1998847822161579264 | 23:27:49.00 +57:24:50.2 (Gaia DR3) | E (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: A5V (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:27:44.26 +57:24:28.2: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:27:44.26 +57:24:28.2: 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 06 21.2242* 23 27 44.26 +57 24 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
Gaia DR3 1998847822161579264,2461212.7242,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998847822161579264 20260621.2242 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 06 21.2242 2461212.7242 13.06 00:03:26.62 +59:45:26.7
116.91576 -2.55254 galactic Cas Second-epoch detections are separated by 2.7" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 423281160314549248 | 00:03:23.26 +59:45:12.4 (Gaia DR3) | ROT (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:03:26.62 +59:45:26.7: 14.78 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:03:26.62 +59:45:26.7: 14.89 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.83 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 03 26.62 +59 45 26.7 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 423281160314549248,2461212.7242,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 423281160314549248 20260621.2242 13.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.15 00:27:13.12 +61:50:40.8
120.07866 -0.89283 galactic Cas Second-epoch detections are separated by 1.9" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430423622209908736 | 00:27:08.19 +61:50:53.3 (Gaia DR3) | ROT (local) | (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:27:13.12 +61:50:40.8: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:27:13.12 +61:50:40.8: 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 06 21.2242* 00 27 13.12 +61 50 40.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
Gaia DR3 430423622209908736,2461212.7242,13.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430423622209908736 20260621.2242 13.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.04 00:15:54.56 +59:25:16.6
118.42003 -3.13887 galactic Cas Second-epoch detections are separated by 3.8" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:54.56 +59:25:16.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:54.56 +59:25:16.6: 15.56 +/- 0.29 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:54.56 +59:25:16.6: 15.85 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.56 +/- 0.29
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 15 54.56 +59 25 16.6 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,2461212.7242,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.05 00:24:16.38 +61:50:54.3
119.73326 -0.85451 galactic Cas Second-epoch detections are separated by 3.4" and 6.1 pix
The object was found in VSX19" ASASSN-V J002416.75+615112.8
Type: SR
# Max. Min./Amp. JD0 Period
12.540 V 12.730 V 2457344.73300 48.430000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:24:16.38 +61:50:54.3: 13.99 +/- 0.07 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:24:16.38 +61:50:54.3: 14.14 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.05 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 24 16.38 +61 50 54.3 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J002416.75+615112.8,2461212.7242,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J002416.75+615112.8 20260621.2242 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 06 21.2242 2461212.7242 12.84 00:30:25.66 +57:56:22.1
120.13670 -4.81820 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 | ATO J007.6335+57.9311 | 00:30:29.89 +57:56:28.3 (Gaia DR3) | MSINE (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:30:25.66 +57:56:22.1: 14.43 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:30:25.66 +57:56:22.1: 14.24 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.32 +/- 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 06 21.2242* 00 30 25.66 +57 56 22.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
ATO J007.6335+57.9311,2461212.7242,12.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.6335+57.9311 20260621.2242 12.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.90 00:16:07.42 +63:38:24.7
119.02380 1.03673 galactic Cas Second-epoch detections are separated by 3.3" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:07.42 +63:38:24.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:07.42 +63:38:24.7: 15.69 +/- 0.26 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:07.42 +63:38:24.7: 15.66 +/- 0.27 detection
Forced photometry reference-image weighted average: 15.68 +/- 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 06 21.2242* 00 16 07.42 +63 38 24.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,2461212.7242,12.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 12.89 00:00:26.79 +63:11:25.2
117.21946 0.88553 galactic Cas Second-epoch detections are separated by 3.7" and 6.1 pix
The object was found in VSX 8" ZTF J000026.55+631117.6
Type: EW
# Max. Min./Amp. JD0 Period
18.485 r Y 0.543 r 2458367.84320 0.374738000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:00:26.79 +63:11:25.2: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:00:26.79 +63:11:25.2: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 00 26.79 +63 11 25.2 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
ZTF J000026.55+631117.6,2461212.7242,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J000026.55+631117.6 20260621.2242 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.01 00:09:30.57 +62:35:17.5
118.12738 0.10822 galactic Cas Second-epoch detections are separated by 2.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429997591513318400 | 00:09:35.21 +62:34:59.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:30.57 +62:35:17.5: 15.23 +/- 0.22 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:30.57 +62:35:17.5: 14.61 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.75 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 09 30.57 +62 35 17.5 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 429997591513318400,2461212.7242,13.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429997591513318400 20260621.2242 13.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.89 00:18:27.47 +61:52:42.7
119.05580 -0.74476 galactic Cas Second-epoch detections are separated by 2.3" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | FP Cas | 00:18:23.39 +61:52:27.8 (Gaia DR3) | LB (local) | (local) | Gaia3var=VARIABLE SpType: M6 1956ApJ...124..346C FP Cas
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:18:27.47 +61:52:42.7: 14.89 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:18:27.47 +61:52:42.7: 14.69 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.77 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 18 27.47 +61 52 42.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
FP Cas,2461212.7242,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
FP Cas 20260621.2242 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.80 00:09:11.64 +63:10:36.0
118.18754 0.69471 galactic Cas Second-epoch detections are separated by 3.2" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:11.64 +63:10:36.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:11.64 +63:10:36.0: 15.68 +/- 0.34 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:11.64 +63:10:36.0: 15.74 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.68 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 09 11.64 +63 10 36.0 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 12.62 23:23:08.41 +64:48:40.6
113.71051 3.53227 galactic Cep Second-epoch detections are separated by 3.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:23:08.41 +64:48:40.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:23:08.41 +64:48:40.6: 16.02 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:23:08.41 +64:48:40.6: 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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 11.57 00:16:14.47 +60:59:35.9
118.67630 -1.58729 galactic Cas Second-epoch detections are separated by 2.9" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429571844296750592 | 00:16:10.31 +60:59:44.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:14.47 +60:59:35.9: 14.69 +/- 0.16 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:14.47 +60:59:35.9: 14.65 +/- 0.17 detection
Forced photometry reference-image weighted average: 14.67 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 16 14.47 +60 59 35.9 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429571844296750592,2461212.7242,11.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429571844296750592 20260621.2242 11.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.01 00:20:28.90 +61:52:31.5
119.29210 -0.77736 galactic Cas Second-epoch detections are separated by 0.5" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430464922616254848 | 00:20:27.36 +61:52:32.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:20:28.90 +61:52:31.5: 13.80 +/- 0.07 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:20:28.90 +61:52:31.5: 13.82 +/- 0.07 detection
Forced photometry reference-image weighted average: 13.81 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 20 28.90 +61 52 31.5 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430464922616254848,2461212.7242,12.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430464922616254848 20260621.2242 12.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.47 00:04:54.35 +61:20:34.7
117.38181 -1.02634 galactic Cas Second-epoch detections are separated by 1.9" and 6.3 pix
The object was found in VSX20" Gaia DR3 429451306029921024
Type: RS
# Max. Min./Amp. JD0 Period
17.990 G 18.130 G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:04:54.35 +61:20:34.7: 14.30 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:54.35 +61:20:34.7: 13.95 +/- 0.06 detection
Forced photometry reference-image weighted average: 14.07 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 04 54.35 +61 20 34.7 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429451306029921024,2461212.7242,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429451306029921024 20260621.2242 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 06 21.2242 2461212.7242 12.46 00:21:27.24 +59:13:54.5
119.09849 -3.41659 galactic Cas Second-epoch detections are separated by 1.6" and 6.1 pix
The object was found in VSX13" FQ Cas
Type: M
# Max. Min./Amp. JD0 Period
11.100 V 17.900 V 2459825.00000 269.800000000000 M6.5
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:21:27.24 +59:13:54.5: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:21:27.24 +59:13:54.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 06 21.2242* 00 21 27.24 +59 13 54.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
FQ Cas,2461212.7242,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
FQ Cas 20260621.2242 12.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.56 00:41:41.86 +65:49:36.8
121.93368 2.97402 galactic Cas Second-epoch detections are separated by 6.4" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:41:41.86 +65:49:36.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:41:41.86 +65:49:36.8: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:41:41.86 +65:49:36.8: 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 06 21.2242* 00 41 41.86 +65 49 36.8 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 12.62 23:42:49.59 +61:39:26.9
114.88337 -0.13743 galactic Cas Second-epoch detections are separated by 1.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:42:49.59 +61:39:26.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:42:49.59 +61:39:26.9: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:42:49.59 +61:39:26.9: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 42 49.59 +61 39 26.9 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 12.71 23:25:07.90 +61:36:03.3
112.85863 0.42873 galactic Cas Second-epoch detections are separated by 8.3" and 6.5 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
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:25:07.90 +61:36:03.3: 13.78 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:07.90 +61:36:03.3: 13.55 +/- 0.09 detection
Forced photometry reference-image weighted average: 13.64 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 25 07.90 +61 36 03.3 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J232507.68+613615.8,2461212.7242,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J232507.68+613615.8 20260621.2242 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.85 00:15:12.83 +58:24:51.9
118.19069 -4.12347 galactic Cas Second-epoch detections are separated by 1.4" and 6.3 pix
The object was not found in VSX
The object was found in ASASSN-V14" ASASSN-V J001511.05+582452.4
Type: ROT
MeanMag 13.09 m Amp. 0.15 m Period 4.0710173 d
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:12.83 +58:24:51.9: 14.99 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:12.83 +58:24:51.9: 14.96 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.97 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 15 12.83 +58 24 51.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
VARIABLE_NAME,2461212.7242,12.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
VARIABLE_NAME 20260621.2242 12.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.85 00:16:43.33 +65:59:37.2
119.40621 3.35985 galactic Cas Second-epoch detections are separated by 6.6" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:43.33 +65:59:37.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:43.33 +65:59:37.2: 16.10 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:43.33 +65:59:37.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 06 21.2242* 00 16 43.33 +65 59 37.2 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 12.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.85 00:35:16.92 +63:00:42.3
121.10019 0.19747 galactic Cas Second-epoch detections are separated by 4.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430819721271142272 | 00:35:14.88 +63:00:41.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:35:16.92 +63:00:42.3: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:35:16.92 +63:00:42.3: 15.64 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 35 16.92 +63 00 42.3 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430819721271142272,2461212.7242,12.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430819721271142272 20260621.2242 12.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 12.89 00:21:58.05 +61:46:03.0
119.45370 -0.90506 galactic Cas Second-epoch detections are separated by 2.7" and 6.1 pix
The object was found in VSX 9" Gaia DR3 430450968254479872
Type: ROT
# Max. Min./Amp. JD0 Period
18.040 G 18.150 G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:21:58.05 +61:46:03.0: 14.28 +/- 0.09 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:21:58.05 +61:46:03.0: 13.81 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.96 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 21 58.05 +61 46 03.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
Gaia DR3 430450968254479872,2461212.7242,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430450968254479872 20260621.2242 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.04 23:59:35.73 +60:17:47.4
116.54759 -1.93105 galactic Cas Second-epoch detections are separated by 3.5" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J359.9106+60.2939 | 23:59:35.73 +60:17:47.4 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:59:35.73 +60:17:47.4: 14.12 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:59:35.73 +60:17:47.4: 14.42 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.23 +/- 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 06 21.2242* 23 59 35.73 +60 17 47.4 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 J359.9106+60.2939,2461212.7242,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.9106+60.2939 20260621.2242 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 06 21.2242 2461212.7242 12.98 00:01:41.55 +60:04:54.7
116.76129 -2.19255 galactic Cas Second-epoch detections are separated by 2.6" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 423324762823234048 | 00:01:37.57 +60:05:21.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A0 1955IzKry..14....3B [B55b] 5644
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:01:41.55 +60:04:54.7: 14.41 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:41.55 +60:04:54.7: 14.50 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.45 +/- 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 06 21.2242* 00 01 41.55 +60 04 54.7 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 423324762823234048,2461212.7242,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 423324762823234048 20260621.2242 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 06 21.2242 2461212.7242 13.11 00:04:32.58 +62:17:27.7
117.51048 -0.08608 galactic Cas Second-epoch detections are separated by 3.1" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:32.58 +62:17:27.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:04:32.58 +62:17:27.7: 15.60 +/- 0.27 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:32.58 +62:17:27.7: 15.71 +/- 0.31 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 06 21.2242* 00 04 32.58 +62 17 27.7 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.19 00:19:09.01 +63:34:25.4
119.34860 0.92684 galactic Cas Second-epoch detections are separated by 5.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 | 00:19:09.01 +63:34:25.4 (user input) | T | P | (position from user input) J-Ks=0.595+/-0.060 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:19:09.01 +63:34:25.4: 15.40 +/- 0.23 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:19:09.01 +63:34:25.4: 15.00 +/- 0.16 detection
Forced photometry reference-image weighted average: 15.13 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 19 09.01 +63 34 25.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
target,2461212.7242,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.16 23:38:45.88 +61:19:05.3
114.32503 -0.33328 galactic Cas Second-epoch detections are separated by 7.9" 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 | ASASSN-V J233841.62+611906.2 | 23:38:41.61 +61:19:05.8 (Gaia DR3) | L (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:38:45.88 +61:19:05.3: 14.33 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:38:45.88 +61:19:05.3: 14.14 +/- 0.07 detection
Forced photometry reference-image weighted average: 14.22 +/- 0.05
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 38 45.88 +61 19 05.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
ASASSN-V J233841.62+611906.2,2461212.7242,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J233841.62+611906.2 20260621.2242 13.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.16 00:00:32.22 +60:21:56.0
116.67554 -1.88642 galactic Cas Second-epoch detections are separated by 2.5" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:32.22 +60:21:56.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:00:32.22 +60:21:56.0: 14.48 +/- 0.09 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:00:32.22 +60:21:56.0: 14.61 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.53 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 00 32.22 +60 21 56.0 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,2461212.7242,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.16 00:30:24.48 +60:12:40.7
120.32015 -2.55376 galactic Cas Second-epoch detections are separated by 2.4" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 428618086677459456 | 00:30:24.38 +60:12:17.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: B3V 1960AAHam...5..215H Cl* NGC 129 Har 38
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:30:24.48 +60:12:40.7: 14.29 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:30:24.48 +60:12:40.7: 14.66 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.39 +/- 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 06 21.2242* 00 30 24.48 +60 12 40.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
Gaia DR3 428618086677459456,2461212.7242,13.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428618086677459456 20260621.2242 13.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.22 23:57:27.93 +61:03:13.8
116.44650 -1.13647 galactic Cas Second-epoch detections are separated by 2.9" 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:57:27.93 +61:03:13.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:57:27.93 +61:03:13.8: 14.14 +/- 0.08 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:27.93 +61:03:13.8: 14.15 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.15 +/- 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 06 21.2242* 23 57 27.93 +61 03 13.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,2461212.7242,13.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.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 06 21.2242 2461212.7242 13.19 00:05:44.65 +58:17:41.3
116.94225 -4.04455 galactic Cas Second-epoch detections are separated by 3.7" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.4433+58.3059 | 00:05:44.65 +58:17:41.3 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input) SpType: A5V (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:44.65 +58:17:41.3: 15.81 +/- 0.35 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:44.65 +58:17:41.3: 15.62 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.70 +/- 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 06 21.2242* 00 05 44.65 +58 17 41.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
ATO J001.4433+58.3059,2461212.7242,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.4433+58.3059 20260621.2242 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 06 21.2242 2461212.7242 13.21 23:56:27.62 +64:58:40.9
117.15782 2.72443 galactic Cas Second-epoch detections are separated by 3.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:56:27.62 +64:58:40.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:56:27.62 +64:58:40.9: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:56:27.62 +64:58:40.9: 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 06 21.2242* 23 56 27.62 +64 58 40.9 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,2461212.7242,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.29 00:10:26.89 +60:01:04.2
117.82682 -2.44700 galactic Cas Second-epoch detections are separated by 3.2" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.6312+60.0252 | 00:10:26.89 +60:01:04.2 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:26.89 +60:01:04.2: 15.04 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:10:26.89 +60:01:04.2: 14.65 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.79 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 10 26.89 +60 01 04.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
ATO J002.6312+60.0252,2461212.7242,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.6312+60.0252 20260621.2242 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 06 21.2242 2461212.7242 13.28 00:10:43.63 +59:41:30.1
117.80987 -2.77458 galactic Cas Second-epoch detections are separated by 5.2" and 6.5 pix
The object was found in VSX16" Gaia DR3 429059025197795456
Type: ROT
# Max. Min./Amp. JD0 Period
13.330 G 13.360 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:43.63 +59:41:30.1: 15.28 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:10:43.63 +59:41:30.1: 15.12 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.19 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 10 43.63 +59 41 30.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
Gaia DR3 429059025197795456,2461212.7242,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429059025197795456 20260621.2242 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 06 21.2242 2461212.7242 13.24 00:10:45.24 +59:41:48.0
117.81400 -2.77020 galactic Cas Second-epoch detections are separated by 3.4" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:45.24 +59:41:48.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:45.24 +59:41:48.0: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:10:45.24 +59:41:48.0: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 10 45.24 +59 41 48.0 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,2461212.7242,13.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.45 00:21:48.24 +61:02:48.7
119.35174 -1.61872 galactic Cas Second-epoch detections are separated by 1.5" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:21:48.24 +61:02:48.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:21:48.24 +61:02:48.7: 15.89 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:21:48.24 +61:02:48.7: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 21 48.24 +61 02 48.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.34 00:23:58.77 +60:58:55.6
119.60663 -1.71223 galactic Cas Second-epoch detections are separated by 2.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:58.77 +60:58:55.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:58.77 +60:58:55.6: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:23:58.77 +60:58:55.6: 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 06 21.2242* 00 23 58.77 +60 58 55.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,2461212.7242,13.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.38 00:35:30.84 +61:53:04.4
121.05681 -0.92920 galactic Cas Second-epoch detections are separated by 4.4" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:35:30.84 +61:53:04.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:35:30.84 +61:53:04.4: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:35:30.84 +61:53:04.4: 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 06 21.2242* 00 35 30.84 +61 53 04.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,2461212.7242,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.48 00:15:03.61 +61:26:02.0
118.59647 -1.13126 galactic Cas Second-epoch detections are separated by 3.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429599538245809280 | 00:14:59.83 +61:26:29.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:03.61 +61:26:02.0: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:03.61 +61:26:02.0: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 15 03.61 +61 26 02.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
Gaia DR3 429599538245809280,2461212.7242,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429599538245809280 20260621.2242 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.54 23:21:18.92 +64:45:52.5
113.51146 3.55409 galactic Cep Second-epoch detections are separated by 6.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:21:18.92 +64:45:52.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:21:18.92 +64:45:52.5: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:21:18.92 +64:45:52.5: 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,2461212.7242,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.47 00:01:39.33 +60:28:09.6
116.83117 -1.81140 galactic Cas Second-epoch detections are separated by 3.6" and 6.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J000.4352+60.4640 | 00:01:39.33 +60:28:09.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:01:39.33 +60:28:09.6: 14.62 +/- 0.11 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:39.33 +60:28:09.6: 14.46 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.53 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 01 39.33 +60 28 09.6 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.4352+60.4640,2461212.7242,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.4352+60.4640 20260621.2242 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 06 21.2242 2461212.7242 13.55 00:12:36.74 +62:53:05.4
118.52464 0.34580 galactic Cas Second-epoch detections are separated by 5.3" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:36.74 +62:53:05.4 (user input) | T | P | (position from user input) J-Ks=0.744+/- (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:12:36.74 +62:53:05.4: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:12:36.74 +62:53:05.4: 15.60 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.60 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 12 36.74 +62 53 05.4 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.58 00:23:46.13 +59:31:57.7
119.42557 -3.15055 galactic Cas Second-epoch detections are separated by 2.5" and 6.4 pix
The object was found in VSX16" Mis V1302
Type: M
# Max. Min./Amp. JD0 Period
14.231 r Y 4.383 r 2458514.64480 308.827887100000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:46.13 +59:31:57.7: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:23:46.13 +59:31:57.7: 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 06 21.2242* 00 23 46.13 +59 31 57.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
Mis V1302,2461212.7242,13.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Mis V1302 20260621.2242 13.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.56 00:14:58.18 +62:49:31.2
118.78200 0.24780 galactic Cas Second-epoch detections are separated by 4.4" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 431281000762096128 | 00:14:57.29 +62:50:13.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: OB- 1959LS....C01....0H LS I +62 81
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:14:58.18 +62:49:31.2: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:14:58.18 +62:49:31.2: 15.45 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 14 58.18 +62 49 31.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 431281000762096128,2461212.7242,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431281000762096128 20260621.2242 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.59 00:17:14.71 +62:51:13.3
119.04312 0.24040 galactic Cas Second-epoch detections are separated by 3.8" and 6.1 pix
The object was found in VSX20" Gaia DR3 431272269083225472
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.600 G 13.660 G 1.159660000000 B
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:14.71 +62:51:13.3: 15.77 +/- 0.36 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:14.71 +62:51:13.3: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.77 +/- 0.36
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 17 14.71 +62 51 13.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431272269083225472,2461212.7242,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431272269083225472 20260621.2242 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 06 21.2242 2461212.7242 13.48 00:36:27.91 +63:12:18.0
121.24541 0.38229 galactic Cas Second-epoch detections are separated by 4.7" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430824875231735552 | 00:36:32.14 +63:11:41.8 (Gaia DR3) | E (local) | A (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:36:27.91 +63:12:18.0: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:36:27.91 +63:12:18.0: 15.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 36 27.91 +63 12 18.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
Gaia DR3 430824875231735552,2461212.7242,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430824875231735552 20260621.2242 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.63 00:07:19.75 +59:57:32.0
117.43207 -2.44101 galactic Cas Second-epoch detections are separated by 2.7" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:19.75 +59:57:32.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:07:19.75 +59:57:32.0: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:07:19.75 +59:57:32.0: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 07 19.75 +59 57 32.0 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.54 00:27:16.43 +60:41:45.5
119.97748 -2.03709 galactic Cas Second-epoch detections are separated by 2.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 428836511532472960 | 00:27:13.15 +60:41:15.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:27:16.43 +60:41:45.5: 14.97 +/- 0.17 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:27:16.43 +60:41:45.5: 15.03 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.00 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 27 16.43 +60 41 45.5 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428836511532472960,2461212.7242,13.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428836511532472960 20260621.2242 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 06 21.2242 2461212.7242 13.43 00:00:05.68 +62:58:46.0
117.13885 0.68663 galactic Cas Second-epoch detections are separated by 0.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430057828437897984 | 00:00:05.00 +62:58:24.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:00:05.68 +62:58:46.0: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:00:05.68 +62:58:46.0: 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 06 21.2242* 00 00 05.68 +62 58 46.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 430057828437897984,2461212.7242,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430057828437897984 20260621.2242 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.48 00:15:43.87 +59:33:58.7
118.41764 -2.99211 galactic Cas Second-epoch detections are separated by 3.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 | 00:15:43.87 +59:33:58.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:43.87 +59:33:58.7: 14.81 +/- 0.12 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:43.87 +59:33:58.7: 15.02 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.89 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 15 43.87 +59 33 58.7 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,2461212.7242,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.58 00:30:05.05 +59:15:23.2
120.20074 -3.50202 galactic Cas Second-epoch detections are separated by 3.4" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.5115+59.2567 | 00:30:01.65 +59:15:49.3 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:30:05.05 +59:15:23.2: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:30:05.05 +59:15:23.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!
TCP 2026 06 21.2242* 00 30 05.05 +59 15 23.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
ATO J007.5115+59.2567,2461212.7242,13.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J007.5115+59.2567 20260621.2242 13.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.63 23:23:51.59 +65:45:15.0
114.09725 4.39589 galactic Cep Second-epoch detections are separated by 3.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:23:51.59 +65:45:15.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:23:51.59 +65:45:15.0: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:23:51.59 +65:45:15.0: 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
target,2461212.7242,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.75 00:28:28.57 +63:42:29.2
120.39229 0.94964 galactic Cas Second-epoch detections are separated by 6.6" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:28:28.57 +63:42:29.2 (user input) | T | P | (position from user input) J-Ks=1.345+/-0.103 (Very red! L if it's a dwarf)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:28:28.57 +63:42:29.2: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:28:28.57 +63:42:29.2: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 28 28.57 +63 42 29.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,2461212.7242,13.75,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.69 00:23:33.87 +65:19:38.3
120.02599 2.61294 galactic Cas Second-epoch detections are separated by 5.9" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:23:33.87 +65:19:38.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:33.87 +65:19:38.3: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:23:33.87 +65:19:38.3: 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 06 21.2242* 00 23 33.87 +65 19 38.3 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.69 00:08:23.26 +62:22:13.4
117.96381 -0.08537 galactic Cas Second-epoch detections are separated by 0.7" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429968974152693376 | 00:08:21.91 +62:22:59.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: B7IV 1956JO.....39..104D AG+62 10
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:08:23.26 +62:22:13.4: 14.49 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:08:23.26 +62:22:13.4: 14.91 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.62 +/- 0.09
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 08 23.26 +62 22 13.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
Gaia DR3 429968974152693376,2461212.7242,13.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429968974152693376 20260621.2242 13.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.74 00:34:37.36 +62:38:19.2
121.00120 -0.17003 galactic Cas Second-epoch detections are separated by 4.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:34:37.36 +62:38:19.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:34:37.36 +62:38:19.2: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:37.36 +62:38:19.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!
TCP 2026 06 21.2242* 00 34 37.36 +62 38 19.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
target,2461212.7242,13.74,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.74CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.66 00:34:59.46 +58:42:24.8
120.79209 -4.09651 galactic Cas Second-epoch detections are separated by 5.3" and 5.9 pix
The object was found in VSX17" Mis V1171
Type: M
# Max. Min./Amp. JD0 Period
18.782 g Y 5.734 g 2458285.31480 304.000000000000 M7
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:34:59.46 +58:42:24.8: 16.08 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:59.46 +58:42:24.8: 16.10 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 34 59.46 +58 42 24.8 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Mis V1171,2461212.7242,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Mis V1171 20260621.2242 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 06 21.2242 2461212.7242 13.93 00:09:22.22 +61:47:53.6
117.98324 -0.66866 galactic Cas Second-epoch detections are separated by 5.9" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:22.22 +61:47:53.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:22.22 +61:47:53.6: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:22.22 +61:47:53.6: 15.67 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.67 +/- 0.29
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 09 22.22 +61 47 53.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.95 00:00:51.74 +60:48:05.6
116.80001 -1.46664 galactic Cas Second-epoch detections are separated by 3.1" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:51.74 +60:48:05.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:00:51.74 +60:48:05.6: 15.94 +/- 0.31 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:00:51.74 +60:48:05.6: 16.02 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.94 +/- 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 06 21.2242* 00 00 51.74 +60 48 05.6 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 14.12 00:12:21.22 +60:34:37.7
118.14683 -1.93098 galactic Cas Second-epoch detections are separated by 4.0" and 6.2 pix
The object was found in VSX20" ZTF J001218.47+603439.1
Type: RS
# Max. Min./Amp. JD0 Period
14.158 r Y 0.065 r 2458493.36760 6.999803100000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:12:21.22 +60:34:37.7: 14.95 +/- 0.17 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:12:21.22 +60:34:37.7: 15.28 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.06 +/- 0.14
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 12 21.22 +60 34 37.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
ZTF J001218.47+603439.1,2461212.7242,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J001218.47+603439.1 20260621.2242 14.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.93 00:14:54.43 +58:38:28.0
118.18301 -3.89340 galactic Cas Second-epoch detections are separated by 4.7" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.7057+58.6349 | 00:14:54.43 +58:38:28.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:14:54.43 +58:38:28.0: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:14:54.43 +58:38:28.0: 15.67 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 14 54.43 +58 38 28.0 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J003.7057+58.6349,2461212.7242,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.7057+58.6349 20260621.2242 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.88 23:50:30.51 +59:35:29.8
115.28318 -2.37226 galactic Cas Second-epoch detections are separated by 4.3" 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 J357.6212+59.5947 | 23:50:30.51 +59:35:29.8 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:50:30.51 +59:35:29.8: 14.88 +/- 0.14 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:50:30.51 +59:35:29.8: 15.20 +/- 0.20 detection
Forced photometry reference-image weighted average: 14.98 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 50 30.51 +59 35 29.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.6212+59.5947,2461212.7242,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.6212+59.5947 20260621.2242 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 06 21.2242 2461212.7242 13.96 23:57:06.36 +63:28:49.7
116.91123 1.24562 galactic Cas Second-epoch detections are separated by 7.1" and 6.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:06.36 +63:28:49.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:57:06.36 +63:28:49.7: 15.71 +/- 0.33 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:06.36 +63:28:49.7: 15.82 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.71 +/- 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 06 21.2242* 23 57 06.36 +63 28 49.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.98 00:24:11.43 +62:20:23.3
119.77546 -0.36484 galactic Cas Second-epoch detections are separated by 5.9" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:11.43 +62:20:23.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:24:11.43 +62:20:23.3: 15.23 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:24:11.43 +62:20:23.3: 15.40 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 24 11.43 +62 20 23.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,2461212.7242,13.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.97 23:40:03.97 +61:54:53.4
114.63789 0.19784 galactic Cas Second-epoch detections are separated by 3.4" and 6.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 2015548957121790208 | 23:40:07.42 +61:55:29.4 (Gaia DR3) | L (local) | (local) | Gaia3var=NOT_AVAILABLE SpType: A0 1935BSD...C01....0S BSD 19-2056
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:40:03.97 +61:54:53.4: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:40:03.97 +61:54:53.4: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 40 03.97 +61 54 53.4 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 2015548957121790208,2461212.7242,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 2015548957121790208 20260621.2242 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 06 21.2242 2461212.7242 13.99 00:05:37.66 +62:31:52.3
117.67697 0.12777 galactic Cas Second-epoch detections are separated by 4.7" and 6.1 pix
The object was found in VSX19" Gaia DR3 429984809685184384
Type: ROT
# Max. Min./Amp. JD0 Period
15.240 G 15.290 G G
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:37.66 +62:31:52.3: 15.41 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:37.66 +62:31:52.3: 15.35 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 05 37.66 +62 31 52.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
Gaia DR3 429984809685184384,2461212.7242,13.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429984809685184384 20260621.2242 13.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.24 00:21:28.71 +60:49:23.3
119.28662 -1.83639 galactic Cas Second-epoch detections are separated by 2.1" 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 | Gaia DR3 428805931362608768 | 00:21:23.24 +60:49:38.8 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:21:28.71 +60:49:23.3: 16.05 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:21:28.71 +60:49:23.3: 16.08 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 21 28.71 +60 49 23.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428805931362608768,2461212.7242,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428805931362608768 20260621.2242 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.16 00:06:32.51 +58:44:43.0
117.12408 -3.61928 galactic Cas Second-epoch detections are separated by 6.6" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.6309+58.7471 | 00:06:32.51 +58:44:43.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:06:32.51 +58:44:43.0: 15.23 +/- 0.18 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:06:32.51 +58:44:43.0: 16.02 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.23 +/- 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 06 21.2242* 00 06 32.51 +58 44 43.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.6309+58.7471,2461212.7242,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.6309+58.7471 20260621.2242 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 14.20 00:32:50.33 +63:15:24.7
120.84132 0.46063 galactic Cas Second-epoch detections are separated by 7.8" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:50.33 +63:15:24.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:32:50.33 +63:15:24.7: 15.78 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:32:50.33 +63:15:24.7: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 32 50.33 +63 15 24.7 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.47 00:29:28.99 +60:49:52.4
120.25843 -1.92651 galactic Cas Second-epoch detections are separated by 3.9" and 6.1 pix
The object was found in VSX14" 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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:29:28.99 +60:49:52.4: 15.99 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:29:28.99 +60:49:52.4: 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 06 21.2242* 00 29 28.99 +60 49 52.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
NSVS J0029273+604956,2461212.7242,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0029273+604956 20260621.2242 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 06 21.2242 2461212.7242 13.25 23:58:38.28 +58:25:47.2
116.05102 -3.73481 galactic Cas Second-epoch detections are separated by 4.9" and 6.7 pix
The object was found in VSX18" 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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:58:38.28 +58:25:47.2: 16.03 +/- 0.32 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:58:38.28 +58:25:47.2: 16.08 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 16.03 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 58 38.28 +58 25 47.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
2MASS J23583604+5825441,2461212.7242,13.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 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 20260621.2242 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 06 21.2242 2461212.7242 12.62 00:07:43.09 +64:42:22.7
118.28166 2.23003 galactic Cas Second-epoch detections are separated by 3.7" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:43.09 +64:42:22.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:07:43.09 +64:42:22.7: 16.00 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:07:43.09 +64:42:22.7: 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 06 21.2242* 00 07 43.09 +64 42 22.7 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461212.7242,12.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 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 06 21.2242 2461212.7242 13.07 00:24:13.80 +57:57:08.4
119.31640 -4.72829 galactic Cas Second-epoch detections are separated by 3.2" and 6.1 pix
The object was found in VSX13" NSVS J0024122+575706
Type: SR
# Max. Min./Amp. JD0 Period
12.979 r Y 0.517 r 2458470.85960 232.234431800000 M6.5
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:24:13.80 +57:57:08.4: 16.08 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:24:13.80 +57:57:08.4: 15.98 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.98 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 00 24 13.80 +57 57 08.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
NSVS J0024122+575706,2461212.7242,13.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0024122+575706 20260621.2242 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 06 21.2242 2461212.7242 13.56 23:29:41.07 +64:59:25.2
114.42645 3.47736 galactic Cep Second-epoch detections are separated by 3.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:29:41.07 +64:59:25.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:29:41.07 +64:59:25.2: 16.11 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:29:41.07 +64:59:25.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,2461212.7242,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260621.2242 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 21.2242 2461212.7242 13.21 23:33:14.72 +58:27:40.5
112.83929 -2.86993 galactic Cas Second-epoch detections are separated by 5.5" and 6.6 pix
The object was found in VSX12" ASASSN-V J233313.58+582743.8
Type: SRA
# Max. Min./Amp. JD0 Period
13.036 r Y 1.529 r 2457656.80000 404.000000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:33:14.72 +58:27:40.5: 14.11 +/- 0.09 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:33:14.72 +58:27:40.5: 14.16 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.13 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 21.2242* 23 33 14.72 +58 27 40.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
ASASSN-V J233313.58+582743.8,2461212.7242,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J233313.58+582743.8 20260621.2242 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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461049.57276170 09.01.2026 01:44:36.611 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
First image: 2461049.57276170 09.01.2026 01:44:36.611 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
Last image: 2461212.72441962 21.06.2026 05:22:59.855 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 4
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: 7 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): 24154
Objects passed selection criteria: 24055
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 16989
Average stars matched: 15613 (91.9006 %)
Memory usage VmPeak: 127496 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 16 15:05:04 CDT 2026
VaST build number 1.0rc89-100-g8a7e82c2
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Jun 21 00:34:19 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: 2461049.57276170 09.01.2026 01:44:36.611 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
First image: 2461049.57276170 09.01.2026 01:44:36.611 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
Last image: 2461212.72441962 21.06.2026 05:22:59.855 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 224
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.34
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: 90 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): 187256
Objects passed selection criteria: 186677
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 138109
Average stars matched: 128059 (92.7228 %)
Memory usage VmPeak: 1938176 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 16 15:05:04 CDT 2026
VaST build number 1.0rc89-100-g8a7e82c2
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-16)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Sun Jun 21 01:12:44 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
SExtractor catalog cache: saved Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.cat to cache
SExtractor catalog cache: saved Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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: 2461212.72388233
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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits'
wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits exists and is non-empty
Saving wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits to local_wcs_cache/
'wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits' -> 'local_wcs_cache/wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits'
wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits'
wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits (1st reference image)
verification OK: wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
Image size: 943.5'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:58.941 +61:59:19.93 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-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Image size: 941.5'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.451 +62:00:01.20 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:58.941 +61:59:19.93
Second-epoch image center 00:00:06.451 +62:00:01.20
Angular distance between the image centers 0.0186 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Image size: 941.5'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:05.395 +62:00:38.17 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:58.941 +61:59:19.93
Second-epoch image center 00:00:05.395 +62:00:38.17
Angular distance between the image centers 0.0251 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:06.451 +62:00:01.20
Second-epoch second image center 00:00:05.395 +62:00:38.17
Angular distance between the image centers 0.01047 deg.
###################################
Running solve_plate_with_UCAC5...
Preparing for ar aprallel run
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits &> /tmp/tmp.WoFd8XsTmq
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits &> /tmp/tmp.FaOzzZS2El
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_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/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits &> /tmp/tmp.wWrMfIADvI
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits &> /tmp/tmp.6ql2yisaiE
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits and wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits and wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat
Found non-empty wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits and wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat
The reference image (wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits) and catalog (wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat) found
'wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat' -> 'wcsmag.cat'
Read 28928 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0003 to 359.9986 deg, Dec +55.3299 to +67.4085 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.0003 to 359.9986 deg, Dec 55.3299 to 67.4085 deg
Loaded 133379 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): 1544 out of 1735 total matches.
Matched with Tycho-2 1735 out of 28928 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.943100
a=0.000000 b=1.000000 c=22.943100
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 28928 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0003 to 359.9986 deg, Dec +55.3299 to +67.4085 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.0003 to 359.9986 deg, Dec 55.3299 to 67.4085 deg
Loaded 133379 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): 1544 out of 1735 total matches.
Matched with Tycho-2 1735 out of 28928 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits -> calib.txt_param_ref_wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits (aperture=5.8)
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-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits:
Forced-photometry filter: calibrated wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits -> calib.txt_param_ref_wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits (aperture=5.8)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 3 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.0 pix Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
2.1 pix Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
2.0 pix wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
2.1 pix wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Limiting magnitude estimates:
15.2 mag. Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
15.2 mag. Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
14.3 mag. fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
All-image limiting magnitude estimate: 14.3 (SNR ) 11.4 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.WoFd8XsTmq (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits' -> 'wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat corresponding to the image wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat corresponding to the image wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3732, passed=28928
Got 28928 stars (including 25166 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat
util/solve_plate_with_UCAC5 got 28928 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.9061, gap 19.9061 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 949 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 908 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.24"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 940 matched stars entering correct_measured_positions(), 26071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.51"
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.9054, gap 19.9054 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 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 26086 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.47"
Accuracy estimation diagnostic: 968 matched stars entering correct_measured_positions(), 26929 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 1.29"
Excluding outliers - 968 stars left (next iteration limit 1034)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits N_match=968 sigma_overall_arcsec=2.004 sigma_q1_arcsec=1.709 sigma_q2_arcsec=1.480 sigma_q3_arcsec=1.550 sigma_q4_arcsec=1.402 n_q1=148 n_q2=275 n_q3=232 n_q4=313 worst_quadrant_to_overall_ratio=0.853
The image catalog is written to wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits -region wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.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.FaOzzZS2El (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_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-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-02-Q2b1x1_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-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits' -> 'wcs_Cas-02-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS_IMAGE_NAME=wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS-calibrated image found: wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
Checking if the catalog wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat corresponding to the image wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits alredy exist and is non-empty...
Catalog wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat corresponding to the image wcs_Cas-02-Q2b1x1_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-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits
WCS catalog name: wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3591, passed=30191
Got 30191 stars (including 26565 good ones) from the SExtractor catalog wcs_Cas-02-Q2b1x1_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.1679 through 0 to 20.0647, gap 20.0647 to 341.1679
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(), 27226 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 2.53"
Accuracy estimation diagnostic: 963 matched stars entering correct_measured_positions(), 28091 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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits N_match=963 sigma_overall_arcsec=1.992 sigma_q1_arcsec=1.731 sigma_q2_arcsec=1.562 sigma_q3_arcsec=1.318 sigma_q4_arcsec=1.469 n_q1=158 n_q2=270 n_q3=234 n_q4=301 worst_quadrant_to_overall_ratio=0.869
The image catalog is written to wcs_Cas-02-Q2b1x1_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-Q2b1x1_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-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits -region wcs_Cas-02-Q2b1x1_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-Q2b1x1_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.wWrMfIADvI (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1137, passed=14618
Got 14618 stars (including 13470 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat
util/solve_plate_with_UCAC5 got 14618 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (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 340.6697 through 0 to 19.0210, gap 19.0210 to 340.6697
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 554 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 437 matched stars entering correct_measured_positions(), 397 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 420 matched stars entering correct_measured_positions(), 7233 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.39"
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 340.6644 through 0 to 19.0382, gap 19.0382 to 340.6644
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 626 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 557 matched stars entering correct_measured_positions(), 7316 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.27"
Accuracy estimation diagnostic: 556 matched stars entering correct_measured_positions(), 9167 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.70"
Excluding outliers - 556 stars left (next iteration limit 462)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits N_match=556 sigma_overall_arcsec=5.780 sigma_q1_arcsec=8.000 sigma_q2_arcsec=3.342 sigma_q3_arcsec=22.564 sigma_q4_arcsec=10.729 n_q1=173 n_q2=248 n_q3=56 n_q4=79 worst_quadrant_to_overall_ratio=3.904
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.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.6ql2yisaiE (6) ############
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1113, passed=14700
Got 14700 stars (including 13568 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat
util/solve_plate_with_UCAC5 got 14700 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (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 340.6697 through 0 to 19.0414, gap 19.0414 to 340.6697
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 555 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 437 matched stars entering correct_measured_positions(), 398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.21"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 421 matched stars entering correct_measured_positions(), 7242 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.49"
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 340.6657 through 0 to 19.0623, gap 19.0623 to 340.6657
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 626 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 550 matched stars entering correct_measured_positions(), 7322 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.44"
Accuracy estimation diagnostic: 548 matched stars entering correct_measured_positions(), 9126 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.99"
Excluding outliers - 548 stars left (next iteration limit 463)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits N_match=548 sigma_overall_arcsec=6.348 sigma_q1_arcsec=8.215 sigma_q2_arcsec=3.647 sigma_q3_arcsec=20.718 sigma_q4_arcsec=11.335 n_q1=180 n_q2=241 n_q3=53 n_q4=74 worst_quadrant_to_overall_ratio=3.263
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits sigma_overall=2.004 worst_q_ratio=0.853
ref2=Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits sigma_overall=1.992 worst_q_ratio=0.869
new1=fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits sigma_overall=5.780 worst_q_ratio=3.904
new2=fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits sigma_overall=6.348 worst_q_ratio=3.263
reference average sigma_overall=1.998 worst_q_ratio=0.861
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits) flagged: sigma=5.780 (ref avg 1.998), ratio=3.904 (ref avg 0.861), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00003.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/lib/make_outxyls_for_astrometric_calibration found 13982 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.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: "out2111532.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2111532.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 26.8675 (4.66028e+11), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0234958,61.9986), pixel scale 5.95074 arcsec/pix.
Hit/miss: Hit/miss: ++---+-+--+-+(best)--------------+----+----+--------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2111532.solved to indicate this.
Field: out2111532.xyls
Field center: (RA,Dec) = (0.025188, 61.999479) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:06.045, +61:59:58.125).
Field size: 15.7145 x 10.5177 degrees
Field rotation angle: up is -4.34684 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits' -> 'fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 21 00:46 fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
-rw-r--r-- 1 apache apache 8.5K Jun 21 00:46 out2111532.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits (fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.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: "out2111532.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2111532.axy"...
Only searching for solutions within 15.6917 degrees of RA,Dec (0.0268792,62.0003)
log-odds ratio 26.8675 (4.66028e+11), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0234958,61.9986), pixel scale 5.95074 arcsec/pix.
Hit/miss: Hit/miss: ++---+-+--+-+(best)--------------+----+----+--------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2111532.solved to indicate this.
Field: out2111532.xyls
Field center: (RA,Dec) = (0.025188, 61.999479) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:06.045, +61:59:58.125).
Field size: 15.7145 x 10.5177 degrees
Field rotation angle: up is -4.34684 degrees E of N
Field parity: neg
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 21 00:46 fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
-rw-r--r-- 1 apache apache 8.5K Jun 21 00:46 out2111532.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.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-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 77435 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.axy"...
Verifying WCS using indices with quads of size [63.3556, 949.738] 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 2.38174
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 1.75496
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 7.1101
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.45627
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 1.73012
Verifying WCS using indices with quads of size [63.3556, 949.738] 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 2.38174
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 1.75496
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 7.1101
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.45627
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 1.73012
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-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
Image size: 941.5'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.451 +62:00:01.20 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 14618 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/correct_sextractor_wcs_catalog_usingxy2sky2696292.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1137, passed=14618
Got 14618 stars (including 13470 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat
util/solve_plate_with_UCAC5 got 14618 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (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 340.6697 through 0 to 19.0210, gap 19.0210 to 340.6697
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 554 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 437 matched stars entering correct_measured_positions(), 397 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.06"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 420 matched stars entering correct_measured_positions(), 7233 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.39"
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 340.6644 through 0 to 19.0382, gap 19.0382 to 340.6644
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 626 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 557 matched stars entering correct_measured_positions(), 7316 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.27"
Accuracy estimation diagnostic: 556 matched stars entering correct_measured_positions(), 9167 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.70"
Excluding outliers - 556 stars left (next iteration limit 462)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits N_match=556 sigma_overall_arcsec=5.780 sigma_q1_arcsec=8.000 sigma_q2_arcsec=3.342 sigma_q3_arcsec=22.564 sigma_q4_arcsec=10.729 n_q1=173 n_q2=248 n_q3=56 n_q4=79 worst_quadrant_to_overall_ratio=3.904
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.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-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits): sigma 5.780->5.780, ratio 3.904->3.904; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits) flagged: sigma=6.348 (ref avg 1.998), ratio=3.263 (ref avg 0.861), threshold=2.0x. Retrying with --tweak-order 2.
Running with VAST_TWEAK_ORDER=2: util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Parsing command line arguments...
The minor axis of the CCD chip should be 24.0 mm based on the derived pixel size of 3.8 um
Internal estimated FoV 605.3'
The guess is based on the FOCALLEN keyword.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
It's not one of the telescopes that are know to produce images with good WCS solutions - will try to re-solve!
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits .... Determining astrometry method...
Using the local copy of Astrometry.net software...
Choosing aperture...
Using the catalog image00004.cat SExtracted earlier from the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/lib/make_outxyls_for_astrometric_calibration found 14063 high-SNR stars for plate solving
This service uses tools provided by Astrometry.net.
For more information visit http://astrometry.net/
######### Trying to solve plate assuming 605' field of view #########
/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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: "out2698527.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2698527.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 27.6466 (1.01567e+12), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0190933,62.0089), pixel scale 5.95075 arcsec/pix.
Hit/miss: Hit/miss: ++---+++----+(best)--+------------------+--+--------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2698527.solved to indicate this.
Field: out2698527.xyls
Field center: (RA,Dec) = (0.020786, 62.009748) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:04.989, +62:00:35.091).
Field size: 15.7144 x 10.5176 degrees
Field rotation angle: up is -4.33785 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits' -> 'fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 21 00:57 fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
-rw-r--r-- 1 apache apache 8.5K Jun 21 00:57 out2698527.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits)... done!
done!
All done!
done
The WCS header appears to be added with no errors in /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits (fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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: "out2698527.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out2698527.axy"...
Only searching for solutions within 15.6917 degrees of RA,Dec (0.0224792,62.0106)
log-odds ratio 27.6466 (1.01567e+12), 6 match, 0 conflict, 7 distractors, 28 index.
RA,Dec = (0.0190933,62.0089), pixel scale 5.95075 arcsec/pix.
Hit/miss: Hit/miss: ++---+++----+(best)--+------------------+--+--------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out2698527.solved to indicate this.
Field: out2698527.xyls
Field center: (RA,Dec) = (0.020786, 62.009748) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:04.989, +62:00:35.091).
Field size: 15.7144 x 10.5176 degrees
Field rotation angle: up is -4.33785 degrees E of N
Field parity: neg
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 21 00:57 fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
-rw-r--r-- 1 apache apache 8.5K Jun 21 00:57 out2698527.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 76990 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.axy"...
Verifying WCS using indices with quads of size [63.3556, 949.739] 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 5.475
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.18052
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 2.8308
Verifying WCS using indices with quads of size [63.3556, 949.739] 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 5.475
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 4.18052
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 2.8308
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-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
Image size: 941.5'x627.1' 15.7(deg)x10.5(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:05.395 +62:00:38.17 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 14700 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/correct_sextractor_wcs_catalog_usingxy2sky3872231.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1113, passed=14700
Got 14700 stars (including 13568 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat
util/solve_plate_with_UCAC5 got 14700 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (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 340.6697 through 0 to 19.0414, gap 19.0414 to 340.6697
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 555 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 437 matched stars entering correct_measured_positions(), 398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.21"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 421 matched stars entering correct_measured_positions(), 7242 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.49"
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 340.6657 through 0 to 19.0623, gap 19.0623 to 340.6657
Reading UCAC5 zone files...
Searching UCAC5 zones 728 to 788 (Dec 55.7 to 67.3)
Done reading UCAC5 zone files...
Matched 626 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 550 matched stars entering correct_measured_positions(), 7322 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.44"
Accuracy estimation diagnostic: 548 matched stars entering correct_measured_positions(), 9126 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.99"
Excluding outliers - 548 stars left (next iteration limit 463)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits N_match=548 sigma_overall_arcsec=6.348 sigma_q1_arcsec=8.215 sigma_q2_arcsec=3.647 sigma_q3_arcsec=20.718 sigma_q4_arcsec=11.335 n_q1=180 n_q2=241 n_q3=53 n_q4=74 worst_quadrant_to_overall_ratio=3.263
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.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-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits): sigma 6.348->6.348, ratio 3.263->3.263; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=5.780 -- 2.89x the reference average (1.998); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=6.348 -- 3.18x the reference average (1.998); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=3.904 -- 4.53x the reference average (0.861); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=3.263 -- 3.79x the reference average (0.861); plate solution may be of low accuracy
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011_astrometric_residuals.png (968 matched stars from wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 1.06 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014_astrometric_residuals.png (963 matched stars from wcs_Cas-02-Q2b1x1_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_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144_astrometric_residuals.png (556 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 2.93 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145_astrometric_residuals.png (548 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 3.09 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-13_20.00sec_4.90C_LIGHT_0144.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-21_CI_Cas-02-Q2b1x1_003152_TTUQ2b1x1_1538756_59psftg7/wcs_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145.fits'
Preparing the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:20:23.38 +62:23:43.2: 9.79 +/- 0.00 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:34:23.96 +64:31:45.8: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:20:23.38 +62:23:43.2: 9.72 +/- 0.00 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:23.96 +64:31:45.8: 15.88 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 9.75 +/- 0.00
Forced photometry filter REJECTED candidate at 00:20:23.38 +62:23:43.2: ref_mag=9.75 +/- 0.00 new_mean_mag=10.7771 delta=-1.03 (need > 0.90)
Adding exclusion_list_local.txt__out34110.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: 1s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32074_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 32074_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32443_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 32443_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246252_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246252_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246255_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246255_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246260_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246260_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246264_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246264_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (22.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246266_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246266_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246267_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246267_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246269_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246269_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246271_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246271_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246273_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246273_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246275_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246275_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246280_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246280_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246283_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246283_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246288_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246288_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246291_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246291_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246293_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246293_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246301_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246301_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246307_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246307_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246312_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246312_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246313_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246313_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246314_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246314_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246321_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246321_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246325_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246325_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246328_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246328_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246329_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246329_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246330_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246330_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246332_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246332_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246334_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246334_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246336_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246336_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246338_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246338_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (23.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246344_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246344_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246345_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246345_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246346_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246346_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246350_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246350_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246352_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246352_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246353_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246353_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 23:34:47.74 +58:11:01.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246359_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246359_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246360_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246360_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246362_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246362_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246368_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246368_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246371_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246371_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246372_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246372_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246373_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246373_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246374_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246374_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246375_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246375_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246377_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246377_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246379_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246379_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246381_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246381_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246384_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246384_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246385_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246385_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246386_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246386_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246387_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246387_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246392_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246392_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246393_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246393_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246394_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246394_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:10:45.07 +63:25:22.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246399_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246399_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246400_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246400_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246404_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246404_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246407_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246407_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246409_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246409_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246410_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 246410_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246414_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246414_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246415_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 246415_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:14:51.82 +62:50:05.2 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249161_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 249161_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249781_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 249781_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249983_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 249983_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250219_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 250219_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250401_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 250401_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251535_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 251535_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:36:21.76 +60:18:14.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252011_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 252011_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252110_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 252110_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252187_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 252187_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252406_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 252406_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252638_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 252638_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252895_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 252895_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253148_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 253148_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253267_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 253267_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253630_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 253630_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254571_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 254571_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254639_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 254639_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254644_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 254644_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255114_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 255114_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255367_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 255367_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255414_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 255414_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255526_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 255526_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255566_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 255566_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 256163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256684_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 256684_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257105_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257105_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257335_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257335_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257350_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257350_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257398_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257398_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257554_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257554_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257557_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257557_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257566_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 257566_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:05:15.71 +61:17:29.8 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257751_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257751_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257880_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 257880_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257961_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 257961_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258051_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 258051_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258074_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 258074_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258171_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 258171_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:09:14.03 +59:06:28.2 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258469_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 258469_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258567_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 258567_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258642_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 258642_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258723_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 258723_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258806_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 258806_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258913_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 258913_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:01:50.41 +61:12:22.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259319_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 259319_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259407_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259407_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259478_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259478_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259549_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 259549_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259584_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 259584_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259805_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259805_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:09:17.46 +59:06:03.0 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259878_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259878_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259889_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259889_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (12.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259917_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259917_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:01:42.75 +61:11:22.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259983_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 259983_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260380_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260380_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260395_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260395_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260406_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 260406_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260518_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260518_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260568_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260568_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260586_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 260586_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:23:55.37 +60:22:44.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260624_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 260624_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 23:49:01.38 +59:57:18.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260750_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260750_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260878_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 260878_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260947_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 260947_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261017_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 261017_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261233_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 261233_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261261_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 261261_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261265_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 261265_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261279_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 261279_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261281_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 261281_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261285_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 261285_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 23:48:48.41 +59:59:32.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261307_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 261307_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 261354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261506_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 261506_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262011_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262011_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262087_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262087_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262179_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 262179_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262197_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262197_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262389_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262389_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 23:29:49.38 +58:31:40.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262527_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262527_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262787_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 262787_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262905_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 262905_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262986_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 262986_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (29.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262990_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 262990_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263080_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 263080_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:16:39.85 +63:29:07.2 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.64, MAG_FAINT_SEARCH_LIMIT=14.62)GAIADR2_OUTPUT=# 4.738 431417134044654080 004.16383498512 +63.48620615768 13.9559 13.5465 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.738#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263216_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 263216_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263385_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 263385_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263785_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 263785_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263950_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 263950_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264045_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264045_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264157_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264157_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264297_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 264297_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264349_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264349_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264581_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264581_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264650_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264650_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264688_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 264688_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:17:11.39 +61:30:49.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265099_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 265099_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265656_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 265656_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265824_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 265824_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 266163_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266184_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 266184_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266194_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 266194_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266467_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 266467_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266506_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 266506_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266665_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 266665_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266751_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 266751_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266867_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 266867_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267009_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 267009_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267171_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 267171_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267198_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 267198_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 267354_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268386_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 268386_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268418_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 268418_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268500_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 268500_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268545_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 268545_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236991_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 236991_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 189730_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 189730_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30302_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 30302_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 98390_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 98390_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
Rejecting candidate due to large distance (36.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 233076_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 233076_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 190031_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 190031_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 49463_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 49463_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:36:59.67 +63:07:59.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 29265_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 29265_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 97063_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 97063_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:07:05.44 +61:48:57.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24334_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
The candidate 24334_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145 did not pass the final checks
**** FOUND 00:34:24.84 +64:31:46.3 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 186935_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
Preparing report for the candidate 186935_fd_Cas-02-Q2b1x1_2026-06-21_00-22-59_20.00sec_4.90C_LIGHT_0145
make_report_in_HTML.sh Phase 2 (HTML assembly): 5s
make_report_in_HTML.sh TOTAL: 227s
Prepared the HTML report for the field Cas-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
00:34:23.96 +64:31:45.8
23:33:14.72 +58:27:40.5
23:58:38.28 +58:25:47.2
00:24:13.80 +57:57:08.4
00:29:28.99 +60:49:52.4
00:05:04.17 +62:16:30.5
00:01:02.67 +63:08:17.9
23:21:32.26 +65:22:39.1
23:31:43.98 +63:17:24.9
23:58:05.41 +63:14:26.8
23:55:26.41 +62:57:17.5
00:23:14.08 +62:26:41.2
00:20:22.93 +60:15:48.4
23:57:08.74 +62:42:27.6
00:23:32.36 +60:00:49.8
00:14:44.88 +62:54:27.4
00:09:37.10 +63:17:37.5
00:13:32.08 +63:01:26.6
23:57:20.18 +59:53:22.3
00:05:44.49 +63:49:46.3
00:22:08.72 +63:58:07.8
00:15:49.72 +63:10:16.1
23:35:24.40 +57:34:22.0
00:17:54.84 +59:11:56.0
00:18:20.39 +58:11:24.5
23:59:12.04 +64:51:31.8
00:05:11.49 +61:07:04.8
00:02:05.99 +62:08:21.7
00:29:43.96 +58:56:37.3
00:02:24.80 +57:55:40.1
00:27:12.32 +61:09:29.6
00:11:17.00 +57:47:49.4
00:17:17.39 +62:50:56.1
23:52:29.20 +63:11:39.6
23:27:44.26 +57:24:28.2
00:03:26.62 +59:45:26.7
00:27:13.12 +61:50:40.8
00:15:54.56 +59:25:16.6
00:24:16.38 +61:50:54.3
00:30:25.66 +57:56:22.1
00:16:07.42 +63:38:24.7
00:00:26.79 +63:11:25.2
00:09:30.57 +62:35:17.5
00:18:27.47 +61:52:42.7
00:09:11.64 +63:10:36.0
23:23:08.41 +64:48:40.6
00:16:14.47 +60:59:35.9
00:20:28.90 +61:52:31.5
00:04:54.35 +61:20:34.7
00:21:27.24 +59:13:54.5
00:41:41.86 +65:49:36.8
23:42:49.59 +61:39:26.9
23:25:07.90 +61:36:03.3
00:15:12.83 +58:24:51.9
00:16:43.33 +65:59:37.2
00:35:16.92 +63:00:42.3
00:21:58.05 +61:46:03.0
23:59:35.73 +60:17:47.4
00:01:41.55 +60:04:54.7
00:04:32.58 +62:17:27.7
00:19:09.01 +63:34:25.4
23:38:45.88 +61:19:05.3
00:00:32.22 +60:21:56.0
00:30:24.48 +60:12:40.7
23:57:27.93 +61:03:13.8
00:05:44.65 +58:17:41.3
23:56:27.62 +64:58:40.9
00:10:26.89 +60:01:04.2
00:10:43.63 +59:41:30.1
00:10:45.24 +59:41:48.0
00:21:48.24 +61:02:48.7
00:23:58.77 +60:58:55.6
00:35:30.84 +61:53:04.4
00:15:03.61 +61:26:02.0
23:21:18.92 +64:45:52.5
00:01:39.33 +60:28:09.6
00:12:36.74 +62:53:05.4
00:23:46.13 +59:31:57.7
00:14:58.18 +62:49:31.2
00:17:14.71 +62:51:13.3
00:36:27.91 +63:12:18.0
00:07:19.75 +59:57:32.0
00:27:16.43 +60:41:45.5
00:00:05.68 +62:58:46.0
00:15:43.87 +59:33:58.7
00:30:05.05 +59:15:23.2
23:23:51.59 +65:45:15.0
00:28:28.57 +63:42:29.2
00:23:33.87 +65:19:38.3
00:08:23.26 +62:22:13.4
00:34:37.36 +62:38:19.2
00:34:59.46 +58:42:24.8
00:09:22.22 +61:47:53.6
00:00:51.74 +60:48:05.6
00:12:21.22 +60:34:37.7
00:14:54.43 +58:38:28.0
23:50:30.51 +59:35:29.8
23:57:06.36 +63:28:49.7
00:24:11.43 +62:20:23.3
23:40:03.97 +61:54:53.4
00:05:37.66 +62:31:52.3
00:21:28.71 +60:49:23.3
00:06:32.51 +58:44:43.0
00:32:50.33 +63:15:24.7
23:29:41.07 +64:59:25.2
00:07:43.09 +64:42:22.7
########### Completed Cas-02-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
00:34:23.96 +64:31:45.8
00:05:04.17 +62:16:30.5
00:01:02.67 +63:08:17.9
23:21:32.26 +65:22:39.1
23:31:43.98 +63:17:24.9
23:58:05.41 +63:14:26.8
23:55:26.41 +62:57:17.5
00:23:14.08 +62:26:41.2
00:20:22.93 +60:15:48.4
23:57:08.74 +62:42:27.6
00:23:32.36 +60:00:49.8
00:14:44.88 +62:54:27.4
00:09:37.10 +63:17:37.5
00:13:32.08 +63:01:26.6
23:57:20.18 +59:53:22.3
00:05:44.49 +63:49:46.3
00:22:08.72 +63:58:07.8
00:15:49.72 +63:10:16.1
23:35:24.40 +57:34:22.0
00:17:54.84 +59:11:56.0
00:18:20.39 +58:11:24.5
23:59:12.04 +64:51:31.8
00:05:11.49 +61:07:04.8
00:02:05.99 +62:08:21.7
00:29:43.96 +58:56:37.3
00:02:24.80 +57:55:40.1
00:27:12.32 +61:09:29.6
00:11:17.00 +57:47:49.4
00:17:17.39 +62:50:56.1
23:52:29.20 +63:11:39.6
23:27:44.26 +57:24:28.2
00:03:26.62 +59:45:26.7
00:27:13.12 +61:50:40.8
00:15:54.56 +59:25:16.6
00:24:16.38 +61:50:54.3
00:30:25.66 +57:56:22.1
00:16:07.42 +63:38:24.7
00:00:26.79 +63:11:25.2
00:09:30.57 +62:35:17.5
00:18:27.47 +61:52:42.7
00:09:11.64 +63:10:36.0
23:23:08.41 +64:48:40.6
00:16:14.47 +60:59:35.9
00:20:28.90 +61:52:31.5
00:04:54.35 +61:20:34.7
00:21:27.24 +59:13:54.5
00:41:41.86 +65:49:36.8
23:42:49.59 +61:39:26.9
23:25:07.90 +61:36:03.3
00:15:12.83 +58:24:51.9
00:16:43.33 +65:59:37.2
00:35:16.92 +63:00:42.3
00:21:58.05 +61:46:03.0
23:59:35.73 +60:17:47.4
00:01:41.55 +60:04:54.7
00:04:32.58 +62:17:27.7
00:19:09.01 +63:34:25.4
23:38:45.88 +61:19:05.3
00:00:32.22 +60:21:56.0
00:30:24.48 +60:12:40.7
23:57:27.93 +61:03:13.8
00:05:44.65 +58:17:41.3
23:56:27.62 +64:58:40.9
00:10:26.89 +60:01:04.2
00:10:43.63 +59:41:30.1
00:10:45.24 +59:41:48.0
00:21:48.24 +61:02:48.7
00:23:58.77 +60:58:55.6
00:35:30.84 +61:53:04.4
00:15:03.61 +61:26:02.0
23:21:18.92 +64:45:52.5
00:01:39.33 +60:28:09.6
00:12:36.74 +62:53:05.4
00:23:46.13 +59:31:57.7
00:14:58.18 +62:49:31.2
00:17:14.71 +62:51:13.3
00:36:27.91 +63:12:18.0
00:07:19.75 +59:57:32.0
00:27:16.43 +60:41:45.5
00:00:05.68 +62:58:46.0
00:15:43.87 +59:33:58.7
00:30:05.05 +59:15:23.2
23:23:51.59 +65:45:15.0
00:28:28.57 +63:42:29.2
00:23:33.87 +65:19:38.3
00:08:23.26 +62:22:13.4
00:34:37.36 +62:38:19.2
00:34:59.46 +58:42:24.8
00:09:22.22 +61:47:53.6
00:00:51.74 +60:48:05.6
00:12:21.22 +60:34:37.7
00:14:54.43 +58:38:28.0
23:50:30.51 +59:35:29.8
23:57:06.36 +63:28:49.7
00:24:11.43 +62:20:23.3
23:40:03.97 +61:54:53.4
00:05:37.66 +62:31:52.3
00:21:28.71 +60:49:23.3
00:06:32.51 +58:44:43.0
00:32:50.33 +63:15:24.7
00:29:28.99 +60:49:52.4
23:58:38.28 +58:25:47.2
00:07:43.09 +64:42:22.7
00:24:13.80 +57:57:08.4
23:29:41.07 +64:59:25.2
23:33:14.72 +58:27:40.5
###################################################################################
00:34:23.96 +64:31:45.8 -- not an asteroid (will add it to exclusion list)
00:05:04.17 +62:16:30.5 -- not an asteroid (will add it to exclusion list)
00:01:02.67 +63:08:17.9 -- not an asteroid (will add it to exclusion list)
23:21:32.26 +65:22:39.1 -- not an asteroid (will add it to exclusion list)
23:31:43.98 +63:17:24.9 -- not an asteroid (will add it to exclusion list)
23:58:05.41 +63:14:26.8 -- not an asteroid (will add it to exclusion list)
23:55:26.41 +62:57:17.5 -- not an asteroid (will add it to exclusion list)
00:23:14.08 +62:26:41.2 -- not an asteroid (will add it to exclusion list)
00:20:22.93 +60:15:48.4 -- not an asteroid (will add it to exclusion list)
23:57:08.74 +62:42:27.6 -- not an asteroid (will add it to exclusion list)
00:23:32.36 +60:00:49.8 -- not an asteroid (will add it to exclusion list)
00:14:44.88 +62:54:27.4 -- not an asteroid (will add it to exclusion list)
00:09:37.10 +63:17:37.5 -- not an asteroid (will add it to exclusion list)
00:13:32.08 +63:01:26.6 -- not an asteroid (will add it to exclusion list)
23:57:20.18 +59:53:22.3 -- not an asteroid (will add it to exclusion list)
00:05:44.49 +63:49:46.3 -- not an asteroid (will add it to exclusion list)
00:22:08.72 +63:58:07.8 -- not an asteroid (will add it to exclusion list)
00:15:49.72 +63:10:16.1 -- not an asteroid (will add it to exclusion list)
23:35:24.40 +57:34:22.0 -- not an asteroid (will add it to exclusion list)
00:17:54.84 +59:11:56.0 -- not an asteroid (will add it to exclusion list)
00:18:20.39 +58:11:24.5 -- not an asteroid (will add it to exclusion list)
23:59:12.04 +64:51:31.8 -- not an asteroid (will add it to exclusion list)
00:05:11.49 +61:07:04.8 -- not an asteroid (will add it to exclusion list)
00:02:05.99 +62:08:21.7 -- not an asteroid (will add it to exclusion list)
00:29:43.96 +58:56:37.3 -- not an asteroid (will add it to exclusion list)
00:02:24.80 +57:55:40.1 -- not an asteroid (will add it to exclusion list)
00:27:12.32 +61:09:29.6 -- not an asteroid (will add it to exclusion list)
00:11:17.00 +57:47:49.4 -- not an asteroid (will add it to exclusion list)
00:17:17.39 +62:50:56.1 -- not an asteroid (will add it to exclusion list)
23:52:29.20 +63:11:39.6 -- not an asteroid (will add it to exclusion list)
23:27:44.26 +57:24:28.2 -- not an asteroid (will add it to exclusion list)
00:03:26.62 +59:45:26.7 -- not an asteroid (will add it to exclusion list)
00:27:13.12 +61:50:40.8 -- not an asteroid (will add it to exclusion list)
00:15:54.56 +59:25:16.6 -- not an asteroid (will add it to exclusion list)
00:24:16.38 +61:50:54.3 -- not an asteroid (will add it to exclusion list)
00:30:25.66 +57:56:22.1 -- not an asteroid (will add it to exclusion list)
00:16:07.42 +63:38:24.7 -- not an asteroid (will add it to exclusion list)
00:00:26.79 +63:11:25.2 -- not an asteroid (will add it to exclusion list)
00:09:30.57 +62:35:17.5 -- not an asteroid (will add it to exclusion list)
00:18:27.47 +61:52:42.7 -- not an asteroid (will add it to exclusion list)
00:09:11.64 +63:10:36.0 -- not an asteroid (will add it to exclusion list)
23:23:08.41 +64:48:40.6 -- not an asteroid (will add it to exclusion list)
00:16:14.47 +60:59:35.9 -- not an asteroid (will add it to exclusion list)
00:20:28.90 +61:52:31.5 -- not an asteroid (will add it to exclusion list)
00:04:54.35 +61:20:34.7 -- not an asteroid (will add it to exclusion list)
00:21:27.24 +59:13:54.5 -- not an asteroid (will add it to exclusion list)
00:41:41.86 +65:49:36.8 -- not an asteroid (will add it to exclusion list)
23:42:49.59 +61:39:26.9 -- not an asteroid (will add it to exclusion list)
23:25:07.90 +61:36:03.3 -- not an asteroid (will add it to exclusion list)
00:15:12.83 +58:24:51.9 -- not an asteroid (will add it to exclusion list)
00:16:43.33 +65:59:37.2 -- not an asteroid (will add it to exclusion list)
00:35:16.92 +63:00:42.3 -- not an asteroid (will add it to exclusion list)
00:21:58.05 +61:46:03.0 -- not an asteroid (will add it to exclusion list)
23:59:35.73 +60:17:47.4 -- not an asteroid (will add it to exclusion list)
00:01:41.55 +60:04:54.7 -- not an asteroid (will add it to exclusion list)
00:04:32.58 +62:17:27.7 -- not an asteroid (will add it to exclusion list)
00:19:09.01 +63:34:25.4 -- not an asteroid (will add it to exclusion list)
23:38:45.88 +61:19:05.3 -- not an asteroid (will add it to exclusion list)
00:00:32.22 +60:21:56.0 -- not an asteroid (will add it to exclusion list)
00:30:24.48 +60:12:40.7 -- not an asteroid (will add it to exclusion list)
23:57:27.93 +61:03:13.8 -- not an asteroid (will add it to exclusion list)
00:05:44.65 +58:17:41.3 -- not an asteroid (will add it to exclusion list)
23:56:27.62 +64:58:40.9 -- not an asteroid (will add it to exclusion list)
00:10:26.89 +60:01:04.2 -- not an asteroid (will add it to exclusion list)
00:10:43.63 +59:41:30.1 -- not an asteroid (will add it to exclusion list)
00:10:45.24 +59:41:48.0 -- not an asteroid (will add it to exclusion list)
00:21:48.24 +61:02:48.7 -- not an asteroid (will add it to exclusion list)
00:23:58.77 +60:58:55.6 -- not an asteroid (will add it to exclusion list)
00:35:30.84 +61:53:04.4 -- not an asteroid (will add it to exclusion list)
00:15:03.61 +61:26:02.0 -- not an asteroid (will add it to exclusion list)
23:21:18.92 +64:45:52.5 -- not an asteroid (will add it to exclusion list)
00:01:39.33 +60:28:09.6 -- not an asteroid (will add it to exclusion list)
00:12:36.74 +62:53:05.4 -- not an asteroid (will add it to exclusion list)
00:23:46.13 +59:31:57.7 -- not an asteroid (will add it to exclusion list)
00:14:58.18 +62:49:31.2 -- not an asteroid (will add it to exclusion list)
00:17:14.71 +62:51:13.3 -- not an asteroid (will add it to exclusion list)
00:36:27.91 +63:12:18.0 -- not an asteroid (will add it to exclusion list)
00:07:19.75 +59:57:32.0 -- not an asteroid (will add it to exclusion list)
00:27:16.43 +60:41:45.5 -- not an asteroid (will add it to exclusion list)
00:00:05.68 +62:58:46.0 -- not an asteroid (will add it to exclusion list)
00:15:43.87 +59:33:58.7 -- not an asteroid (will add it to exclusion list)
00:30:05.05 +59:15:23.2 -- not an asteroid (will add it to exclusion list)
23:23:51.59 +65:45:15.0 -- not an asteroid (will add it to exclusion list)
00:28:28.57 +63:42:29.2 -- not an asteroid (will add it to exclusion list)
00:23:33.87 +65:19:38.3 -- not an asteroid (will add it to exclusion list)
00:08:23.26 +62:22:13.4 -- not an asteroid (will add it to exclusion list)
00:34:37.36 +62:38:19.2 -- not an asteroid (will add it to exclusion list)
00:34:59.46 +58:42:24.8 -- not an asteroid (will add it to exclusion list)
00:09:22.22 +61:47:53.6 -- not an asteroid (will add it to exclusion list)
00:00:51.74 +60:48:05.6 -- not an asteroid (will add it to exclusion list)
00:12:21.22 +60:34:37.7 -- not an asteroid (will add it to exclusion list)
00:14:54.43 +58:38:28.0 -- not an asteroid (will add it to exclusion list)
23:50:30.51 +59:35:29.8 -- not an asteroid (will add it to exclusion list)
23:57:06.36 +63:28:49.7 -- not an asteroid (will add it to exclusion list)
00:24:11.43 +62:20:23.3 -- not an asteroid (will add it to exclusion list)
23:40:03.97 +61:54:53.4 -- not an asteroid (will add it to exclusion list)
00:05:37.66 +62:31:52.3 -- not an asteroid (will add it to exclusion list)
00:21:28.71 +60:49:23.3 -- not an asteroid (will add it to exclusion list)
00:06:32.51 +58:44:43.0 -- not an asteroid (will add it to exclusion list)
00:32:50.33 +63:15:24.7 -- not an asteroid (will add it to exclusion list)
00:29:28.99 +60:49:52.4 -- not an asteroid (will add it to exclusion list)
23:58:38.28 +58:25:47.2 -- not an asteroid (will add it to exclusion list)
00:07:43.09 +64:42:22.7 -- not an asteroid (will add it to exclusion list)
00:24:13.80 +57:57:08.4 -- not an asteroid (will add it to exclusion list)
23:29:41.07 +64:59:25.2 -- not an asteroid (will add it to exclusion list)
23:33:14.72 +58:27:40.5 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:05.68 +62:58:46.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:26.79 +63:11:25.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:32.22 +60:21:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:51.74 +60:48:05.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:02.67 +63:08:17.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:39.33 +60:28:09.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:41.55 +60:04:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:05.99 +62:08:21.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:24.80 +57:55:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:26.62 +59:45:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:32.58 +62:17:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:54.35 +61:20:34.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:04.17 +62:16:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:11.49 +61:07:04.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:37.66 +62:31:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:44.49 +63:49:46.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:44.65 +58:17:41.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:32.51 +58:44:43.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:19.75 +59:57:32.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:43.09 +64:42:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:23.26 +62:22:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:11.64 +63:10:36.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:22.22 +61:47:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:30.57 +62:35:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:37.10 +63:17:37.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:26.89 +60:01:04.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:43.63 +59:41:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:45.24 +59:41:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:17.00 +57:47:49.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:21.22 +60:34:37.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:36.74 +62:53:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:32.08 +63:01:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:44.88 +62:54:27.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:54.43 +58:38:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:58.18 +62:49:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:03.61 +61:26:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:12.83 +58:24:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:43.87 +59:33:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:49.72 +63:10:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:54.56 +59:25:16.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:07.42 +63:38:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:14.47 +60:59:35.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:43.33 +65:59:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:14.71 +62:51:13.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:17.39 +62:50:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:54.84 +59:11:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:20.39 +58:11:24.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:27.47 +61:52:42.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:09.01 +63:34:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:22.93 +60:15:48.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:28.90 +61:52:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:27.24 +59:13:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:28.71 +60:49:23.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:48.24 +61:02:48.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:58.05 +61:46:03.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:08.72 +63:58:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:14.08 +62:26:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:32.36 +60:00:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:33.87 +65:19:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:46.13 +59:31:57.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:58.77 +60:58:55.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:11.43 +62:20:23.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:13.80 +57:57:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:16.38 +61:50:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:12.32 +61:09:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:13.12 +61:50:40.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:16.43 +60:41:45.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:28.57 +63:42:29.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:28.99 +60:49:52.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:43.96 +58:56:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:05.05 +59:15:23.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:24.48 +60:12:40.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:25.66 +57:56:22.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:50.33 +63:15:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:23.96 +64:31:45.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:37.36 +62:38:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:59.46 +58:42:24.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:16.92 +63:00:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:30.84 +61:53:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:27.91 +63:12:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:41.86 +65:49:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:18.92 +64:45:52.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:21:32.26 +65:22:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:08.41 +64:48:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:51.59 +65:45:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:07.90 +61:36:03.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:44.26 +57:24:28.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:41.07 +64:59:25.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:43.98 +63:17:24.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:14.72 +58:27:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:24.40 +57:34:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:45.88 +61:19:05.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:03.97 +61:54:53.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:49.59 +61:39:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:30.51 +59:35:29.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:29.20 +63:11:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:26.41 +62:57:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:27.62 +64:58:40.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:06.36 +63:28:49.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:08.74 +62:42:27.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:20.18 +59:53:22.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:27.93 +61:03:13.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:05.41 +63:14:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:38.28 +58:25:47.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:12.04 +64:51:31.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:35.73 +60:17:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:00:05.68 +62:58:46.0 -- not a known variable star
00:00:26.79 +63:11:25.2 -- a known variable star
00:00:32.22 +60:21:56.0 -- not a known variable star
00:00:51.74 +60:48:05.6 -- not a known variable star
00:01:02.67 +63:08:17.9 -- not a known variable star
00:01:39.33 +60:28:09.6 -- not a known variable star
00:01:41.55 +60:04:54.7 -- not a known variable star
00:02:05.99 +62:08:21.7 -- not a known variable star
00:02:24.80 +57:55:40.1 -- not a known variable star
00:03:26.62 +59:45:26.7 -- not a known variable star
00:04:32.58 +62:17:27.7 -- not a known variable star
00:04:54.35 +61:20:34.7 -- a known variable star
00:05:04.17 +62:16:30.5 -- not a known variable star
00:05:11.49 +61:07:04.8 -- not a known variable star
00:05:37.66 +62:31:52.3 -- a known variable star
00:05:44.49 +63:49:46.3 -- not a known variable star
00:05:44.65 +58:17:41.3 -- not a known variable star
00:06:32.51 +58:44:43.0 -- not a known variable star
00:07:19.75 +59:57:32.0 -- not a known variable star
00:07:43.09 +64:42:22.7 -- not a known variable star
00:08:23.26 +62:22:13.4 -- not a known variable star
00:09:11.64 +63:10:36.0 -- not a known variable star
00:09:22.22 +61:47:53.6 -- not a known variable star
00:09:30.57 +62:35:17.5 -- not a known variable star
00:09:37.10 +63:17:37.5 -- not a known variable star
00:10:26.89 +60:01:04.2 -- not a known variable star
00:10:43.63 +59:41:30.1 -- a known variable star
00:10:45.24 +59:41:48.0 -- not a known variable star
00:11:17.00 +57:47:49.4 -- not a known variable star
00:12:21.22 +60:34:37.7 -- a known variable star
00:12:36.74 +62:53:05.4 -- not a known variable star
00:13:32.08 +63:01:26.6 -- not a known variable star
00:14:44.88 +62:54:27.4 -- a known variable star
00:14:54.43 +58:38:28.0 -- not a known variable star
00:14:58.18 +62:49:31.2 -- not a known variable star
00:15:03.61 +61:26:02.0 -- not a known variable star
00:15:12.83 +58:24:51.9 -- a known variable star
00:15:43.87 +59:33:58.7 -- not a known variable star
00:15:49.72 +63:10:16.1 -- a known variable star
00:15:54.56 +59:25:16.6 -- not a known variable star
00:16:07.42 +63:38:24.7 -- not a known variable star
00:16:14.47 +60:59:35.9 -- not a known variable star
00:16:43.33 +65:59:37.2 -- not a known variable star
00:17:14.71 +62:51:13.3 -- a known variable star
00:17:17.39 +62:50:56.1 -- a known variable star
00:17:54.84 +59:11:56.0 -- not a known variable star
00:18:20.39 +58:11:24.5 -- not a known variable star
00:18:27.47 +61:52:42.7 -- not a known variable star
00:19:09.01 +63:34:25.4 -- not a known variable star
00:20:22.93 +60:15:48.4 -- not a known variable star
00:20:28.90 +61:52:31.5 -- not a known variable star
00:21:27.24 +59:13:54.5 -- a known variable star
00:21:28.71 +60:49:23.3 -- not a known variable star
00:21:48.24 +61:02:48.7 -- not a known variable star
00:21:58.05 +61:46:03.0 -- a known variable star
00:22:08.72 +63:58:07.8 -- a known variable star
00:23:14.08 +62:26:41.2 -- not a known variable star
00:23:32.36 +60:00:49.8 -- a known variable star
00:23:33.87 +65:19:38.3 -- not a known variable star
00:23:46.13 +59:31:57.7 -- a known variable star
00:23:58.77 +60:58:55.6 -- not a known variable star
00:24:11.43 +62:20:23.3 -- not a known variable star
00:24:13.80 +57:57:08.4 -- a known variable star
00:24:16.38 +61:50:54.3 -- a known variable star
00:27:12.32 +61:09:29.6 -- not a known variable star
00:27:13.12 +61:50:40.8 -- not a known variable star
00:27:16.43 +60:41:45.5 -- not a known variable star
00:28:28.57 +63:42:29.2 -- not a known variable star
00:29:28.99 +60:49:52.4 -- a known variable star
00:29:43.96 +58:56:37.3 -- not a known variable star
00:30:05.05 +59:15:23.2 -- not a known variable star
00:30:24.48 +60:12:40.7 -- not a known variable star
00:30:25.66 +57:56:22.1 -- not a known variable star
00:32:50.33 +63:15:24.7 -- not a known variable star
00:34:23.96 +64:31:45.8 -- not a known variable star
00:34:37.36 +62:38:19.2 -- not a known variable star
00:34:59.46 +58:42:24.8 -- a known variable star
00:35:16.92 +63:00:42.3 -- not a known variable star
00:35:30.84 +61:53:04.4 -- not a known variable star
00:36:27.91 +63:12:18.0 -- not a known variable star
00:41:41.86 +65:49:36.8 -- not a known variable star
23:21:18.92 +64:45:52.5 -- not a known variable star
23:21:32.26 +65:22:39.1 -- a known variable star
23:23:08.41 +64:48:40.6 -- not a known variable star
23:23:51.59 +65:45:15.0 -- not a known variable star
23:25:07.90 +61:36:03.3 -- a known variable star
23:27:44.26 +57:24:28.2 -- not a known variable star
23:29:41.07 +64:59:25.2 -- not a known variable star
23:31:43.98 +63:17:24.9 -- not a known variable star
23:33:14.72 +58:27:40.5 -- a known variable star
23:35:24.40 +57:34:22.0 -- not a known variable star
23:38:45.88 +61:19:05.3 -- not a known variable star
23:40:03.97 +61:54:53.4 -- not a known variable star
23:42:49.59 +61:39:26.9 -- not a known variable star
23:50:30.51 +59:35:29.8 -- not a known variable star
23:52:29.20 +63:11:39.6 -- not a known variable star
23:55:26.41 +62:57:17.5 -- not a known variable star
23:56:27.62 +64:58:40.9 -- not a known variable star
23:57:06.36 +63:28:49.7 -- not a known variable star
23:57:08.74 +62:42:27.6 -- not a known variable star
23:57:20.18 +59:53:22.3 -- not a known variable star
23:57:27.93 +61:03:13.8 -- not a known variable star
23:58:05.41 +63:14:26.8 -- not a known variable star
23:58:38.28 +58:25:47.2 -- a known variable star
23:59:12.04 +64:51:31.8 -- not a known variable star
23:59:35.73 +60:17:47.4 -- not a known variable star
Found 83 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
106 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 106 (excluding asteroids and hot pixels, 83 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)2461212.72388233 -observatory V36
07:39:56.39 +21:24:13.0 Mercury (0.9mag)
08:46:28.04 +20:00:50.0 Venus (-4.0mag)
03:27:41.11 +18:24:49.1 Mars (1.3mag)
07:59:34.72 +21:02:03.2 Jupiter (-1.8mag)
00:52:40.29 +03:06:03.8 Saturn (0.8mag)
04:03:13.74 +20:34:02.4 Uranus (5.8mag)
00:16:44.72 +00:19:58.9 Neptune (7.8mag)
20:32:30.76 -23:09:43.7 Pluto (14.5mag)
11:22:04.13 +01:22:47.9 Moon (-10.1mag)
-rw-r--r-- 1 apache apache 362 Jun 21 00:34 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461212.72388233:
07:59:41.11 +21:01:41.7 Io (6.2mag)
07:59:27.38 +21:02:27.1 Europa (6.3mag)
07:59:30.99 +21:02:11.3 Ganymede (5.6mag)
08:00:02.59 +21:00:36.3 Callisto (6.9mag)
07:59:06.10 +20:40:11.2 Himalia (15.6mag)
07:59:34.96 +21:02:02.7 Thebe (16.6mag)
07:58:44.57 +20:50:19.1 Elara (17.6mag)
08:02:23.11 +21:06:37.4 Pasiphae (17.8mag)
08:05:33.44 +21:04:52.3 Carme (18.9mag)
00:52:31.85 +03:06:28.9 Titan (8.6mag)
00:52:40.07 +03:06:16.8 Rhea (9.9mag)
00:52:52.25 +03:08:23.0 Iapetus (11.3mag)
00:52:40.09 +03:06:34.2 Hyperion (14.6mag)
00:53:06.18 +03:06:06.4 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jun 21 00:34 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461212.72388233:
17:29:37.55 -35:29:59.3 JWST
11:43:12.09 +54:28:40.5 Chandra
08:44:38.32 -49:02:11.7 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jun 21 00:34 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461212.72388233 -observatory V36
18:33:36.09 -33:31:10.2 13.6mag P/2010 H2 (Vales)
06:06:26.38 -67:59:40.3 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
05:53:53.05 +32:08:49.9 17.6mag C/2017 K2 (PANSTARRS)
17:09:35.68 +15:51:07.3 17.9mag C/2021 G2 (ATLAS)
23:21:39.22 -34:26:16.5 15.8mag P/2021 N1 (ZTF)
23:08:47.10 +32:01:08.9 17.2mag C/2022 E2 (ATLAS)
05:49:53.66 +27:00:44.0 16.6mag C/2022 N2 (PANSTARRS)
09:39:35.06 +30:35:37.5 16.7mag C/2022 QE78 (ATLAS)
08:57:53.55 +04:28:31.8 17.7mag C/2022 R6 (PANSTARRS)
18:19:35.26 +21:41:59.3 17.8mag C/2023 A3 (Tsuchinshan-ATLAS)
15:15:14.03 -11:04:49.0 17.6mag P/2023 B1 (PANSTARRS)
22:07:41.12 +67:13:05.1 17.8mag C/2023 H5 (Lemmon)
17:14:00.94 -08:01:52.5 13.7mag C/2023 R1 (PANSTARRS)
13:17:55.57 +79:55:38.7 18.0mag C/2023 X2 (Lemmon)
07:29:27.41 +64:47:57.5 17.8mag C/2024 A1 (ATLAS)
07:06:31.15 +28:51:57.2 14.1mag C/2024 E1 (Wierzchos)
15:27:39.20 +14:29:42.2 17.4mag C/2024 G6 (ATLAS)
20:02:37.49 +34:51:26.7 13.9mag C/2024 J3 (ATLAS)
04:31:02.53 -14:54:57.6 15.9mag C/2024 T5 (ATLAS)
06:17:54.51 +32:15:49.9 17.9mag C/2025 J1 (Borisov)
11:32:04.67 +51:57:03.5 17.9mag C/2025 L1 (ATLAS)
06:58:48.37 -11:31:19.3 15.2mag C/2025 R3 (PANSTARRS)
09:35:47.29 +23:05:15.9 17.8mag C/2025 V2 (Rankin)
12:40:18.91 +04:32:16.3 17.1mag C/2025 Y1 (ATLAS)
17:46:12.83 +77:30:39.4 17.7mag C/2026 A2 (Bok)
02:21:42.24 +44:15:42.7 16.3mag C/2026 B2 (Sun-Gao)
11:15:23.17 +00:18:12.8 16.7mag A/2026 E1
20:46:55.88 -10:06:13.5 8.1mag 10P/Tempel
11:05:44.19 -01:13:51.1 16.0mag 29P/Schwassmann-Wachmann
03:31:44.04 +27:19:31.0 17.7mag 47P/Ashbrook-Jackson
09:27:44.40 +19:56:43.1 16.9mag 63P/Wild
00:37:11.98 -05:39:06.4 15.6mag 65P/Gunn
07:25:47.46 +34:19:44.0 17.3mag 76P/West-Kohoutek-Ikemura
03:40:49.71 +18:42:13.6 13.8mag 78P/Gehrels
01:47:46.96 +07:29:10.7 15.8mag 88P/Howell
05:36:23.47 +30:54:59.6 15.4mag 93P/Lovas
03:21:01.73 +29:28:56.7 17.3mag 114P/Wiseman-Skiff
07:21:57.31 +32:22:41.6 15.4mag 123P/West-Hartley
10:13:11.44 +09:06:25.8 16.6mag 124P/Mrkos
04:20:31.76 +20:01:42.5 16.3mag 128P/Shoemaker-Holt
04:59:20.12 +19:32:39.8 17.8mag 131P/Mueller
06:50:40.87 +16:47:50.5 16.3mag 141P/Machholz
06:54:21.52 +17:51:22.1 16.2mag 141P-A/Machholz
05:56:57.83 +17:19:38.9 13.1mag 141P-D/Machholz
03:06:26.49 -23:01:59.9 16.3mag 161P/Hartley-IRAS
04:25:26.00 +28:37:16.3 15.1mag 162P/SidingSpring
19:31:58.24 +06:02:42.8 16.1mag 169P/NEAT
00:52:55.96 +04:51:22.6 17.8mag 220P/McNaught
16:43:12.39 -08:05:28.2 16.6mag 235P/LINEAR
08:03:50.75 +34:47:58.7 17.7mag 240P/NEAT
01:06:55.06 +03:14:48.6 16.1mag 260P/McNaught
04:40:38.24 +34:37:48.0 17.5mag 295P/LINEAR
00:58:59.61 +04:02:43.0 18.0mag 320P/McNaught
15:10:13.62 +07:29:09.8 17.5mag 391P/Kowalski
08:17:51.91 +20:22:13.6 17.9mag 450P/LONEOS
07:21:10.54 +40:44:16.7 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.7K Jun 21 00:34 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
20:49:13.39 +25:17:59.20 ASASSN-26du 2026-06-15.39 15.93
23:09:30.84 +32:40:42.00 SN2026oxc 2026-06-14.35 16.83
02:02:26.78 +32:04:21.30 AT2026ovz 2026-06-14.59 15.39
21:26:28.11 -72:31:19.50 AT2026nwc 2026-06-11 17.05
17:54:57.33 +26:32:34.20 SN 2026odc 2026-06-11.23 17.62
13:55:59.94 +17:30:37.20 SN 2026nyq 2026-06-11.1 16.24
00:50:45.14 -71:38:36.90 ASASSN-26dt 2026-06-11.13 10.22
14:42:19.73 +19:11:35.60 SN2026nyp 2026-06-10.3 16.32
12:23:23.92 +12:56:43.50 SN2026mta 2026-06-8.29 16.69
12:30:18.51 +47:12:33.20 SN2026oao 2026-06-9.32 17.02
10:51:05.21 -42:28:56.60 AT2026nvf 2026-06-8.12 16.75
13:50:22.48 -07:35:00.00 SN2026npn 2026-06-8.02 17.58
00:56:07.17 +43:01:43.20 ASASSN-26dq 2026-06-7.43 13.58
01:07:49.46 +41:59:43.70 SN 2026obc 2026-06-7.43 15.15
21:11:25.22 +14:14:31.90 ASASSN-26dr 2026-06-7.24 16.24
06:21:27.06 -65:16:42.00 ASASSN-26ds 2026-06-2.97 15.02
20:07:38.15 -21:07:05.40 SN2026mho 2026-05-25.18 -1.12
11:29:42.55 +79:01:03.10 AT2026min 2026-05-24.21 16.63
11:44:32.95 -68:48:30.00 ASASSN-26no 2026-05-24 8.41
19:00:42.82 -48:31:01.60 ASASSN-26dp 2026-05-22.31 -3.28
14:23:56.72 -58:37:47.60 ASASSN-26dn 2026-05-20.01 14.64
11:24:54.06 +47:57:01.60 AT2026nma 2026-05-20.29 15.46
21:27:08.58 +33:24:38.10 AT2026lli 2026-05-19.34 15.86
00:31:01.41 -13:38:51.70 AT2026nad 2026-05-19.39 15.34
15:16:06.61 -79:16:32.40 ASASSN-26dm 2026-05-19.03 14.44
11:24:25.21 -59:23:19.10 ASASSN-26dl 2026-05-18.02 13.55
13:45:51.52 -53:16:01.00 ASASSN-26dk 2026-05-18.16 12.96
02:05:49.69 -30:29:09.60 ASASSN-26dh 2026-05-18.43 15.37
17:50:22.87 -39:42:33.90 ASASSN-26dj 2026-05-17.05 15.7
01:13:11.60 -33:25:16.10 ASASSN-26dg 2026-05-13.41 16.8
16:44:31.77 -27:15:18.40 AT2026mhn 2026-05-12.33 15.8
09:46:31.08 -33:41:51.00 ASASSN-26di 2026-05-12.14 14.63
21:23:11.57 -19:09:45.00 AT2026kwu 2026-05-12.26 16.9
14:20:14.30 -30:20:51.90 AT2026ktm 2026-05-12.06 17.21
14:41:39.01 -37:13:46.40 AT2026lkm 2026-05-11.18 16.89
12:59:50.45 -10:58:38.80 SN2026kep 2026-05-9.06 17.5
13:37:29.61 -29:50:30.90 AT2026lkd 2026-05-9.09 17.23
09:46:42.01 -14:52:03.60 SN2026kmo 2026-05-8.99 17.51
15:03:05.18 +22:02:03.40 AT2026lxf 2026-05-8.07 13.94
10:23:49.41 -20:57:25.30 ASASSN-26df 2026-05-8.21 16.52
22:14:40.56 +05:04:51.60 2026lda 2026-05-7.56 16.2
21:35:33.81 -14:05:16.30 ASASSN-26de 2026-05-6.29 14.51
16:21:49.13 -61:36:14.60 ASASSN-26dd 2026-05-5.15 15.93
14:26:40.22 -24:48:37.50 AT2026lig 2026-05-4.27 14.63
13:17:51.04 +30:25:13.50 SN2026kcp 2026-05-4.46 16.43
11:27:55.57 -13:38:56.90 SN2026kza 2026-05-1.08 15.59
22:28:27.10 +30:17:54.30 SN 2026fov 2026-04-29.6 14.36
21:00:10.71 -32:17:03.90 AT2026kis 2026-04-27.36 16.15
14:32:57.37 -58:13:26.40 ASASSN-26dc 2026-04-27.27 13.42
15:32:05.35 -43:54:34.60 ASASSN-26db 2026-04-27.37 16.06
16:34:34.97 -54:34:58.00 ASASSN-26da 2026-04-25.32 16.11
10:06:55.04 -01:13:49.70 SN2026jsg 2026-04-24.99 16.28
15:15:57.17 +56:18:32.80 SN2026kid 2026-04-24.52 -3.65
07:58:28.45 +57:03:42.40 AT2026kcf 2026-04-24.2 16.89
11:38:21.80 -50:43:06.50 SN2026jkb 2026-04-24.24 15.38
10:06:11.41 -39:41:04.20 AT2026dil 2026-04-24.2 16.85
14:21:40.08 +13:13:46.30 SN2026jlm 2026-04-22.16 15.12
10:53:55.52 -16:06:06.00 ASASSN-26cz 2026-04-22.28 16.29
20:49:13.39 +25:17:59.20 2026-06-15.39 15.93
13:45:02.03 +15:17:14.50 ASASSN-26cy 2026-04-21.27 15.78
13:20:52.22 -35:57:03.60 AT2026jcm 2026-04-19.01 16.65
13:36:15.66 -36:53:48.40 SN 2026iqy 2026-04-18.92 17.31
06:34:01.33 -40:07:34.00 ASASSN-26cx 2026-04-19.07 16.16
23:33:57.97 -45:12:11.90 SN 2026idu 2026-04-19.41 15.9
12:10:50.92 +66:55:31.20 SN 2026icv 2026-04-17.14 16.03
21:36:59.06 -60:43:35.90 ASASSN-26cv 2026-04-17.35 -1.18
08:13:26.26 -27:07:30.50 ASASSN-26cw 2026-04-17.07 -1.01
14:49:14.01 -27:29:20.10 ASASSN-26cu 2026-04-16.29 -2.7
17:21:59.44 -38:54:04.60 ASASSN-26ct 2026-04-14.4 15.15
15:25:54.99 +07:49:24.50 SN2026huo 2026-04-12.14 16.96
20:49:13.39 +25:17:59.20 2026-06-15.39 15.93
12:23:20.40 +04:53:39.10 AT2026ixd 2026-04-12.14 17.65
17:46:09.76 -61:19:50.40 SN2026icy 2026-04-12.2 17.03
09:25:46.42 +02:13:46.30 SN2026gud 2026-04-11.98 16.49
16:52:15.46 -60:27:45.90 ASASSN-26cs 2026-04-12.4 15.5
04:20:55.37 -51:15:31.10 ASASSN-26cr 2026-04-12.01 15.37
22:25:39.35 +36:45:06.90 AT2026ihl 2026-04-10.48 14.21
19:40:44.94 +00:41:03.80 AT2026imw 2026-04-10.32 16.06
19:52:04.70 +05:53:33.50 ASASSN-26cq 2026-04-9.31 14.98
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.14 13.64
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:35.90 ASASSN-26co 2026-04-7.15 14.93
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.68 -22:39:32.70 ASASSN-26cm 2026-04-4.27 13.88
18:08:57.38 +76:48:23.60 ASASSN-26ck 2026-04-2.37 15.38
16:16:36.10 +44:52:30.20 AT2026hyy 2026-04-2.58 13.81
21:55:23.31 -34:48:53.90 ASASSN-26cj 2026-03-30.4 -1.47
11:19:50.81 -27:51:50.40 SN2026gvk 2026-03-30 15.28
11:53:57.02 -23:09:46.20 SN2026gzx 2026-03-28.75 15.27
07:13:46.14 -33:10:15.70 ASASSN-26ci 2026-03-28.15 15.14
09:03:36.09 -67:58:13.00 SN2026hkg 2026-03-28.19 15.82
07:03:00.72 +39:14:43.00 SN2026fin 2026-03-28.27 15.82
05:35:42.79 -63:44:05.60 ASASSN-26ch 2026-03-28.12 13.14
-rw-r--r-- 1 apache apache 5.6K Jun 21 00:34 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
00:43:01.82 +41:18:16.6 PNV J00430182+4118166 2026-05-21.8651 18.83Cmag
00:42:51.20 +41:16:59.4 PNV J00425120+4116594 2022-10-26.135 19.3mag
12:24:25.10 +28:47:12.0 TCP J12242510+2847120 2026-05-31.6015 14.8mag
00:56:07.13 +43:01:40.6 TCP J00560713+4301406 2026-06-01.4135 12.2mag
00:42:41.64 +41:15:16.2 PNV J00424164+4115162 2026-06-02.029 17.4mag
00:42:38.68 +41:15:58.2 PNV J00423868+4115582 2026-06-05.1224 19.97Umag
19:00:42.95 -48:31:01.7 PNV J19004295-4831017 2026-05-25.0752 14.2mag
09:55:21.28 +69:02:52.6 PNV J09552128+6902526 2026-06-13.933 18.9mag
19:51:21.42 +37:06:40.0 TCP J19512142+3706400 2026-06-17.2942 16.8mag
19:57:03.87 +37:41:46.4 TCP J19570387+3741464 2026-06-18.2638 17.5mag
-rw-r--r-- 1 apache apache 189K Jun 21 00:34 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
16:11:41.646 +16:56:18.65 AT 2026pap 2026-06-12.83 20.32
20:46:15.499 -32:19:29.95 SN 2026pao 2026-06-11.36 18.635
15:03:43.225 +02:12:54.73 AT 2026pan 2026-06-05.29 20.61
23:06:24.407 +14:31:45.25 AT 2026pam 2026-06-06.80 19.38
11:47:31.848 -25:11:15.00 AT 2026pal 2026-06-07.35 20.37
15:04:37.659 -01:15:27.46 AT 2026pak 2026-06-07.45 20.29
17:48:25.754 +32:00:08.94 AT 2026paj 2026-06-12.05 19.81
21:50:53.005 -01:05:39.13 AT 2026pai 2026-06-08.43 20.366
12:25:02.669 +52:19:31.14 AT 2026pah 2026-06-03.24 19.8587
21:46:05.755 -08:58:40.30 TDE 2026pag 2026-06-03.38 19.3089
10:27:13.174 +19:29:29.02 AT 2026paf 2026-06-01.20 19.6465
22:55:52.731 -02:16:03.48 AT 2026pae 2026-06-05.45 19.7544
15:08:17.400 -12:11:26.44 SN 2026pad 2026-06-12.28 20.06
22:23:33.649 -01:35:22.74 AT 2026pac 2026-06-09.42 20.1163
16:50:53.544 -15:00:19.11 AT 2026pab 2026-06-07.24 21.56
17:27:02.076 +41:10:59.54 AT 2026paa 2026-06-07.32 20.214
18:20:18.686 +77:47:56.78 AT 2026ozz 2026-06-09.31 19.322
22:11:50.531 +22:43:04.06 AT 2026ozy 2026-06-11.18 19.472
11:50:19.187 +31:49:23.30 AT 2026ozx 2026-06-10.91 19.389
18:26:16.254 +32:18:13.23 AT 2026ozw 2026-06-11.07 20.169
-rw-r--r-- 1 apache apache 30K Jun 21 00:34 tns_transients_list.txt
