This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI
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 17.4203 2461208.9203 11.37 00:34:23.05 +64:31:55.3
121.09916 1.72098 galactic Cas Second-epoch detections are separated by 3.1" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:34:23.05 +64:31:55.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:34:23.05 +64:31:55.3: 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:34:23.05 +64:31:55.3: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 34 23.05 +64 31 55.3 11.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,11.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 11.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.12 00:15:28.13 +61:28:18.7
118.65013 -1.10050 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 | ZTF J001522.29+612755.7 | 00:15:23.01 +61:28:10.5 (Gaia DR3) | EW (local) | 2458336.85790 (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:15:28.13 +61:28:18.7: 13.58 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:28.13 +61:28:18.7: 13.22 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.35 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 15 28.13 +61 28 18.7 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J001522.29+612755.7,2461208.9203,12.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 J001522.29+612755.7 20260617.4203 12.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 17.4203 2461208.9203 12.19 00:17:18.73 +61:39:29.8
118.89285 -0.94556 galactic Cas Second-epoch detections are separated by 1.9" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429687602251961728 | 00:17:17.70 +61:39:27.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:17:18.73 +61:39:29.8: 14.06 +/- 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:17:18.73 +61:39:29.8: 13.86 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.93 +/- 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 17.4203* 00 17 18.73 +61 39 29.8 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429687602251961728,2461208.9203,12.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429687602251961728 20260617.4203 12.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.22 23:55:25.66 +64:08:38.7
116.87113 1.93341 galactic Cas Second-epoch detections are separated by 1.3" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:25.66 +64:08:38.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:55:25.66 +64:08:38.7: 15.71 +/- 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:55:25.66 +64:08:38.7: 15.87 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.71 +/- 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 17.4203* 23 55 25.66 +64 08 38.7 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,12.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 20260617.4203 12.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 17.4203 2461208.9203 12.25 00:11:32.58 +61:13:57.0
118.14948 -1.26825 galactic Cas Second-epoch detections are separated by 1.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 429627747589632896 | 00:11:31.39 +61:13:58.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:11:32.58 +61:13:57.0: 13.42 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:11:32.58 +61:13:57.0: 13.47 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.45 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 11 32.58 +61 13 57.0 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429627747589632896,2461208.9203,12.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
Gaia DR3 429627747589632896 20260617.4203 12.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 17.4203 2461208.9203 12.27 00:11:14.87 +64:53:33.2
118.68293 2.35289 galactic Cas Second-epoch detections are separated by 2.4" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:14.87 +64:53:33.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:11:14.87 +64:53:33.2: 14.56 +/- 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:11:14.87 +64:53:33.2: 14.90 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.68 +/- 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 17.4203* 00 11 14.87 +64 53 33.2 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,12.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 12.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.72 00:16:47.48 +64:42:54.8
119.24144 2.09202 galactic Cas Second-epoch detections are separated by 1.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:16:47.48 +64:42:54.8 (user input) | T | P | (position from user input) J-Ks=0.711+/-0.174 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:47.48 +64:42:54.8: 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:47.48 +64:42:54.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 17.4203* 00 16 47.48 +64 42 54.8 14.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,2461208.9203,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.67 00:23:11.84 +63:49:18.6
119.82299 1.12069 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:23:11.84 +63:49:18.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:11.84 +63:49:18.6: 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:11.84 +63:49:18.6: 16.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 23 11.84 +63 49 18.6 14.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,2461208.9203,14.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.70 23:57:03.44 +61:22:15.0
116.46453 -0.81619 galactic Cas Second-epoch detections are separated by 3.1" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:03.44 +61:22: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:57:03.44 +61:22:15.0: 15.62 +/- 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:03.44 +61:22:15.0: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 57 03.44 +61 22 15.0 14.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,2461208.9203,14.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.68 23:25:18.81 +57:37:12.2
111.57747 -3.34063 galactic Cas Second-epoch detections are separated by 4.2" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:18.81 +57:37:12.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:25:18.81 +57:37:12.2: 15.91 +/- 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:25:18.81 +57:37:12.2: 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 17.4203* 23 25 18.81 +57 37 12.2 14.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,2461208.9203,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.71 23:31:56.96 +65:42:21.6
114.87210 4.08580 galactic Cep Second-epoch detections are separated by 5.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:56.96 +65:42:21.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:31:56.96 +65:42:21.6: 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 23:31:56.96 +65:42:21.6: 15.87 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.79 23:25:05.21 +64:43:23.9
113.87737 3.38048 galactic Cep Second-epoch detections are separated by 5.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:05.21 +64:43:23.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:25:05.21 +64:43:23.9: 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:25:05.21 +64:43:23.9: 16.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.60 00:03:10.72 +64:44:02.1
117.80925 2.34324 galactic Cas Second-epoch detections are separated by 7.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:10.72 +64:44:02.1 (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:03:10.72 +64:44:02.1: 16.16 +/- 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:03:10.72 +64:44:02.1: 16.16 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 03 10.72 +64 44 02.1 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.55 00:04:36.75 +60:35:02.5
117.21008 -1.76647 galactic Cas Second-epoch detections are separated by 5.7" and 5.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:36.75 +60:35:02.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:04:36.75 +60:35:02.5: 16.09 +/- 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:04:36.75 +60:35:02.5: 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 17.4203* 00 04 36.75 +60 35 02.5 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.56 23:55:57.21 +64:02:12.2
116.90423 1.81623 galactic Cas Second-epoch detections are separated by 4.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 | 23:55:57.21 +64:02:12.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:55:57.21 +64:02:12.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 23:55:57.21 +64:02:12.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!
TCP 2026 06 17.4203* 23 55 57.21 +64 02 12.2 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.49 00:02:52.95 +62:04:53.3
117.28153 -0.25642 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 | target | 00:02:52.95 +62:04:53.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:02:52.95 +62:04:53.3: 15.85 +/- 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:02:52.95 +62:04:53.3: 15.37 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.51 +/- 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 17.4203* 00 02 52.95 +62 04 53.3 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.43 00:23:25.11 +61:50:19.2
119.63197 -0.85342 galactic Cas Second-epoch detections are separated by 7.3" and 5.6 pix
The object was found in VSX14" Gaia DR3 430455061371462400
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.440 G 14.460 G 0.053247600000 A
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:25.11 +61:50:19.2: 16.04 +/- 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:25.11 +61:50:19.2: 16.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 23 25.11 +61 50 19.2 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430455061371462400,2461208.9203,14.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430455061371462400 20260617.4203 14.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.40 00:23:13.57 +62:26:43.2
119.67572 -0.24792 galactic Cas Second-epoch detections are separated by 4.5" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Large-amplitude variable Gaia DR2 430588067912107264 | 00:23:13.57 +62:26:43.2 (user input) | 2021A&A...648A..44M | | (position from user input) (the VSX policy as of May 2022 seems to be NOT to regard variables from 2021A&A...648A..44M as 'known' for the lack of classification)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:23:13.57 +62:26:43.2: 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:13.57 +62:26:43.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 17.4203* 00 23 13.57 +62 26 43.2 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Large-amplitude variable Gaia DR2 430588067912107264,2461208.9203,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Large-amplitude variable Gaia DR2 430588067912107264 20260617.4203 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.31 00:20:43.12 +62:52:57.2
119.43962 0.21929 galactic Cas Second-epoch detections are separated by 3.5" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:20:43.12 +62:52:57.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:20:43.12 +62:52:57.2: 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:20:43.12 +62:52:57.2: 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 17.4203* 00 20 43.12 +62 52 57.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.27 00:34:22.09 +60:00:43.8
120.79793 -2.78884 galactic Cas Second-epoch detections are separated by 3.1" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 428559017983381632 | 00:34:18.37 +60:00:56.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:34:22.09 +60:00:43.8: 15.91 +/- 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:22.09 +60:00:43.8: 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 17.4203* 00 34 22.09 +60 00 43.8 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428559017983381632,2461208.9203,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 428559017983381632 20260617.4203 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.03 00:06:56.79 +62:32:10.1
117.82758 0.10614 galactic Cas Second-epoch detections are separated by 6.0" 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:06:56.79 +62:32:10.1 (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:06:56.79 +62:32:10.1: 16.16 +/- 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:06:56.79 +62:32:10.1: 16.16 +/- 0.35 detection
Forced photometry reference-image weighted average: 16.16 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 06 56.79 +62 32 10.1 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.13 00:13:25.13 +63:15:27.0
118.67029 0.70077 galactic Cas Second-epoch detections are separated by 2.7" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:25.13 +63:15:27.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:13:25.13 +63:15:27.0: 15.81 +/- 0.32 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:13:25.13 +63:15:27.0: 15.61 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.69 +/- 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 17.4203* 00 13 25.13 +63 15 27.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.98 23:41:35.07 +59:35:28.8
114.18914 -2.08945 galactic Cas Second-epoch detections are separated by 8.6" and 6.1 pix
The object was found in VSX 8" V0996 Cas
Type: SR
# Max. Min./Amp. JD0 Period
11.800 w 13.300 w 2451384.00000 260.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:41:35.07 +59:35:28.8: 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:41:35.07 +59:35:28.8: 16.09 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 41 35.07 +59 35 28.8 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0996 Cas,2461208.9203,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
V0996 Cas 20260617.4203 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 17.4203 2461208.9203 14.02 00:20:21.88 +60:15:51.5
119.08444 -2.37511 galactic Cas Second-epoch detections are separated by 1.3" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:20:21.88 +60:15:51.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:20:21.88 +60:15:51.5: 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:20:21.88 +60:15:51.5: 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 17.4203* 00 20 21.88 +60 15 51.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,2461208.9203,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.70 00:03:35.60 +63:34:46.8
117.63966 1.20061 galactic Cas Second-epoch detections are separated by 7.7" and 5.8 pix
The object was found in VSX10" Gaia DR3 431611197851413248
Type: ROT
# Max. Min./Amp. JD0 Period
15.190 G 15.220 G F
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:03:35.60 +63:34:46.8: 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:03:35.60 +63:34:46.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 17.4203* 00 03 35.60 +63 34 46.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
Gaia DR3 431611197851413248,2461208.9203,13.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 431611197851413248 20260617.4203 13.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.29 23:22:21.62 +62:39:45.7
112.90606 1.53777 galactic Cas Second-epoch detections are separated by 7.3" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:21.62 +62:39:45.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:22:21.62 +62:39:45.7: 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 23:22:21.62 +62:39:45.7: 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 17.4203* 23 22 21.62 +62 39 45.7 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 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 17.4203 2461208.9203 11.62 00:16:14.03 +60:59:38.4
118.67551 -1.58648 galactic Cas Second-epoch detections are separated by 1.2" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | 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.03 +60:59:38.4: 14.21 +/- 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:16:14.03 +60:59:38.4: 14.14 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.18 +/- 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 17.4203* 00 16 14.03 +60 59 38.4 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,2461208.9203,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429571844296750592 20260617.4203 11.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 17.4203 2461208.9203 12.35 00:21:26.52 +59:13:56.8
119.09704 -3.41578 galactic Cas Second-epoch detections are separated by 1.3" and 5.7 pix
The object was found in VSX 8" 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:26.52 +59:13:56.8: 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:26.52 +59:13:56.8: 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 17.4203* 00 21 26.52 +59 13 56.8 12.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
FQ Cas,2461208.9203,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
FQ Cas 20260617.4203 12.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.76 00:16:40.71 +65:59:41.4
119.40195 3.36160 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:16:40.71 +65:59:41.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:16:40.71 +65:59:41.4: 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:40.71 +65:59:41.4: 16.15 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 16 40.71 +65 59 41.4 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,2461208.9203,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.96 00:35:16.36 +63:00:43.9
121.09916 0.19798 galactic Cas Second-epoch detections are separated by 1.3" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | 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.36 +63:00:43.9: 15.68 +/- 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.36 +63:00:43.9: 15.66 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 35 16.36 +63 00 43.9 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430819721271142272,2461208.9203,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430819721271142272 20260617.4203 12.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.97 00:21:57.21 +61:46:06.0
119.45215 -0.90405 galactic Cas Second-epoch detections are separated by 6.4" and 5.6 pix
The object was found in VSX12" 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:57.21 +61:46:06.0: 15.00 +/- 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:21:57.21 +61:46:06.0: 14.67 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.80 +/- 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 17.4203* 00 21 57.21 +61 46 06.0 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430450968254479872,2461208.9203,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430450968254479872 20260617.4203 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 12.96 00:15:12.25 +58:24:53.0
118.18947 -4.12299 galactic Cas Second-epoch detections are separated by 2.6" and 5.7 pix
The object was not found in VSX
The object was found in ASASSN-V 9" 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.25 +58:24:53.0: 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 00:15:12.25 +58:24:53.0: 14.19 +/- 0.07 detection
Forced photometry reference-image weighted average: 14.25 +/- 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 17.4203* 00 15 12.25 +58 24 53.0 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
VARIABLE_NAME,2461208.9203,12.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
VARIABLE_NAME 20260617.4203 12.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.20 00:30:23.76 +60:12:41.2
120.31868 -2.55349 galactic Cas Second-epoch detections are separated by 5.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 | 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:23.76 +60:12:41.2: 14.52 +/- 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:30:23.76 +60:12:41.2: 14.53 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.52 +/- 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 17.4203* 00 30 23.76 +60 12 41.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 428618086677459456,2461208.9203,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 428618086677459456 20260617.4203 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 17.4203 2461208.9203 13.22 23:52:13.37 +65:38:33.0
116.87174 3.46988 galactic Cas Second-epoch detections are separated by 5.9" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:13.37 +65:38:33.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:52:13.37 +65:38:33.0: 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 23:52:13.37 +65:38:33.0: 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!
TCP 2026 06 17.4203* 23 52 13.37 +65 38 33.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,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.27 00:10:26.28 +60:01:06.0
117.82564 -2.44630 galactic Cas Second-epoch detections are separated by 2.6" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.6312+60.0252 | 00:10:26.28 +60:01:06.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:10:26.28 +60:01:06.0: 14.88 +/- 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:10:26.28 +60:01:06.0: 14.70 +/- 0.11 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 17.4203* 00 10 26.28 +60 01 06.0 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.6312+60.0252,2461208.9203,13.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.6312+60.0252 20260617.4203 13.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.29 00:10:45.95 +63:25:28.6
118.40155 0.91118 galactic Cas Second-epoch detections are separated by 2.2" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 431453241826796032 | 00:10:38.95 +63:25:24.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:10:45.95 +63:25:28.6: 15.31 +/- 0.24 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:10:45.95 +63:25:28.6: 14.93 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.05 +/- 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 17.4203* 00 10 45.95 +63 25 28.6 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 431453241826796032,2461208.9203,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 431453241826796032 20260617.4203 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 17.4203 2461208.9203 13.37 00:00:30.32 +65:48:24.4
117.74003 3.44976 galactic Cas Second-epoch detections are separated by 6.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 | Gaia DR3 432301068366547584 | 00:00:36.30 +65:48:49.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:00:30.32 +65:48:24.4: 14.29 +/- 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:00:30.32 +65:48:24.4: 14.32 +/- 0.08 detection
Forced photometry reference-image weighted average: 14.31 +/- 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 17.4203* 00 00 30.32 +65 48 24.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
Gaia DR3 432301068366547584,2461208.9203,13.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 432301068366547584 20260617.4203 13.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.49 00:21:47.83 +61:02:51.6
119.35101 -1.61783 galactic Cas Second-epoch detections are separated by 0.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:21:47.83 +61:02:51.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:21:47.83 +61:02:51.6: 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:47.83 +61:02:51.6: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 21 47.83 +61 02 51.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
target,2461208.9203,13.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.53 00:35:29.49 +61:53:07.8
121.05422 -0.92810 galactic Cas Second-epoch detections are separated by 4.0" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:35:29.49 +61:53:07.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:35:29.49 +61:53:07.8: 15.83 +/- 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:29.49 +61:53:07.8: 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 17.4203* 00 35 29.49 +61 53 07.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,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.54 00:40:45.95 +64:16:35.6
121.77390 1.42881 galactic Cas Second-epoch detections are separated by 7.7" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:40:45.95 +64:16:35.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:40:45.95 +64:16:35.6: 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:40:45.95 +64:16:35.6: 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 17.4203* 00 40 45.95 +64 16 35.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
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.56 00:15:43.58 +59:34:01.8
118.41715 -2.99117 galactic Cas Second-epoch detections are separated by 1.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:15:43.58 +59:34:01.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:15:43.58 +59:34:01.8: 14.57 +/- 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:15:43.58 +59:34:01.8: 14.72 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.63 +/- 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 17.4203* 00 15 43.58 +59 34 01.8 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.52 00:15:02.92 +61:26:04.5
118.59520 -1.13038 galactic Cas Second-epoch detections are separated by 4.6" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | 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:02.92 +61:26:04.5: 15.75 +/- 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:02.92 +61:26:04.5: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 15 02.92 +61 26 04.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 429599538245809280,2461208.9203,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 429599538245809280 20260617.4203 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 17.4203 2461208.9203 13.64 00:07:46.77 +61:54:28.1
117.81634 -0.52954 galactic Cas Second-epoch detections are separated by 1.3" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429861080268999296 | 00:07:50.85 +61:54:42.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:07:46.77 +61:54:28.1: 14.74 +/- 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:07:46.77 +61:54:28.1: 14.61 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.67 +/- 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 17.4203* 00 07 46.77 +61 54 28.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
Gaia DR3 429861080268999296,2461208.9203,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429861080268999296 20260617.4203 13.64CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.65 00:12:36.08 +62:53:08.1
118.52351 0.34673 galactic Cas Second-epoch detections are separated by 3.2" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:12:36.08 +62:53:08.1 (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:12:36.08 +62:53:08.1: 15.68 +/- 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:12:36.08 +62:53:08.1: 15.03 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.19 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 12 36.08 +62 53 08.1 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.62 00:23:45.40 +59:32:00.7
119.42412 -3.14956 galactic Cas Second-epoch detections are separated by 2.9" and 5.7 pix
The object was found in VSX10" 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:45.40 +59:32:00.7: 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:23:45.40 +59:32:00.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 17.4203* 00 23 45.40 +59 32 00.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,2461208.9203,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Mis V1302 20260617.4203 13.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.71 00:23:31.68 +65:19:46.1
120.02243 2.61551 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:31.68 +65:19:46.1 (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:31.68 +65:19:46.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:23:31.68 +65:19:46.1: 16.00 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 23 31.68 +65 19 46.1 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 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 17.4203 2461208.9203 13.62 00:00:34.43 +62:49:36.3
117.16230 0.52618 galactic Cas Second-epoch detections are separated by 6.2" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 430049375942358912 | 00:00:29.64 +62:49:24.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE J-Ks=0.940+/-0.088 (M)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:00:34.43 +62:49:36.3: 14.96 +/- 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:00:34.43 +62:49:36.3: 14.84 +/- 0.13 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 17.4203* 00 00 34.43 +62 49 36.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 430049375942358912,2461208.9203,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430049375942358912 20260617.4203 13.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.73 23:23:48.81 +65:45:07.0
114.09201 4.39538 galactic Cep Second-epoch detections are separated by 7.3" 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:23:48.81 +65:45:07.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:48.81 +65:45:07.0: 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 23:23:48.81 +65:45:07.0: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.72 00:01:10.87 +64:55:36.9
117.63725 2.57307 galactic Cas Second-epoch detections are separated by 5.9" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:10.87 +64:55:36.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:10.87 +64:55:36.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 00:01:10.87 +64:55:36.9: 15.91 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 01 10.87 +64 55 36.9 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.86 00:03:30.11 +58:28:54.0
116.68648 -3.80761 galactic Cas Second-epoch detections are separated by 2.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 | ATO J000.8557+58.4755 | 00:03:30.11 +58:28:54.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:03:30.11 +58:28:54.0: 15.08 +/- 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:03:30.11 +58:28:54.0: 14.93 +/- 0.14 detection
Forced photometry reference-image weighted average: 15.00 +/- 0.11
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 03 30.11 +58 28 54.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 J000.8557+58.4755,2461208.9203,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.8557+58.4755 20260617.4203 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.76 00:01:55.45 +63:10:47.0
117.38091 0.84286 galactic Cas Second-epoch detections are separated by 3.7" and 6.0 pix
The object was found in VSX15" Gaia DR3 430085900345681152
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.900 G 13.930 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:01:55.45 +63:10:47.0: 15.54 +/- 0.32 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:55.45 +63:10:47.0: 15.47 +/- 0.32 detection
Forced photometry reference-image weighted average: 15.50 +/- 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 17.4203* 00 01 55.45 +63 10 47.0 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430085900345681152,2461208.9203,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 430085900345681152 20260617.4203 13.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.82 00:02:05.62 +63:18:19.2
117.42358 0.96253 galactic Cas Second-epoch detections are separated by 3.1" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:02:05.62 +63:18: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:02:05.62 +63:18:19.2: 15.71 +/- 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:02:05.62 +63:18:19.2: 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 17.4203* 00 02 05.62 +63 18 19.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,2461208.9203,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.98 23:59:26.60 +63:49:12.2
117.23469 1.52493 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 | target | 23:59:26.60 +63:49:12.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:59:26.60 +63:49:12.2: 15.90 +/- 0.36 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:59:26.60 +63:49:12.2: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.90 +/- 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 17.4203* 23 59 26.60 +63 49 12.2 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.94 00:13:51.00 +59:58:37.1
118.24132 -2.55201 galactic Cas Second-epoch detections are separated by 4.6" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:51.00 +59:58:37.1 (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:51.00 +59:58:37.1: 15.02 +/- 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:13:51.00 +59:58:37.1: 15.30 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.12 +/- 0.15
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 13 51.00 +59 58 37.1 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.97 23:24:19.46 +64:02:47.3
113.57624 2.76854 galactic Cep Second-epoch detections are separated by 3.4" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:19.46 +64:02:47.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 23:24:19.46 +64:02:47.3: 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:24:19.46 +64:02:47.3: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 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 17.4203 2461208.9203 13.99 00:09:16.33 +59:38:42.3
117.62086 -2.79115 galactic Cas Second-epoch detections are separated by 4.0" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.3361+59.6510 | 00:09:20.90 +59:38:31.9 (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:09:16.33 +59:38:42.3: 15.23 +/- 0.20 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:16.33 +59:38:42.3: 15.18 +/- 0.19 detection
Forced photometry reference-image weighted average: 15.21 +/- 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 17.4203* 00 09 16.33 +59 38 42.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
ATO J002.3361+59.6510,2461208.9203,13.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.3361+59.6510 20260617.4203 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 17.4203 2461208.9203 14.04 00:07:57.70 +63:21:39.1
118.08135 0.89930 galactic Cas Second-epoch detections are separated by 3.5" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:57.70 +63:21:39.1 (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:57.70 +63:21:39.1: 15.42 +/- 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:57.70 +63:21:39.1: 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 17.4203* 00 07 57.70 +63 21 39.1 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 13.96 00:30:05.13 +60:13:25.0
120.28122 -2.53820 galactic Cas Second-epoch detections are separated by 4.2" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:30:05.13 +60:13:25.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:30:05.13 +60:13:25.0: 15.37 +/- 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.13 +60:13:25.0: 15.42 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 30 05.13 +60 13 25.0 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 14.04 00:09:21.55 +61:47:56.5
117.98207 -0.66765 galactic Cas Second-epoch detections are separated by 4.0" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:21.55 +61:47:56.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:21.55 +61:47:56.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:09:21.55 +61:47:56.5: 15.37 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.37 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 09 21.55 +61 47 56.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,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 14.07 23:57:00.59 +63:29:18.0
116.90238 1.25555 galactic Cas Second-epoch detections are separated by 3.8" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:00.59 +63:29:18.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:57:00.59 +63:29:18.0: 15.47 +/- 0.27 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:00.59 +63:29:18.0: 15.18 +/- 0.20 detection
Forced photometry reference-image weighted average: 15.28 +/- 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 17.4203* 23 57 00.59 +63 29 18.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.13 00:07:53.22 +57:56:32.6
117.16069 -4.44053 galactic Cas Second-epoch detections are separated by 2.9" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:53.22 +57:56:32.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:07:53.22 +57:56:32.6: 15.66 +/- 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:07:53.22 +57:56:32.6: 15.76 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.70 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 07 53.22 +57 56 32.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,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 14.11 00:17:57.20 +59:09:21.0
118.64354 -3.43683 galactic Cas Second-epoch detections are separated by 4.2" and 5.7 pix
The object was found in VSX 9" V0659 Cas
Type: M
# Max. Min./Amp. JD0 Period
13.500 V < 17.000 V 2442638.00000 344.000000000000 M5/7e
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:57.20 +59:09:21.0: 15.91 +/- 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:57.20 +59:09:21.0: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 17 57.20 +59 09 21.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0659 Cas,2461208.9203,14.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0659 Cas 20260617.4203 14.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.11 00:05:34.26 +62:32:06.0
117.67122 0.13267 galactic Cas Second-epoch detections are separated by 6.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:34.26 +62:32:06.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:05:34.26 +62:32:06.0: 15.47 +/- 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:34.26 +62:32:06.0: 15.36 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 05 34.26 +62 32 06.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.21 00:03:11.57 +62:20:26.2
117.36541 -0.00857 galactic Cas Second-epoch detections are separated by 2.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 | Gaia DR3 429932003074514816 | 00:03:14.67 +62:19:56.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:03:11.57 +62:20:26.2: 15.42 +/- 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:03:11.57 +62:20:26.2: 15.05 +/- 0.20 detection
Forced photometry reference-image weighted average: 15.17 +/- 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 17.4203* 00 03 11.57 +62 20 26.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
Gaia DR3 429932003074514816,2461208.9203,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429932003074514816 20260617.4203 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.10 00:31:00.50 +61:24:59.0
120.49014 -1.35846 galactic Cas Second-epoch detections are separated by 3.5" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:31:00.50 +61:24:59.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:31:00.50 +61:24:59.0: 15.61 +/- 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:31:00.50 +61:24:59.0: 15.83 +/- 0.36 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 17.4203* 00 31 00.50 +61 24 59.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.15 00:09:06.05 +58:45:35.0
117.45428 -3.66103 galactic Cas Second-epoch detections are separated by 2.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:09:06.05 +58:45:35.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:06.05 +58:45:35.0: 15.86 +/- 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:09:06.05 +58:45:35.0: 15.80 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.83 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 09 06.05 +58 45 35.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 14.24 00:23:13.48 +60:17:38.6
119.44029 -2.38628 galactic Cas Second-epoch detections are separated by 3.9" and 5.6 pix
The object was found in VSX13" Gaia DR3 428719688420980608
Type: RS
# Max. Min./Amp. JD0 Period
14.080 G 14.190 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:23:13.48 +60:17:38.6: 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:23:13.48 +60:17:38.6: 15.34 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.34 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 23 13.48 +60 17 38.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 428719688420980608,2461208.9203,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 428719688420980608 20260617.4203 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 17.4203 2461208.9203 14.29 00:19:25.32 +59:23:44.7
118.86043 -3.22267 galactic Cas Second-epoch detections are separated by 2.3" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:19:25.32 +59:23:44.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:19:25.32 +59:23:44.7: 15.94 +/- 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:19:25.32 +59:23:44.7: 16.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 19 25.32 +59 23 44.7 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.23 00:22:22.70 +59:28:18.3
119.24323 -3.19171 galactic Cas Second-epoch detections are separated by 4.7" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:22.70 +59:28:18.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:22:22.70 +59:28:18.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:22:22.70 +59:28:18.3: 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 17.4203* 00 22 22.70 +59 28 18.3 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.26 23:47:42.13 +60:42:41.8
115.21200 -1.20127 galactic Cas Second-epoch detections are separated by 3.5" and 6.1 pix
The object was found in VSX12" NSVS J2347397+604236
Type: SRA
# Max. Min./Amp. JD0 Period
17.022 g Y 2.200 g 2458250.24390 217.294225100000
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:47:42.13 +60:42:41.8: 15.43 +/- 0.18 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:47:42.13 +60:42:41.8: 15.13 +/- 0.14 detection
Forced photometry reference-image weighted average: 15.24 +/- 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 17.4203* 23 47 42.13 +60 42 41.8 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J2347397+604236,2461208.9203,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J2347397+604236 20260617.4203 14.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.22 00:07:11.59 +57:51:19.1
117.05473 -4.51068 galactic Cas Second-epoch detections are separated by 3.3" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:11.59 +57:51:19.1 (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:11.59 +57:51:19.1: 15.66 +/- 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:07:11.59 +57:51:19.1: 15.33 +/- 0.20 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 17.4203* 00 07 11.59 +57 51 19.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.24 00:28:07.61 +63:12:32.1
120.30864 0.45596 galactic Cas Second-epoch detections are separated by 2.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 | Gaia DR3 430978154028648576 | 00:28:01.88 +63:12:56.2 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: A2 1966UppAn...5d...1O [O66] 8:1097
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:28:07.61 +63:12:32.1: 16.03 +/- 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:07.61 +63:12:32.1: 16.04 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 28 07.61 +63 12 32.1 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 430978154028648576,2461208.9203,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 430978154028648576 20260617.4203 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 17.4203 2461208.9203 14.29 00:16:23.24 +61:54:20.2
118.81760 -0.68582 galactic Cas Second-epoch detections are separated by 6.4" and 5.2 pix
The object was found in VSX 7" Gaia DR3 429726772354547200
Type: ROT
# Max. Min./Amp. JD0 Period
16.500 G 16.610 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:16:23.24 +61:54:20.2: 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:16:23.24 +61:54:20.2: 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 17.4203* 00 16 23.24 +61 54 20.2 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429726772354547200,2461208.9203,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429726772354547200 20260617.4203 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.29 00:12:20.24 +60:34:40.1
118.14494 -1.93002 galactic Cas Second-epoch detections are separated by 3.5" and 5.9 pix
The object was found in VSX13" 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:20.24 +60:34:40.1: 15.77 +/- 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:20.24 +60:34:40.1: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 12 20.24 +60 34 40.1 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J001218.47+603439.1,2461208.9203,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J001218.47+603439.1 20260617.4203 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.35 23:23:46.63 +58:23:54.3
111.64220 -2.53872 galactic Cas Second-epoch detections are separated by 7.5" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:46.63 +58:23:54.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 23:23:46.63 +58:23:54.3: 15.40 +/- 0.21 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:23:46.63 +58:23:54.3: 15.14 +/- 0.18 detection
Forced photometry reference-image weighted average: 15.26 +/- 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 17.4203* 23 23 46.63 +58 23 54.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.24 00:11:48.21 +61:45:41.6
118.26150 -0.75026 galactic Cas Second-epoch detections are separated by 5.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 | target | 00:11:48.21 +61:45:41.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:11:48.21 +61:45:41.6: 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:11:48.21 +61:45:41.6: 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 17.4203* 00 11 48.21 +61 45 41.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,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 20260617.4203 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 17.4203 2461208.9203 14.23 00:18:23.17 +58:05:04.5
118.56097 -4.50639 galactic Cas Second-epoch detections are separated by 2.7" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:18:23.17 +58:05:04.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:18:23.17 +58:05:04.5: 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:18:23.17 +58:05:04.5: 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 17.4203* 00 18 23.17 +58 05 04.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,2461208.9203,14.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.21 23:24:56.01 +63:49:19.9
113.56552 2.53474 galactic Cep 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 | 23:24:56.01 +63:49:19.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:24:56.01 +63:49:19.9: 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 23:24:56.01 +63:49:19.9: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.30 00:32:48.60 +63:15:27.0
120.83814 0.46151 galactic Cas Second-epoch detections are separated by 5.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:32:48.60 +63:15:27.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:32:48.60 +63:15:27.0: 15.77 +/- 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:48.60 +63:15:27.0: 15.79 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 32 48.60 +63 15 27.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.28 00:19:14.18 +63:35:38.4
119.36064 0.94576 galactic Cas Second-epoch detections are separated by 0.8" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:19:14.18 +63:35:38.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:19:14.18 +63:35:38.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:19:14.18 +63:35:38.4: 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 17.4203* 00 19 14.18 +63 35 38.4 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.25 00:41:32.04 +65:49:07.4
121.91660 2.96650 galactic Cas Second-epoch detections are separated by 5.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:41:32.04 +65:49:07.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:41:32.04 +65:49:07.4: 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:41:32.04 +65:49:07.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 17.4203* 00 41 32.04 +65 49 07.4 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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
target 20260617.4203 14.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 17.4203 2461208.9203 14.41 00:07:03.07 +57:49:55.7
117.03207 -4.53026 galactic Cas Second-epoch detections are separated by 3.9" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 422650487313757056 | 00:06:59.06 +57:50:23.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:07:03.07 +57:49:55.7: 15.64 +/- 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:07:03.07 +57:49:55.7: 15.35 +/- 0.21 detection
Forced photometry reference-image weighted average: 15.45 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 07 03.07 +57 49 55.7 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 422650487313757056,2461208.9203,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422650487313757056 20260617.4203 14.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.32 23:52:22.47 +65:38:11.6
116.88564 3.46053 galactic Cas 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:52:22.47 +65:38:11.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:22.47 +65:38:11.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 23:52:22.47 +65:38:11.6: 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 17.4203* 23 52 22.47 +65 38 11.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.41 00:05:12.19 +60:11:01.0
117.20997 -2.17348 galactic Cas Second-epoch detections are separated by 0.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:05:12.19 +60:11:01.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:05:12.19 +60:11:01.0: 16.03 +/- 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:12.19 +60:11:01.0: 15.52 +/- 0.23 detection
Forced photometry reference-image weighted average: 15.52 +/- 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 17.4203* 00 05 12.19 +60 11 01.0 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.46 00:19:14.22 +63:34:52.2
119.35912 0.93302 galactic Cas Second-epoch detections are separated by 3.8" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:19:14.22 +63:34:52.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:19:14.22 +63:34:52.2: 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:19:14.22 +63:34:52.2: 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 17.4203* 00 19 14.22 +63 34 52.2 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.47 00:00:08.90 +62:26:20.2
117.03807 0.15557 galactic Cas Second-epoch detections are separated by 5.5" and 6.1 pix
The object was found in VSX15" Gaia DR3 429943616665815680
Type: RS
# Max. Min./Amp. JD0 Period
14.600 G 14.680 G F
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:08.90 +62:26:20.2: 15.35 +/- 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:00:08.90 +62:26:20.2: 15.38 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.36 +/- 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 17.4203* 00 00 08.90 +62 26 20.2 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429943616665815680,2461208.9203,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429943616665815680 20260617.4203 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.49 00:08:01.59 +60:10:45.0
117.55514 -2.23861 galactic Cas Second-epoch detections are separated by 3.4" and 5.6 pix
The object was found in VSX15" Gaia DR3 429286074351344640
Type: ROT
# Max. Min./Amp. JD0 Period
14.540 G 14.570 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:08:01.59 +60:10:45.0: 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:08:01.59 +60:10:45.0: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 08 01.59 +60 10 45.0 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 429286074351344640,2461208.9203,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429286074351344640 20260617.4203 14.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.51 23:42:11.64 +58:56:31.7
114.09130 -2.73595 galactic Cas Second-epoch detections are separated by 3.0" and 5.9 pix
The object was found in VSX12" IRAS 23397+5839
Type: M
# Max. Min./Amp. JD0 Period
15.600 V < 17.900 V 2457749.00000 330.000000000000 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:42:11.64 +58:56:31.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 23:42:11.64 +58:56:31.7: 16.03 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.69 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 42 11.64 +58 56 31.7 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
IRAS 23397+5839,2461208.9203,14.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
IRAS 23397+5839 20260617.4203 14.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.54 23:25:42.11 +59:45:26.6
112.32306 -1.33668 galactic Cas Second-epoch detections are separated by 2.6" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:25:42.11 +59:45: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 23:25:42.11 +59:45:26.6: 15.47 +/- 0.21 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:25:42.11 +59:45:26.6: 15.75 +/- 0.30 detection
Forced photometry reference-image weighted average: 15.56 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 25 42.11 +59 45 26.6 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.41 23:33:19.80 +64:36:26.4
114.67980 2.99436 galactic Cep Second-epoch detections are separated by 6.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:19.80 +64:36:26.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 23:33:19.80 +64:36:26.4: 16.13 +/- 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:33:19.80 +64:36:26.4: 16.14 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.56 00:05:24.83 +57:58:26.9
116.84219 -4.35240 galactic Cas Second-epoch detections are separated by 3.8" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.3637+57.9625 | 00:05:24.83 +57:58:26.9 (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:05:24.83 +57:58:26.9: 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 00:05:24.83 +57:58:26.9: 15.93 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.93 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 05 24.83 +57 58 26.9 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.3637+57.9625,2461208.9203,14.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.3637+57.9625 20260617.4203 14.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 17.4203 2461208.9203 14.62 00:17:24.69 +57:53:58.0
118.40832 -4.67314 galactic Cas Second-epoch detections are separated by 4.3" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:17:24.69 +57:53:58.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:17:24.69 +57:53:58.0: 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:17:24.69 +57:53:58.0: 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 17.4203* 00 17 24.69 +57 53 58.0 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.55 00:01:45.01 +60:05:35.4
116.77052 -2.18283 galactic Cas Second-epoch detections are separated by 3.4" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:45.01 +60:05:35.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:01:45.01 +60:05:35.4: 15.60 +/- 0.24 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:45.01 +60:05:35.4: 16.00 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.72 +/- 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 17.4203* 00 01 45.01 +60 05 35.4 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.51 23:27:39.45 +59:32:06.7
112.48554 -1.62656 galactic Cas Second-epoch detections are separated by 3.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:27:39.45 +59:32:06.7 (user input) | T | P | (position from user input) J-Ks=0.752+/-0.201 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:27:39.45 +59:32:06.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 23:27:39.45 +59:32:06.7: 15.60 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.64 +/- 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 17.4203* 23 27 39.45 +59 32 06.7 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.60 00:06:54.65 +63:35:56.0
118.00617 1.15379 galactic Cas Second-epoch detections are separated by 2.9" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:06:54.65 +63:35: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:06:54.65 +63:35:56.0: 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 00:06:54.65 +63:35:56.0: 15.78 +/- 0.31 detection
Forced photometry reference-image weighted average: 15.78 +/- 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 17.4203* 00 06 54.65 +63 35 56.0 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.71 00:23:27.65 +63:43:17.2
119.84100 1.01772 galactic Cas Second-epoch detections are separated by 3.1" and 5.4 pix
The object was found in VSX24" ZTF J002324.54+634305.1
Type: EW
# Max. Min./Amp. JD0 Period
18.795 r Y 0.748 r 2458345.86100 0.315027000000
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:27.65 +63:43:17.2: 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 00:23:27.65 +63:43:17.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 17.4203* 00 23 27.65 +63 43 17.2 14.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 J002324.54+634305.1,2461208.9203,14.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 J002324.54+634305.1 20260617.4203 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.63 23:49:38.25 +61:05:21.3
115.53135 -0.89139 galactic Cas Second-epoch detections are separated by 0.8" and 6.0 pix
The object was found in VSX17" NSVS J2349357+610521
Type: M
# Max. Min./Amp. JD0 Period
17.456 g Y 4.268 g 2458535.29910 375.860830000000
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:49:38.25 +61:05:21.3: 16.09 +/- 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:49:38.25 +61:05:21.3: 16.06 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 49 38.25 +61 05 21.3 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J2349357+610521,2461208.9203,14.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
NSVS J2349357+610521 20260617.4203 14.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 17.4203 2461208.9203 14.71 00:15:13.00 +58:24:17.6
118.18971 -4.13296 galactic Cas Second-epoch detections are separated by 5.7" and 5.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.7914+58.3974 | 00:15:13.00 +58:24:17.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:15:13.00 +58:24:17.6: 15.84 +/- 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:13.00 +58:24:17.6: 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 17.4203* 00 15 13.00 +58 24 17.6 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J003.7914+58.3974,2461208.9203,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.7914+58.3974 20260617.4203 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.66 00:05:23.38 +63:17:40.0
117.78554 0.88374 galactic Cas Second-epoch detections are separated by 2.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:05:23.38 +63:17:40.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:05:23.38 +63:17:40.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 00:05:23.38 +63:17:40.0: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 05 23.38 +63 17 40.0 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.88 00:16:54.20 +61:35:20.9
118.83551 -1.00763 galactic Cas Second-epoch detections are separated by 3.3" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:54.20 +61:35:20.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:16:54.20 +61:35:20.9: 15.91 +/- 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:54.20 +61:35:20.9: 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 17.4203* 00 16 54.20 +61 35 20.9 14.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,2461208.9203,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.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 17.4203 2461208.9203 14.76 23:26:00.02 +64:22:29.1
113.85637 3.01898 galactic Cep Second-epoch detections are separated by 7.8" and 6.1 pix
The object was found in VSX 0" ZTF J232600.07+642229.3
Type: HADS
# Max. Min./Amp. JD0 Period
17.607 r Y 0.259 r 2458644.97180 0.103544500000
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:26:00.02 +64:22:29.1: 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 23:26:00.02 +64:22:29.1: 16.02 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#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 J232600.07+642229.3,2461208.9203,14.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J232600.07+642229.3 20260617.4203 14.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.89 00:36:10.66 +62:54:05.7
121.19510 0.08131 galactic Cas Second-epoch detections are separated by 3.3" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:36:10.66 +62:54:05.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:36:10.66 +62:54:05.7: 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:36:10.66 +62:54:05.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 17.4203* 00 36 10.66 +62 54 05.7 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.88 00:16:51.50 +60:16:09.8
118.65350 -2.31479 galactic Cas Second-epoch detections are separated by 2.2" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 429147600301787648 | 00:16:51.45 +60:16:34.7 (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:51.50 +60:16:09.8: 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:16:51.50 +60:16:09.8: 16.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 16 51.50 +60 16 09.8 14.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 429147600301787648,2461208.9203,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 429147600301787648 20260617.4203 14.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 17.4203 2461208.9203 14.78 00:15:55.27 +60:47:49.1
118.61086 -1.77645 galactic Cas Second-epoch detections are separated by 3.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:55.27 +60:47:49.1 (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:55.27 +60:47:49.1: 15.92 +/- 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:55.27 +60:47:49.1: 15.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 15 55.27 +60 47 49.1 14.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,2461208.9203,14.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.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 17.4203 2461208.9203 14.91 23:23:22.99 +63:17:59.9
113.22952 2.09910 galactic Cas Second-epoch detections are separated by 6.1" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:23:22.99 +63:17:59.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:23:22.99 +63:17:59.9: 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 23:23:22.99 +63:17:59.9: 16.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 23 22.99 +63 17 59.9 14.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,2461208.9203,14.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.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 17.4203 2461208.9203 14.80 23:24:53.86 +65:29:15.0
114.11010 4.10881 galactic Cep Second-epoch detections are separated by 6.6" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:53.86 +65:29: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:24:53.86 +65:29:15.0: 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 23:24:53.86 +65:29:15.0: 16.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.73 00:16:04.88 +58:06:35.8
118.26160 -4.44083 galactic Cas Second-epoch detections are separated by 1.7" and 6.0 pix
The object was found in VSX15" Gaia DR3 422821255214003456
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.570 G 14.600 G A
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:16:04.88 +58:06:35.8: 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:16:04.88 +58:06:35.8: 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 17.4203* 00 16 04.88 +58 06 35.8 14.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 422821255214003456,2461208.9203,14.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 422821255214003456 20260617.4203 14.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.85 00:08:02.17 +58:55:55.2
117.34685 -3.46830 galactic Cas Second-epoch detections are separated by 4.1" and 5.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:08:02.17 +58:55:55.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:08:02.17 +58:55:55.2: 16.17 +/- 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:08:02.17 +58:55:55.2: 16.13 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 08 02.17 +58 55 55.2 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.72 23:30:14.31 +59:03:26.7
112.64862 -2.18356 galactic Cas Second-epoch detections are separated by 3.6" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:14.31 +59:03:26.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:30:14.31 +59:03:26.7: 15.91 +/- 0.31 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:30:14.31 +59:03:26.7: 15.80 +/- 0.30 detection
Forced photometry reference-image weighted average: 15.85 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 30 14.31 +59 03 26.7 14.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,2461208.9203,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.80 23:26:18.02 +57:28:13.5
111.65410 -3.52521 galactic Cas Second-epoch detections are separated by 5.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:26:18.02 +57:28:13.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:26:18.02 +57:28:13.5: 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 23:26:18.02 +57:28:13.5: 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 17.4203* 23 26 18.02 +57 28 13.5 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.84 00:03:38.27 +60:59:26.0
117.16733 -1.34507 galactic Cas Second-epoch detections are separated by 5.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:38.27 +60:59:26.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:03:38.27 +60:59:26.0: 16.13 +/- 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:03:38.27 +60:59:26.0: 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 17.4203* 00 03 38.27 +60 59 26.0 14.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,2461208.9203,14.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.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 17.4203 2461208.9203 14.91 23:48:28.53 +60:08:08.0
115.16459 -1.78324 galactic Cas Second-epoch detections are separated by 4.5" and 5.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:28.53 +60:08:08.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:48:28.53 +60:08:08.0: 15.79 +/- 0.26 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:48:28.53 +60:08:08.0: 15.99 +/- 0.30 detection
Forced photometry reference-image weighted average: 15.87 +/- 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 17.4203* 23 48 28.53 +60 08 08.0 14.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,2461208.9203,14.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.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 17.4203 2461208.9203 14.85 23:23:44.21 +58:37:42.3
111.71378 -2.32006 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 | 23:23:44.21 +58:37:42.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 23:23:44.21 +58:37:42.3: 15.92 +/- 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:44.21 +58:37:42.3: 15.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 23 44.21 +58 37 42.3 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.92 00:10:34.05 +64:29:07.2
118.54721 1.96209 galactic Cas Second-epoch detections are separated by 6.3" and 6.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:34.05 +64:29:07.2 (user input) | T | P | (position from user input) J-Ks=0.686+/-0.206 (K)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:34.05 +64:29:07.2: 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:10:34.05 +64:29:07.2: 16.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 10 34.05 +64 29 07.2 14.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,2461208.9203,14.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.82 00:00:57.37 +59:27:05.5
116.54834 -2.79309 galactic Cas Second-epoch detections are separated by 3.5" and 6.0 pix
The object was found in VSX18" ZTF J000057.37+592723.2
Type: EW
# Max. Min./Amp. JD0 Period
18.121 r Y 0.131 r 2458263.91310 0.274391800000
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:57.37 +59:27:05.5: 15.93 +/- 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:00:57.37 +59:27:05.5: 16.14 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.93 +/- 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 17.4203* 00 00 57.37 +59 27 05.5 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J000057.37+592723.2,2461208.9203,14.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J000057.37+592723.2 20260617.4203 14.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 15.00 00:07:32.23 +62:23:56.2
117.87144 -0.04068 galactic Cas Second-epoch detections are separated by 4.4" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:32.23 +62:23:56.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:07:32.23 +62:23:56.2: 15.92 +/- 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:32.23 +62:23:56.2: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 07 32.23 +62 23 56.2 15.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,2461208.9203,15.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 20260617.4203 15.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 17.4203 2461208.9203 14.80 00:41:03.48 +65:48:56.9
121.86771 2.96551 galactic Cas Second-epoch detections are separated by 6.1" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:41:03.48 +65:48:56.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:41:03.48 +65:48:56.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 00:41:03.48 +65:48:56.9: 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 17.4203* 00 41 03.48 +65 48 56.9 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.89 23:35:28.05 +65:23:02.0
115.12479 3.67015 galactic Cep Second-epoch detections are separated by 6.5" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:35:28.05 +65:23:02.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:35:28.05 +65:23:02.0: 16.16 +/- 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:35:28.05 +65:23:02.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.72 23:48:55.65 +64:22:26.8
116.23588 2.31809 galactic Cas Second-epoch detections are separated by 5.0" and 5.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:55.65 +64:22: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:48:55.65 +64:22:26.8: 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 23:48:55.65 +64:22:26.8: 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 17.4203* 23 48 55.65 +64 22 26.8 14.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,2461208.9203,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 14.78 23:39:12.94 +57:49:42.3
113.41294 -3.70237 galactic Cas Second-epoch detections are separated by 6.2" and 6.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J354.7957+57.8275 | 23:39:12.94 +57:49:42.3 (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:39:12.94 +57:49:42.3: 15.83 +/- 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:39:12.94 +57:49:42.3: 15.71 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.76 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 39 12.94 +57 49 42.3 14.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 J354.7957+57.8275,2461208.9203,14.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
ATO J354.7957+57.8275 20260617.4203 14.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 17.4203 2461208.9203 14.96 23:22:26.56 +64:30:36.2
113.53862 3.27369 galactic Cep Second-epoch detections are separated by 5.0" and 6.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:22:26.56 +64:30:36.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:22:26.56 +64:30:36.2: 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 23:22:26.56 +64:30:36.2: 15.93 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.85 00:09:06.21 +65:47:19.6
118.60504 3.27331 galactic Cas Second-epoch detections are separated by 4.0" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:06.21 +65:47:19.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:06.21 +65:47:19.6: 16.17 +/- 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:06.21 +65:47:19.6: 16.12 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 09 06.21 +65 47 19.6 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 14.74 23:24:39.02 +59:02:46.5
111.96374 -1.96487 galactic Cas Second-epoch detections are separated by 3.7" and 5.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:24:39.02 +59:02:46.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:24:39.02 +59:02:46.5: 15.47 +/- 0.21 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:24:39.02 +59:02:46.5: 15.87 +/- 0.30 detection
Forced photometry reference-image weighted average: 15.60 +/- 0.17
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 23 24 39.02 +59 02 46.5 14.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,2461208.9203,14.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 20260617.4203 14.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 17.4203 2461208.9203 13.38 00:29:28.08 +60:49:54.1
120.25663 -1.92588 galactic Cas Second-epoch detections are separated by 4.8" and 5.3 pix
The object was found in VSX 8" 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.08 +60:49:54.1: 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 00:29:28.08 +60:49:54.1: 15.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 29 28.08 +60 49 54.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
NSVS J0029273+604956,2461208.9203,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
NSVS J0029273+604956 20260617.4203 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 17.4203 2461208.9203 12.59 00:07:41.01 +64:42:26.4
118.27818 2.23167 galactic Cas Second-epoch detections are separated by 5.5" and 5.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:07:41.01 +64:42:26.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:07:41.01 +64:42:26.4: 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 00:07:41.01 +64:42:26.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 17.4203* 00 07 41.01 +64 42 26.4 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461208.9203,12.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 13.36 23:58:37.40 +58:25:46.6
116.04911 -3.73458 galactic Cas Second-epoch detections are separated by 1.6" and 5.8 pix
The object was found in VSX11" 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:37.40 +58:25:46.6: 14.64 +/- 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:58:37.40 +58:25:46.6: 14.93 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.74 +/- 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 17.4203* 23 58 37.40 +58 25 46.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
2MASS J23583604+5825441,2461208.9203,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
2MASS J23583604+5825441 20260617.4203 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 17.4203 2461208.9203 13.50 23:29:38.28 +64:59:14.5
114.42085 3.47606 galactic Cep Second-epoch detections are separated by 8.2" and 6.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:38.28 +64:59:14.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:29:38.28 +64:59:14.5: 16.09 +/- 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:38.28 +64:59:14.5: 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,2461208.9203,13.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260617.4203 13.50CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 17.4203 2461208.9203 11.79 00:07:06.08 +61:48:59.0
117.72201 -0.60605 galactic Cas Second-epoch detections are separated by 1.7" and 5.8 pix
The object was found in VSX 5" V0658 Cas
Type: M
# Max. Min./Amp. JD0 Period
11.500 V 14.000 V 224.000000000000 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:07:06.08 +61:48:59.0: 13.78 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:07:06.08 +61:48:59.0: 13.56 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.64 +/- 0.03
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 17.4203* 00 07 06.08 +61 48 59.0 11.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
V0658 Cas,2461208.9203,11.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
V0658 Cas 20260617.4203 11.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## 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: 2461208.92063370 17.06.2026 10:05:32.752 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 49
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: 8 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): 27488
Objects passed selection criteria: 27398
Measurements per detected object (mean, median, min, max): 3.0 3.0 2 4
Measurements per selected object (mean, median, min, max): 3.0 3.0 2 4
Average stars detected per image: 21547.5
Average stars matched: 19407.2 (90.0673 %)
Memory usage VmPeak: 128076 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 Wed Jun 17 05:29:31 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: 2461208.92063370 17.06.2026 10:05:32.752 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 451
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: 405 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): 206347
Objects passed selection criteria: 205648
Measurements per detected object (mean, median, min, max): 3.0 3.0 2 4
Measurements per selected object (mean, median, min, max): 3.0 3.0 2 4
Average stars detected per image: 163960
Average stars matched: 149933 (91.445 %)
Memory usage VmPeak: 1961000 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 Wed Jun 17 06:08:08 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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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: 2461208.91997828
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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits'
wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits exists and is non-empty
Saving wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits to local_wcs_cache/
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits' -> 'local_wcs_cache/wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits (1st new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Image size: 941.1'x626.8' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:05.804 +61:59:56.62 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:05.804 +61:59:56.62
Angular distance between the image centers 0.0169 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-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits (2nd new image)
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
Image size: 941.1'x626.7' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.796 +62:00:30.70 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:06.796 +62:00:30.70
Angular distance between the image centers 0.0250 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:05.804 +61:59:56.62
Second-epoch second image center 00:00:06.796 +62:00:30.70
Angular distance between the image centers 0.00966 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.n31Jlw9DXq
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.tjCRQuabjS
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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits &> /tmp/tmp.l0KWtAbFlf
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits &> /tmp/tmp.aqBE9uJOz8
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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 48 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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
2.4 pix fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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
15.1 mag. fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
15.0 mag. fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
All-image limiting magnitude estimate: 15.0 (SNR ) 12.1 (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.n31Jlw9DXq (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/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.tjCRQuabjS (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/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.l0KWtAbFlf (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2674, passed=27492
Got 27492 stars (including 24806 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat
util/solve_plate_with_UCAC5 got 27492 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.1'
Seting catalog search parameters based on the expected field of view 941.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013071 (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.010457 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.5595 through 0 to 19.2945, gap 19.2945 to 340.5595
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 570 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 486 matched stars entering correct_measured_positions(), 446 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.22"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 465 matched stars entering correct_measured_positions(), 15782 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.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.5698 through 0 to 19.3200, gap 19.3200 to 340.5698
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 679 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 631 matched stars entering correct_measured_positions(), 15856 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.45"
Accuracy estimation diagnostic: 628 matched stars entering correct_measured_positions(), 19096 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.38"
Excluding outliers - 628 stars left (next iteration limit 511)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits N_match=628 sigma_overall_arcsec=5.421 sigma_q1_arcsec=11.997 sigma_q2_arcsec=3.119 sigma_q3_arcsec=21.558 sigma_q4_arcsec=4.717 n_q1=158 n_q2=300 n_q3=62 n_q4=108 worst_quadrant_to_overall_ratio=3.977
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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.aqBE9uJOz8 (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
WCS-calibrated image found: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2714, passed=27366
Got 27366 stars (including 24639 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat
util/solve_plate_with_UCAC5 got 27366 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.1'
Seting catalog search parameters based on the expected field of view 941.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013071 (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.010457 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.5601 through 0 to 19.2938, gap 19.2938 to 340.5601
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 571 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 488 matched stars entering correct_measured_positions(), 446 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 468 matched stars entering correct_measured_positions(), 15596 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.69"
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.5710 through 0 to 19.3180, gap 19.3180 to 340.5710
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 684 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 643 matched stars entering correct_measured_positions(), 15679 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.62"
Accuracy estimation diagnostic: 640 matched stars entering correct_measured_positions(), 19359 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.41"
Excluding outliers - 640 stars left (next iteration limit 514)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits N_match=640 sigma_overall_arcsec=5.864 sigma_q1_arcsec=11.860 sigma_q2_arcsec=3.181 sigma_q3_arcsec=24.052 sigma_q4_arcsec=5.205 n_q1=163 n_q2=303 n_q3=66 n_q4=108 worst_quadrant_to_overall_ratio=4.102
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits sigma_overall=5.421 worst_q_ratio=3.977
new2=fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits sigma_overall=5.864 worst_q_ratio=4.102
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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits) flagged: sigma=5.421 (ref avg 1.998), ratio=3.977 (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/lib/make_outxyls_for_astrometric_calibration found 26342 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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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: "out3500420.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3500420.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
log-odds ratio 26.5009 (3.23006e+11), 8 match, 0 conflict, 24 distractors, 105 index.
RA,Dec = (0.102487,61.9864), pixel scale 5.90237 arcsec/pix.
Hit/miss: Hit/miss: -------+---+---+--++---+------++(best)-------+---+-----------+-----------------------+-------+------------
Field 1: solved with index index-4114.fits.
Field 1 solved: writing to file ./out3500420.solved to indicate this.
Field: out3500420.xyls
Field center: (RA,Dec) = (359.997522, 61.998000) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:59.405, +61:59:52.799).
Field size: 15.7269 x 10.5307 degrees
Field rotation angle: up is -0.25364 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits' -> 'fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 17 05:40 fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
-rw-r--r-- 1 apache apache 12K Jun 17 05:40 out3500420.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits (fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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: "out3500420.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3500420.axy"...
Only searching for solutions within 15.6583 degrees of RA,Dec (359.999,61.9988)
log-odds ratio 47.2885 (3.4444e+20), 9 match, 0 conflict, 9 distractors, 29 index.
RA,Dec = (0.0206811,61.9974), pixel scale 5.94805 arcsec/pix.
Hit/miss: Hit/miss: ++++-+---+-++----+(best)-----------------------------------+----------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3500420.solved to indicate this.
Field: out3500420.xyls
Field center: (RA,Dec) = (0.022432, 61.998233) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:05.384, +61:59:53.640).
Field size: 15.7078 x 10.5127 degrees
Field rotation angle: up is -2.42984 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 17 05:40 fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
-rw-r--r-- 1 apache apache 8.5K Jun 17 05:40 out3500420.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.axy"...
Verifying WCS using indices with quads of size [63.3269, 949.308] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS using indices with quads of size [63.3269, 949.308] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field 1 did not solve (index index-4112.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4111.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
Image size: 941.1'x626.8' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:05.804 +61:59:56.62 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 27492 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/correct_sextractor_wcs_catalog_usingxy2sky3935851.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2674, passed=27492
Got 27492 stars (including 24806 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat
util/solve_plate_with_UCAC5 got 27492 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.1'
Seting catalog search parameters based on the expected field of view 941.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013071 (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.010457 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.5595 through 0 to 19.2945, gap 19.2945 to 340.5595
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 570 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 486 matched stars entering correct_measured_positions(), 446 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.22"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 465 matched stars entering correct_measured_positions(), 15782 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.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.5698 through 0 to 19.3200, gap 19.3200 to 340.5698
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 679 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 631 matched stars entering correct_measured_positions(), 15856 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.45"
Accuracy estimation diagnostic: 628 matched stars entering correct_measured_positions(), 19096 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.38"
Excluding outliers - 628 stars left (next iteration limit 511)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits N_match=628 sigma_overall_arcsec=5.421 sigma_q1_arcsec=11.997 sigma_q2_arcsec=3.119 sigma_q3_arcsec=21.558 sigma_q4_arcsec=4.717 n_q1=158 n_q2=300 n_q3=62 n_q4=108 worst_quadrant_to_overall_ratio=3.977
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.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-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits): sigma 5.421->5.421, ratio 3.977->3.977; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits) flagged: sigma=5.864 (ref avg 1.998), ratio=4.102 (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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
WCS_IMAGE_NAME=wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/lib/make_outxyls_for_astrometric_calibration found 26144 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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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: "out3944686.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3944686.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
log-odds ratio 28.2923 (1.93719e+12), 8 match, 0 conflict, 24 distractors, 105 index.
RA,Dec = (0.107013,61.9958), pixel scale 5.90221 arcsec/pix.
Hit/miss: Hit/miss: ---+---+---+------++---+------++(best)-----------+-------+---+-------------------+--------------++--------
Field 1: solved with index index-4114.fits.
Field 1 solved: writing to file ./out3944686.solved to indicate this.
Field: out3944686.xyls
Field center: (RA,Dec) = (0.108736, 61.996636) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:26.097, +61:59:47.888).
Field size: 15.3939 x 10.3572 degrees
Field rotation angle: up is 10.8995 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits' -> 'fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits'
WCS keywords have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 17 05:50 fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
-rw-r--r-- 1 apache apache 8.5K Jun 17 05:50 out3944686.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits (fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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: "out3944686.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3944686.axy"...
Only searching for solutions within 15.3933 degrees of RA,Dec (0.110458,61.9975)
log-odds ratio 47.4065 (3.87596e+20), 9 match, 0 conflict, 9 distractors, 29 index.
RA,Dec = (0.024813,62.0069), pixel scale 5.94801 arcsec/pix.
Hit/miss: Hit/miss: ++++-+-+---++----+(best)-------------------------------------+--------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3944686.solved to indicate this.
Field: out3944686.xyls
Field center: (RA,Dec) = (0.026565, 62.007700) deg.
Field center: (RA H:M:S, Dec D:M:S) = (00:00:06.376, +62:00:27.720).
Field size: 15.7076 x 10.5125 degrees
Field rotation angle: up is -2.42644 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 17 05:50 fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
-rw-r--r-- 1 apache apache 8.5K Jun 17 05:50 out3944686.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits for reading... done!
Creating new image file (wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.axy"...
Verifying WCS using indices with quads of size [63.3265, 949.303] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS using indices with quads of size [63.3265, 949.303] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4112.fits, field objects 21-30).
Field: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
Generating wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat corresponding to the image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits created.
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
verification OK: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
Image size: 941.1'x626.7' 15.7(deg)x10.4(deg) 9576x6388 pix
Image scale: 5.90"/pix along the X axis and 5.89"/pix along the Y axis
Image center: 00:00:06.796 +62:00:30.70 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 27366 stars ###
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/correct_sextractor_wcs_catalog_usingxy2sky107442.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-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
WCS catalog name: wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2714, passed=27366
Got 27366 stars (including 24639 good ones) from the SExtractor catalog wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat
util/solve_plate_with_UCAC5 got 27366 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.1'
Seting catalog search parameters based on the expected field of view 941.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013071 (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.010457 (37.6 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 340.5601 through 0 to 19.2938, gap 19.2938 to 340.5601
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 571 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 488 matched stars entering correct_measured_positions(), 446 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.43"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 468 matched stars entering correct_measured_positions(), 15596 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.69"
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.5710 through 0 to 19.3180, gap 19.3180 to 340.5710
Reading UCAC5 zone files...
Searching UCAC5 zones 729 to 788 (Dec 55.9 to 67.2)
Done reading UCAC5 zone files...
Matched 684 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 643 matched stars entering correct_measured_positions(), 15679 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.62"
Accuracy estimation diagnostic: 640 matched stars entering correct_measured_positions(), 19359 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.41"
Excluding outliers - 640 stars left (next iteration limit 514)
WCS_QUALITY_DIAG: file=fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits N_match=640 sigma_overall_arcsec=5.864 sigma_q1_arcsec=11.860 sigma_q2_arcsec=3.181 sigma_q3_arcsec=24.052 sigma_q4_arcsec=5.205 n_q1=163 n_q2=303 n_q3=66 n_q4=108 worst_quadrant_to_overall_ratio=4.102
The image catalog is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits -region wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits): sigma 5.864->5.864, ratio 4.102->4.102; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=5.421 -- 2.71x the reference average (1.998); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=5.864 -- 2.93x the reference average (1.998); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=3.977 -- 4.62x the reference average (0.861); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=4.102 -- 4.76x 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-17_05-04-36_20.00sec_5.00C_LIGHT_0463_astrometric_residuals.png (628 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 2.29 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464_astrometric_residuals.png (640 matched stars from wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 2.45 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-04-36_20.00sec_5.00C_LIGHT_0463.fits'
Saving fully-calibrated image wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-17_CI_Cas-02-Q2b1x1_052708_TTUQ2b1x1_2961185_Fv4B4kzI/wcs_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464.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:07:38.48 +61:54:06.0: 11.84 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:05:21.40 +62:32:41.6: 12.20 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:20:54.20 +62:27:30.4: 12.98 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:35.35 +60:52:38.6: 12.89 +/- 0.02 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.05 +64:31:55.3: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:22:10.33 +61:21:23.4: 11.87 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:40:56.06 +58:05:30.3: 11.98 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:09.35 +61:53:45.6: 12.53 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:32:17.15 +62:16:19.6: 12.61 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:22:10.33 +61:21:23.4: 11.57 +/- 0.01 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.05 +64:31:55.3: 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:07:38.48 +61:54:06.0: 11.83 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:40:56.06 +58:05:30.3: 11.97 +/- 0.01 detection
Forced photometry reference-image weighted average: 11.68 +/- 0.01
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:05:21.40 +62:32:41.6: 12.09 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:35.35 +60:52:38.6: 12.79 +/- 0.02 detection
Forced photometry filter REJECTED candidate at 23:22:10.33 +61:21:23.4: ref_mag=11.68 +/- 0.01 new_mean_mag=11.8488 delta=-0.17 (need > 0.90)
Forced photometry reference-image weighted average: 11.97 +/- 0.01
Forced photometry reference-image weighted average: 11.83 +/- 0.01
Forced photometry filter REJECTED candidate at 23:40:56.06 +58:05:30.3: ref_mag=11.97 +/- 0.01 new_mean_mag=12.1501 delta=-0.18 (need > 0.90)
Forced photometry filter REJECTED candidate at 00:07:38.48 +61:54:06.0: ref_mag=11.83 +/- 0.01 new_mean_mag=11.7355 delta=0.10 (need > 0.90)
Forced photometry reference-image weighted average: 12.14 +/- 0.01
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:20:54.20 +62:27:30.4: 12.59 +/- 0.02 detection
Forced photometry filter REJECTED candidate at 00:05:21.40 +62:32:41.6: ref_mag=12.14 +/- 0.01 new_mean_mag=11.9928 delta=0.15 (need > 0.90)
Forced photometry reference-image weighted average: 12.84 +/- 0.02
Forced photometry filter REJECTED candidate at 00:16:35.35 +60:52:38.6: ref_mag=12.84 +/- 0.02 new_mean_mag=11.9717 delta=0.87 (need > 0.90)
Forced photometry reference-image weighted average: 12.72 +/- 0.02
Forced photometry filter KEPT candidate at 00:20:54.20 +62:27:30.4: ref_mag=12.72 +/- 0.02 new_mean_mag=11.3204 delta=1.40 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:09.35 +61:53:45.6: 12.44 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.48 +/- 0.01
Forced photometry filter REJECTED candidate at 00:17:09.35 +61:53:45.6: ref_mag=12.48 +/- 0.01 new_mean_mag=12.0076 delta=0.48 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:32:17.15 +62:16:19.6: 12.92 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.72 +/- 0.02
Forced photometry filter REJECTED candidate at 00:32:17.15 +62:16:19.6: ref_mag=12.72 +/- 0.02 new_mean_mag=12.0560 delta=0.66 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:18:35.96 +60:54:48.9: 12.62 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:18:35.96 +60:54:48.9: 12.58 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:15:28.13 +61:28:18.7: 13.58 +/- 0.04 detection
Forced photometry reference-image weighted average: 12.60 +/- 0.02
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:31:48.81 +60:14:07.0: 13.00 +/- 0.03 detection
Forced photometry filter REJECTED candidate at 00:18:35.96 +60:54:48.9: ref_mag=12.60 +/- 0.02 new_mean_mag=12.0355 delta=0.56 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:54.50 +63:14:30.7: 13.52 +/- 0.05 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:14:02.64 +63:43:33.8: 13.22 +/- 0.04 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.78 +62:35:32.8: 14.05 +/- 0.10 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:16:15.78 +61:51:00.7: 13.04 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:18:09.21 +60:52:59.6: 12.98 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:15:28.13 +61:28:18.7: 13.22 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.35 +/- 0.03
Forced photometry filter KEPT candidate at 00:15:28.13 +61:28:18.7: ref_mag=13.35 +/- 0.03 new_mean_mag=12.1251 delta=1.22 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:31:48.81 +60:14:07.0: 12.81 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:10:54.50 +63:14:30.7: 12.62 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.88 +/- 0.02
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:16:15.78 +61:51:00.7: 12.73 +/- 0.02 detection
Forced photometry filter REJECTED candidate at 00:31:48.81 +60:14:07.0: ref_mag=12.88 +/- 0.02 new_mean_mag=12.0294 delta=0.85 (need > 0.90)
Forced photometry reference-image weighted average: 12.76 +/- 0.02
Forced photometry filter REJECTED candidate at 00:10:54.50 +63:14:30.7: ref_mag=12.76 +/- 0.02 new_mean_mag=12.0473 delta=0.71 (need > 0.90)
Forced photometry reference-image weighted average: 12.83 +/- 0.02
Forced photometry filter REJECTED candidate at 00:16:15.78 +61:51:00.7: ref_mag=12.83 +/- 0.02 new_mean_mag=12.1077 delta=0.72 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:23.78 +62:35:32.8: 13.74 +/- 0.07 detection
Forced photometry reference-image weighted average: 13.84 +/- 0.06
Forced photometry filter KEPT candidate at 00:34:23.78 +62:35:32.8: ref_mag=13.84 +/- 0.06 new_mean_mag=12.1821 delta=1.66 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:14:02.64 +63:43:33.8: 12.75 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.87 +/- 0.02
Forced photometry filter REJECTED candidate at 00:14:02.64 +63:43:33.8: ref_mag=12.87 +/- 0.02 new_mean_mag=12.1205 delta=0.75 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:18:09.21 +60:52:59.6: 12.77 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.85 +/- 0.02
Forced photometry filter REJECTED candidate at 00:18:09.21 +60:52:59.6: ref_mag=12.85 +/- 0.02 new_mean_mag=12.1625 delta=0.69 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:09.31 +60:21:43.0: 12.31 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:10:11.28 +61:40:53.4: 13.10 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:09.31 +60:21:43.0: 12.39 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:57.91 +61:39:21.5: 12.52 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.35 +/- 0.01
Forced photometry filter REJECTED candidate at 00:09:09.31 +60:21:43.0: ref_mag=12.35 +/- 0.01 new_mean_mag=12.1407 delta=0.21 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:30.02 +62:35:02.8: 12.55 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:23.85 +60:16:19.9: 12.66 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:18.73 +61:39:29.8: 14.06 +/- 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:10:11.28 +61:40:53.4: 12.70 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.82 +/- 0.02
Forced photometry filter REJECTED candidate at 00:10:11.28 +61:40:53.4: ref_mag=12.82 +/- 0.02 new_mean_mag=12.1934 delta=0.63 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:57.91 +61:39:21.5: 12.49 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.51 +/- 0.01
Forced photometry filter REJECTED candidate at 00:09:57.91 +61:39:21.5: ref_mag=12.51 +/- 0.01 new_mean_mag=12.1852 delta=0.32 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:30.02 +62:35:02.8: 12.47 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.51 +/- 0.01
Forced photometry filter REJECTED candidate at 00:09:30.02 +62:35:02.8: ref_mag=12.51 +/- 0.01 new_mean_mag=12.1904 delta=0.32 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:23.85 +60:16:19.9: 12.76 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.70 +/- 0.01
Forced photometry filter REJECTED candidate at 00:17:23.85 +60:16:19.9: ref_mag=12.70 +/- 0.01 new_mean_mag=12.1951 delta=0.51 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:18.73 +61:39:29.8: 13.86 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.93 +/- 0.05
Forced photometry filter KEPT candidate at 00:17:18.73 +61:39:29.8: ref_mag=13.93 +/- 0.05 new_mean_mag=12.1928 delta=1.74 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:58:22.49 +60:44:50.2: 12.19 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:34:55.26 +62:55:46.4: 14.79 +/- 0.15 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:58:22.49 +60:44:50.2: 12.19 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.19 +/- 0.01
Forced photometry filter REJECTED candidate at 23:58:22.49 +60:44:50.2: ref_mag=12.19 +/- 0.01 new_mean_mag=12.1689 delta=0.02 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:26:11.51 +62:03:55.5: 15.10 +/- 0.19 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:30:00.02 +59:04:51.1: 12.93 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:06:41.09 +62:26:33.9: 12.59 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:34:55.26 +62:55:46.4: 14.58 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.66 +/- 0.09
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:26:11.51 +62:03:55.5: 14.18 +/- 0.08 detection
Forced photometry filter KEPT candidate at 00:34:55.26 +62:55:46.4: ref_mag=14.66 +/- 0.09 new_mean_mag=12.2355 delta=2.42 (need > 0.90)
Forced photometry reference-image weighted average: 14.33 +/- 0.07
Forced photometry filter KEPT candidate at 00:26:11.51 +62:03:55.5: ref_mag=14.33 +/- 0.07 new_mean_mag=12.2266 delta=2.10 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:30:00.02 +59:04:51.1: 12.77 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.83 +/- 0.02
Forced photometry filter REJECTED candidate at 00:30:00.02 +59:04:51.1: ref_mag=12.83 +/- 0.02 new_mean_mag=12.2280 delta=0.61 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:08:56.44 +62:33:28.1: 12.34 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:06:41.09 +62:26:33.9: 12.41 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.49 +/- 0.01
Forced photometry filter REJECTED candidate at 00:06:41.09 +62:26:33.9: ref_mag=12.49 +/- 0.01 new_mean_mag=12.2167 delta=0.27 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:17:58.84 +60:55:03.6: 13.01 +/- 0.03 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:08:56.44 +62:33:28.1: 12.31 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.33 +/- 0.01
Forced photometry filter REJECTED candidate at 00:08:56.44 +62:33:28.1: ref_mag=12.33 +/- 0.01 new_mean_mag=12.2263 delta=0.10 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:55:25.66 +64:08:38.7: 15.71 +/- 0.30 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:11:32.58 +61:13:57.0: 13.42 +/- 0.04 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:17:58.84 +60:55:03.6: 12.76 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.86 +/- 0.02
Forced photometry filter REJECTED candidate at 00:17:58.84 +60:55:03.6: ref_mag=12.86 +/- 0.02 new_mean_mag=12.2247 delta=0.63 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:09:19.74 +61:54:16.0: 12.59 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:55:25.66 +64:08:38.7: 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:11:32.58 +61:13:57.0: 13.47 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.45 +/- 0.03
Forced photometry reference-image weighted average: 15.71 +/- 0.30
Forced photometry filter KEPT candidate at 00:11:32.58 +61:13:57.0: ref_mag=13.45 +/- 0.03 new_mean_mag=12.2483 delta=1.20 (need > 0.90)
Forced photometry filter KEPT candidate at 23:55:25.66 +64:08:38.7: ref_mag=15.71 +/- 0.30 new_mean_mag=12.2248 delta=3.49 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:09:19.74 +61:54:16.0: 12.47 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.53 +/- 0.01
Forced photometry filter REJECTED candidate at 00:09:19.74 +61:54:16.0: ref_mag=12.53 +/- 0.01 new_mean_mag=12.2523 delta=0.27 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:02:36.86 +60:54:36.9: 12.28 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:02:36.86 +60:54:36.9: 12.29 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.28 +/- 0.01
Forced photometry filter REJECTED candidate at 00:02:36.86 +60:54:36.9: ref_mag=12.28 +/- 0.01 new_mean_mag=12.2388 delta=0.04 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:39:08.90 +63:36:36.4: 12.86 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:39:08.90 +63:36:36.4: 13.08 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.96 +/- 0.02
Forced photometry filter REJECTED candidate at 00:39:08.90 +63:36:36.4: ref_mag=12.96 +/- 0.02 new_mean_mag=12.2356 delta=0.72 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:12:07.12 +57:57:36.0: 12.40 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 23:57:23.70 +62:37:58.5: 12.29 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:12:07.12 +57:57:36.0: 12.45 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.43 +/- 0.01
Forced photometry filter REJECTED candidate at 00:12:07.12 +57:57:36.0: ref_mag=12.43 +/- 0.01 new_mean_mag=12.2489 delta=0.18 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:11:14.87 +64:53:33.2: 14.56 +/- 0.11 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:04:44.99 +61:34:34.1: 12.38 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 23:57:23.70 +62:37:58.5: 12.23 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.26 +/- 0.01
Forced photometry filter REJECTED candidate at 23:57:23.70 +62:37:58.5: ref_mag=12.26 +/- 0.01 new_mean_mag=12.2432 delta=0.01 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:04:44.99 +61:34:34.1: 12.41 +/- 0.01 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:11:14.87 +64:53:33.2: 14.90 +/- 0.15 detection
Forced photometry reference-image weighted average: 12.39 +/- 0.01
Forced photometry filter REJECTED candidate at 00:04:44.99 +61:34:34.1: ref_mag=12.39 +/- 0.01 new_mean_mag=12.2829 delta=0.11 (need > 0.90)
Forced photometry reference-image weighted average: 14.68 +/- 0.09
Forced photometry filter KEPT candidate at 00:11:14.87 +64:53:33.2: ref_mag=14.68 +/- 0.09 new_mean_mag=12.2671 delta=2.41 (need > 0.90)
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-08_19-44-36_20.00sec_-14.90C_LIGHT_0011.fits at 00:01:37.18 +61:15:41.1: 12.34 +/- 0.02 detection
Forced photometry on wcs_Cas-02-Q2b1x1_2026-01-20_19-33-13_20.00sec_-14.90C_LIGHT_0014.fits at 00:01:37.18 +61:15:41.1: 12.33 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.33 +/- 0.01
Forced photometry filter REJECTED candidate at 00:01:37.18 +61:15:41.1: ref_mag=12.33 +/- 0.01 new_mean_mag=12.2878 delta=0.05 (need > 0.90)
util/fov_of_wcs_calibrated_image.sh: line 144: echo: write error: Broken pipe
Adding exclusion_list_gaiadr2.txt__out32089.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out35977.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out36147.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out36158.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out33986.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35812.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36133.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36303.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36313.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36428.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 25s
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: 6s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32084_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 32084_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32085_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 32085_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32089_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 32089_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:20:54.20 +62:27:30.4 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=11.32, MAG_FAINT_SEARCH_LIMIT=12.30)GAIADR2_OUTPUT=# 4.264 430509040515680000 005.22334750576 +62.45873090347 11.1935 11.0494 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#4.264#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32410_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 32410_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:36:59.53 +63:08:00.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33986_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 33986_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 34640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:07:05.70 +61:48:57.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 34800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35062_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35062_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35338_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35338_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35433_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35433_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35521_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35521_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35619_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35619_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35636_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35636_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35751_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35751_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35812_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 35812_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35863_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35863_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35977_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 35977_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:34:23.78 +62:35:32.8 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.18, MAG_FAINT_SEARCH_LIMIT=13.16)GAIADR2_OUTPUT=# 5.259 430690940972143232 008.59593101730 +62.59261196176 12.0589 11.6191 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.259#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36017_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36017_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36043_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36043_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36052_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36052_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36070_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36070_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36091_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36091_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36108_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36108_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36131_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36131_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36133_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 36133_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36137_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36137_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36147_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36147_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:34:55.26 +62:55:46.4 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.23, MAG_FAINT_SEARCH_LIMIT=13.21)GAIADR2_OUTPUT=# 5.812 430724510437461248 008.72682678919 +62.92997932580 11.8004 10.9478 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.812#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36156_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36156_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (23.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36158_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36158_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:26:11.51 +62:03:55.5 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=12.22, MAG_FAINT_SEARCH_LIMIT=13.20)GAIADR2_OUTPUT=# 5.339 430427401780936960 006.54488856845 +62.06505404615 12.0158 11.4532 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.339#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36198_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36198_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36225_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36225_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36266_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36266_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:21:26.00 +59:13:55.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36300_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36300_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36303_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 36303_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36313_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 36313_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36326_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36326_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36328_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36328_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36336_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36336_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36341_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36341_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36345_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36345_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36400_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36400_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36403_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36403_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 36428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36463_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36463_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36505_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 36505_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246356_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246356_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246368_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246368_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246369_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246369_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246379_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246379_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246397_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246397_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246407_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246407_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (23.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246411_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246411_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246414_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246414_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246417_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246417_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246419_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246419_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246421_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246421_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246423_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246423_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246427_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246427_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246430_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246430_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246433_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246433_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246439_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246439_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246440_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246440_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246443_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246443_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246444_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246444_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246446_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246446_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246447_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246447_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246448_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246448_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246451_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246451_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246454_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246454_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246456_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246456_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246457_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246457_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (26.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246461_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246461_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246464_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246464_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246472_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246472_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246475_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246475_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246481_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246481_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (19.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246486_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246486_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246494_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246494_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246499_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246499_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246504_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246504_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246510_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246510_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246511_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246511_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246512_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246512_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (18.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246514_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246514_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246517_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246517_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246518_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246518_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246521_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246521_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246529_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246529_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246533_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246533_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246536_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246536_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246537_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246537_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246539_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246539_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246540_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246540_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246542_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246542_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246545_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246545_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (24.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246555_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246555_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246556_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246556_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246558_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246558_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246567_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246567_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (24.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246568_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246568_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246572_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246572_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (25.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246573_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246573_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246574_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246574_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246575_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246575_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246576_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246576_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246579_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246579_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246586_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246586_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246589_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246589_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246595_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246595_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246597_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246597_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246598_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246598_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246601_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246601_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246608_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246608_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246609_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246609_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246610_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246610_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246612_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246612_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246619_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246619_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246625_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246625_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246632_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246632_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246638_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246638_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246642_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246642_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246647_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246647_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246651_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246651_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (22.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246657_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246657_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246659_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246659_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246661_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246661_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246665_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246665_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246669_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246669_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246670_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246670_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246678_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246678_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246680_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246680_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246681_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246681_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:10:43.74 +63:25:22.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246682_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246682_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246688_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246688_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246690_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246690_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246693_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246693_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246695_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246695_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246698_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 246698_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246699_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 246699_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249908_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 249908_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (44.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251163_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 251163_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252957_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 252957_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 253281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253377_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 253377_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254487_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 254487_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254510_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 254510_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254693_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 254693_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255763_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 255763_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256223_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 256223_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256394_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 256394_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256746_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 256746_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256762_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 256762_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257209_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 257209_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257274_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 257274_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257283_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 257283_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 257293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:05:15.32 +61:17:30.0 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257406_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 257406_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (22.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257462_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 257462_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258170_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 258170_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258883_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 258883_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:01:42.08 +61:11:25.3 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259173_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 259173_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259226_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 259226_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259307_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 259307_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259377_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 259377_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 259605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260138_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 260138_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260300_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 260300_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260338_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 260338_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260349_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 260349_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260596_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 260596_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (44.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260773_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 260773_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260810_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 260810_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260818_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 260818_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260906_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 260906_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260947_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 260947_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261387_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 261387_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261425_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 261425_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261715_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 261715_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 23:29:49.06 +58:31:42.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261722_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 261722_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261846_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 261846_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261959_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 261959_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262519_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 262519_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262593_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 262593_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262943_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 262943_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262985_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 262985_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263497_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 263497_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264158_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264158_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:30:33.63 +63:40:55.5 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.91, MAG_FAINT_SEARCH_LIMIT=14.89)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264217_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 264217_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264458_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 264458_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 264471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264656_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264656_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264721_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264721_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264731_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264731_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264975_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 264975_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264980_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 264980_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265147_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 265147_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:17:09.45 +61:30:52.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 265471_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265894_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 265894_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266009_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266009_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266181_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 266181_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266205_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266205_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:01:49.37 +61:14:35.1 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266420_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266420_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266446_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 266446_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266502_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266502_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266599_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266599_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 266711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266781_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 266781_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266975_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 266975_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267008_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 267008_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267189_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267189_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267249_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 267249_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267269_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267269_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267439_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267439_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267460_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267460_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267470_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 267470_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267640_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267687_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 267687_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 267711_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268016_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268016_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268079_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268079_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268080_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268080_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268134_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268134_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268168_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268168_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268280_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268280_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268282_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268282_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268298_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268298_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:28:42.60 +63:24:30.9 in Gaia DR2 single (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.17, MAG_FAINT_SEARCH_LIMIT=15.15)GAIADR2_OUTPUT=# 5.652 430987121917655808 007.17418326191 +63.40807310030 13.9619 13.2607 NOT_AVAILABLE#N_GAIA_STARS_WITIN_BLEND_SEARCH_RADIUS=#1#DISTANCE_ARCSEC=#5.652#MAX_ANGULAR_DISTANCE_BETWEEN_MEASURED_POSITION_AND_CATALOG_MATCH_ARCSEC=#5.9#
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268420_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268420_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268639_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268639_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268649_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268649_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268660_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268660_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268706_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268706_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268729_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268729_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268743_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 268743_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268817_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 268817_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269015_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 269015_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269023_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 269023_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269024_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269024_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269052_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 269052_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269239_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269239_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269301_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269301_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269309_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269309_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269730_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269730_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269765_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269765_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269793_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269793_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269920_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 269920_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269941_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 269941_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270116_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270116_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270423_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270423_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270531_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 270531_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270676_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270676_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 270800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270803_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 270803_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270816_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270816_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270930_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 270930_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270950_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 270950_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271251_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 271251_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271415_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271415_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271443_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271443_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271490_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271490_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271567_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 271567_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271746_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271746_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271872_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271872_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271910_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 271910_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272044_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272044_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272335_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272335_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272366_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272366_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272637_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 272637_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272675_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272675_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272942_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 272942_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272948_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 272948_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (20.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273068_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 273068_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273293_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273297_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273297_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273322_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273322_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273438_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 273438_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273544_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 273544_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273553_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273553_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 273653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273800_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273805_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 273805_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273946_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 273946_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274228_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274228_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274437_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 274437_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274508_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274508_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274555_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274555_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274604_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274605_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274609_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274609_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274625_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274625_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274633_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 274633_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 274671_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274729_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 274729_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274938_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 274938_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275234_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 275234_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275606_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275606_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275699_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275699_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275806_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275806_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275813_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275813_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275855_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275855_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275883_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275883_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275909_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275909_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275990_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 275990_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276065_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276065_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (46.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276111_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276111_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276136_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276136_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276177_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 276177_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276421_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 276421_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276434_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 276434_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276490_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 276490_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276553_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276553_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276632_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276632_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276664_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276664_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276761_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276761_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276778_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276778_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276858_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276858_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276905_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276905_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (24.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276922_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 276922_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276993_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 276993_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277073_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277073_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277100_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277100_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277104_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277104_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277187_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277187_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277208_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277208_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277248_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277248_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277276_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277276_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277363_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277363_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277538_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277538_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277557_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277557_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277558_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277558_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277589_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277589_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277636_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277636_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277741_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277741_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277805_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277805_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277861_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277861_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277876_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277876_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277877_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277877_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277930_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 277930_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277973_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 277973_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278039_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278039_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278058_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278058_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278196_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278196_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278314_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278314_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278361_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278361_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278373_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278373_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278391_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278391_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278428_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278462_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278462_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278491_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278491_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (36.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278492_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278492_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (15.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278523_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278523_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278541_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278541_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278546_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278546_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (10.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278598_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278598_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278683_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278683_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278688_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278688_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278735_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278735_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278747_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278747_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278792_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278792_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278796_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278796_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278804_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278804_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278835_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278835_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278896_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278896_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278913_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 278913_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278929_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278929_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278932_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278932_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278963_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278963_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278992_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 278992_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279019_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279019_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279061_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 279061_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279107_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279107_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (16.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279117_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279117_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279172_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279172_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279192_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279192_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279207_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279207_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 279281_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279339_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279339_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (36.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279343_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279343_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279346_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279346_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279398_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279398_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279410_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279410_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279431_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279431_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279452_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 279452_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279470_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279470_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279559_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 279559_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 49463_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 49463_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:36:59.35 +63:08:03.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 236991_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 236991_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 30302_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 30302_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 189730_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 189730_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46413_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 46413_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 29265_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 29265_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 92653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 92653_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
Rejecting candidate due to large distance (12.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 97063_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
Preparing report for the candidate 97063_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 24334_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464
The candidate 24334_fd_Cas-02-Q2b1x1_2026-06-17_05-05-32_20.00sec_5.00C_LIGHT_0464 did not pass the final checks
**** FOUND 00:34:23.51 +64:31:53.4 in the exclusion list exclusion_list_local.txt ****
make_report_in_HTML.sh Phase 2 (HTML assembly): 6s
make_report_in_HTML.sh TOTAL: 295s
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.05 +64:31:55.3
00:15:28.13 +61:28:18.7
00:17:18.73 +61:39:29.8
23:55:25.66 +64:08:38.7
00:11:32.58 +61:13:57.0
00:11:14.87 +64:53:33.2
23:58:37.40 +58:25:46.6
00:29:28.08 +60:49:54.1
00:16:47.48 +64:42:54.8
00:23:11.84 +63:49:18.6
23:57:03.44 +61:22:15.0
23:25:18.81 +57:37:12.2
23:31:56.96 +65:42:21.6
23:25:05.21 +64:43:23.9
00:03:10.72 +64:44:02.1
00:04:36.75 +60:35:02.5
23:55:57.21 +64:02:12.2
00:02:52.95 +62:04:53.3
00:23:25.11 +61:50:19.2
00:23:13.57 +62:26:43.2
00:20:43.12 +62:52:57.2
00:34:22.09 +60:00:43.8
00:06:56.79 +62:32:10.1
00:13:25.13 +63:15:27.0
23:41:35.07 +59:35:28.8
00:20:21.88 +60:15:51.5
00:03:35.60 +63:34:46.8
23:22:21.62 +62:39:45.7
00:16:14.03 +60:59:38.4
00:21:26.52 +59:13:56.8
00:16:40.71 +65:59:41.4
00:35:16.36 +63:00:43.9
00:21:57.21 +61:46:06.0
00:15:12.25 +58:24:53.0
00:30:23.76 +60:12:41.2
23:52:13.37 +65:38:33.0
00:10:26.28 +60:01:06.0
00:10:45.95 +63:25:28.6
00:00:30.32 +65:48:24.4
00:21:47.83 +61:02:51.6
00:35:29.49 +61:53:07.8
00:40:45.95 +64:16:35.6
00:15:43.58 +59:34:01.8
00:15:02.92 +61:26:04.5
00:07:46.77 +61:54:28.1
00:12:36.08 +62:53:08.1
00:23:45.40 +59:32:00.7
00:23:31.68 +65:19:46.1
00:00:34.43 +62:49:36.3
23:23:48.81 +65:45:07.0
00:01:10.87 +64:55:36.9
00:03:30.11 +58:28:54.0
00:01:55.45 +63:10:47.0
00:02:05.62 +63:18:19.2
23:59:26.60 +63:49:12.2
00:13:51.00 +59:58:37.1
23:24:19.46 +64:02:47.3
00:09:16.33 +59:38:42.3
00:07:57.70 +63:21:39.1
00:30:05.13 +60:13:25.0
00:09:21.55 +61:47:56.5
23:57:00.59 +63:29:18.0
00:07:53.22 +57:56:32.6
00:17:57.20 +59:09:21.0
00:05:34.26 +62:32:06.0
00:03:11.57 +62:20:26.2
00:31:00.50 +61:24:59.0
00:09:06.05 +58:45:35.0
00:23:13.48 +60:17:38.6
00:19:25.32 +59:23:44.7
00:22:22.70 +59:28:18.3
23:47:42.13 +60:42:41.8
00:07:11.59 +57:51:19.1
00:28:07.61 +63:12:32.1
00:16:23.24 +61:54:20.2
00:12:20.24 +60:34:40.1
23:23:46.63 +58:23:54.3
00:11:48.21 +61:45:41.6
00:18:23.17 +58:05:04.5
23:24:56.01 +63:49:19.9
00:32:48.60 +63:15:27.0
00:19:14.18 +63:35:38.4
00:41:32.04 +65:49:07.4
00:07:03.07 +57:49:55.7
23:52:22.47 +65:38:11.6
00:05:12.19 +60:11:01.0
00:19:14.22 +63:34:52.2
00:00:08.90 +62:26:20.2
00:08:01.59 +60:10:45.0
23:42:11.64 +58:56:31.7
23:25:42.11 +59:45:26.6
23:33:19.80 +64:36:26.4
00:05:24.83 +57:58:26.9
00:17:24.69 +57:53:58.0
00:01:45.01 +60:05:35.4
23:27:39.45 +59:32:06.7
00:06:54.65 +63:35:56.0
00:23:27.65 +63:43:17.2
23:49:38.25 +61:05:21.3
00:15:13.00 +58:24:17.6
00:05:23.38 +63:17:40.0
00:16:54.20 +61:35:20.9
23:26:00.02 +64:22:29.1
00:36:10.66 +62:54:05.7
00:16:51.50 +60:16:09.8
00:15:55.27 +60:47:49.1
23:23:22.99 +63:17:59.9
23:24:53.86 +65:29:15.0
00:16:04.88 +58:06:35.8
00:08:02.17 +58:55:55.2
23:30:14.31 +59:03:26.7
23:26:18.02 +57:28:13.5
00:03:38.27 +60:59:26.0
23:48:28.53 +60:08:08.0
23:23:44.21 +58:37:42.3
00:10:34.05 +64:29:07.2
00:00:57.37 +59:27:05.5
00:07:32.23 +62:23:56.2
00:41:03.48 +65:48:56.9
23:35:28.05 +65:23:02.0
23:48:55.65 +64:22:26.8
23:39:12.94 +57:49:42.3
23:22:26.56 +64:30:36.2
00:09:06.21 +65:47:19.6
23:24:39.02 +59:02:46.5
23:29:38.28 +64:59:14.5
00:07:41.01 +64:42:26.4
00:07:06.08 +61:48:59.0
########### 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.05 +64:31:55.3
00:15:28.13 +61:28:18.7
00:17:18.73 +61:39:29.8
23:55:25.66 +64:08:38.7
00:11:32.58 +61:13:57.0
00:11:14.87 +64:53:33.2
00:16:47.48 +64:42:54.8
00:23:11.84 +63:49:18.6
23:57:03.44 +61:22:15.0
23:25:18.81 +57:37:12.2
23:31:56.96 +65:42:21.6
23:25:05.21 +64:43:23.9
00:03:10.72 +64:44:02.1
00:04:36.75 +60:35:02.5
23:55:57.21 +64:02:12.2
00:02:52.95 +62:04:53.3
00:23:25.11 +61:50:19.2
00:23:13.57 +62:26:43.2
00:20:43.12 +62:52:57.2
00:34:22.09 +60:00:43.8
00:06:56.79 +62:32:10.1
00:13:25.13 +63:15:27.0
23:41:35.07 +59:35:28.8
00:20:21.88 +60:15:51.5
00:03:35.60 +63:34:46.8
23:22:21.62 +62:39:45.7
00:16:14.03 +60:59:38.4
00:21:26.52 +59:13:56.8
00:16:40.71 +65:59:41.4
00:35:16.36 +63:00:43.9
00:21:57.21 +61:46:06.0
00:15:12.25 +58:24:53.0
00:30:23.76 +60:12:41.2
23:52:13.37 +65:38:33.0
00:10:26.28 +60:01:06.0
00:10:45.95 +63:25:28.6
00:00:30.32 +65:48:24.4
00:21:47.83 +61:02:51.6
00:35:29.49 +61:53:07.8
00:40:45.95 +64:16:35.6
00:15:43.58 +59:34:01.8
00:15:02.92 +61:26:04.5
00:07:46.77 +61:54:28.1
00:12:36.08 +62:53:08.1
00:23:45.40 +59:32:00.7
00:23:31.68 +65:19:46.1
00:00:34.43 +62:49:36.3
23:23:48.81 +65:45:07.0
00:01:10.87 +64:55:36.9
00:03:30.11 +58:28:54.0
00:01:55.45 +63:10:47.0
00:02:05.62 +63:18:19.2
23:59:26.60 +63:49:12.2
00:13:51.00 +59:58:37.1
23:24:19.46 +64:02:47.3
00:09:16.33 +59:38:42.3
00:07:57.70 +63:21:39.1
00:30:05.13 +60:13:25.0
00:09:21.55 +61:47:56.5
23:57:00.59 +63:29:18.0
00:07:53.22 +57:56:32.6
00:17:57.20 +59:09:21.0
00:05:34.26 +62:32:06.0
00:03:11.57 +62:20:26.2
00:31:00.50 +61:24:59.0
00:09:06.05 +58:45:35.0
00:23:13.48 +60:17:38.6
00:19:25.32 +59:23:44.7
00:22:22.70 +59:28:18.3
23:47:42.13 +60:42:41.8
00:07:11.59 +57:51:19.1
00:28:07.61 +63:12:32.1
00:16:23.24 +61:54:20.2
00:12:20.24 +60:34:40.1
23:23:46.63 +58:23:54.3
00:11:48.21 +61:45:41.6
00:18:23.17 +58:05:04.5
23:24:56.01 +63:49:19.9
00:32:48.60 +63:15:27.0
00:19:14.18 +63:35:38.4
00:41:32.04 +65:49:07.4
00:07:03.07 +57:49:55.7
23:52:22.47 +65:38:11.6
00:05:12.19 +60:11:01.0
00:19:14.22 +63:34:52.2
00:00:08.90 +62:26:20.2
00:08:01.59 +60:10:45.0
23:42:11.64 +58:56:31.7
23:25:42.11 +59:45:26.6
23:33:19.80 +64:36:26.4
00:05:24.83 +57:58:26.9
00:17:24.69 +57:53:58.0
00:01:45.01 +60:05:35.4
23:27:39.45 +59:32:06.7
00:06:54.65 +63:35:56.0
00:23:27.65 +63:43:17.2
23:49:38.25 +61:05:21.3
00:15:13.00 +58:24:17.6
00:05:23.38 +63:17:40.0
00:16:54.20 +61:35:20.9
23:26:00.02 +64:22:29.1
00:36:10.66 +62:54:05.7
00:16:51.50 +60:16:09.8
00:15:55.27 +60:47:49.1
23:23:22.99 +63:17:59.9
23:24:53.86 +65:29:15.0
00:16:04.88 +58:06:35.8
00:08:02.17 +58:55:55.2
23:30:14.31 +59:03:26.7
23:26:18.02 +57:28:13.5
00:03:38.27 +60:59:26.0
23:48:28.53 +60:08:08.0
23:23:44.21 +58:37:42.3
00:10:34.05 +64:29:07.2
00:00:57.37 +59:27:05.5
00:07:32.23 +62:23:56.2
00:41:03.48 +65:48:56.9
23:35:28.05 +65:23:02.0
23:48:55.65 +64:22:26.8
23:39:12.94 +57:49:42.3
23:22:26.56 +64:30:36.2
00:09:06.21 +65:47:19.6
23:24:39.02 +59:02:46.5
00:29:28.08 +60:49:54.1
00:07:41.01 +64:42:26.4
23:58:37.40 +58:25:46.6
23:29:38.28 +64:59:14.5
00:07:06.08 +61:48:59.0
###################################################################################
00:34:23.05 +64:31:55.3 -- not an asteroid (will add it to exclusion list)
00:15:28.13 +61:28:18.7 -- not an asteroid (will add it to exclusion list)
00:17:18.73 +61:39:29.8 -- not an asteroid (will add it to exclusion list)
23:55:25.66 +64:08:38.7 -- not an asteroid (will add it to exclusion list)
00:11:32.58 +61:13:57.0 -- not an asteroid (will add it to exclusion list)
00:11:14.87 +64:53:33.2 -- not an asteroid (will add it to exclusion list)
00:16:47.48 +64:42:54.8 -- not an asteroid (will add it to exclusion list)
00:23:11.84 +63:49:18.6 -- not an asteroid (will add it to exclusion list)
23:57:03.44 +61:22:15.0 -- not an asteroid (will add it to exclusion list)
23:25:18.81 +57:37:12.2 -- not an asteroid (will add it to exclusion list)
23:31:56.96 +65:42:21.6 -- not an asteroid (will add it to exclusion list)
23:25:05.21 +64:43:23.9 -- not an asteroid (will add it to exclusion list)
00:03:10.72 +64:44:02.1 -- not an asteroid (will add it to exclusion list)
00:04:36.75 +60:35:02.5 -- not an asteroid (will add it to exclusion list)
23:55:57.21 +64:02:12.2 -- not an asteroid (will add it to exclusion list)
00:02:52.95 +62:04:53.3 -- not an asteroid (will add it to exclusion list)
00:23:25.11 +61:50:19.2 -- not an asteroid (will add it to exclusion list)
00:23:13.57 +62:26:43.2 -- not an asteroid (will add it to exclusion list)
00:20:43.12 +62:52:57.2 -- not an asteroid (will add it to exclusion list)
00:34:22.09 +60:00:43.8 -- not an asteroid (will add it to exclusion list)
00:06:56.79 +62:32:10.1 -- not an asteroid (will add it to exclusion list)
00:13:25.13 +63:15:27.0 -- not an asteroid (will add it to exclusion list)
23:41:35.07 +59:35:28.8 -- not an asteroid (will add it to exclusion list)
00:20:21.88 +60:15:51.5 -- not an asteroid (will add it to exclusion list)
00:03:35.60 +63:34:46.8 -- not an asteroid (will add it to exclusion list)
23:22:21.62 +62:39:45.7 -- not an asteroid (will add it to exclusion list)
00:16:14.03 +60:59:38.4 -- not an asteroid (will add it to exclusion list)
00:21:26.52 +59:13:56.8 -- not an asteroid (will add it to exclusion list)
00:16:40.71 +65:59:41.4 -- not an asteroid (will add it to exclusion list)
00:35:16.36 +63:00:43.9 -- not an asteroid (will add it to exclusion list)
00:21:57.21 +61:46:06.0 -- not an asteroid (will add it to exclusion list)
00:15:12.25 +58:24:53.0 -- not an asteroid (will add it to exclusion list)
00:30:23.76 +60:12:41.2 -- not an asteroid (will add it to exclusion list)
23:52:13.37 +65:38:33.0 -- not an asteroid (will add it to exclusion list)
00:10:26.28 +60:01:06.0 -- not an asteroid (will add it to exclusion list)
00:10:45.95 +63:25:28.6 -- not an asteroid (will add it to exclusion list)
00:00:30.32 +65:48:24.4 -- not an asteroid (will add it to exclusion list)
00:21:47.83 +61:02:51.6 -- not an asteroid (will add it to exclusion list)
00:35:29.49 +61:53:07.8 -- not an asteroid (will add it to exclusion list)
00:40:45.95 +64:16:35.6 -- not an asteroid (will add it to exclusion list)
00:15:43.58 +59:34:01.8 -- not an asteroid (will add it to exclusion list)
00:15:02.92 +61:26:04.5 -- not an asteroid (will add it to exclusion list)
00:07:46.77 +61:54:28.1 -- not an asteroid (will add it to exclusion list)
00:12:36.08 +62:53:08.1 -- not an asteroid (will add it to exclusion list)
00:23:45.40 +59:32:00.7 -- not an asteroid (will add it to exclusion list)
00:23:31.68 +65:19:46.1 -- not an asteroid (will add it to exclusion list)
00:00:34.43 +62:49:36.3 -- not an asteroid (will add it to exclusion list)
23:23:48.81 +65:45:07.0 -- not an asteroid (will add it to exclusion list)
00:01:10.87 +64:55:36.9 -- not an asteroid (will add it to exclusion list)
00:03:30.11 +58:28:54.0 -- not an asteroid (will add it to exclusion list)
00:01:55.45 +63:10:47.0 -- not an asteroid (will add it to exclusion list)
00:02:05.62 +63:18:19.2 -- not an asteroid (will add it to exclusion list)
23:59:26.60 +63:49:12.2 -- not an asteroid (will add it to exclusion list)
00:13:51.00 +59:58:37.1 -- not an asteroid (will add it to exclusion list)
23:24:19.46 +64:02:47.3 -- not an asteroid (will add it to exclusion list)
00:09:16.33 +59:38:42.3 -- not an asteroid (will add it to exclusion list)
00:07:57.70 +63:21:39.1 -- not an asteroid (will add it to exclusion list)
00:30:05.13 +60:13:25.0 -- not an asteroid (will add it to exclusion list)
00:09:21.55 +61:47:56.5 -- not an asteroid (will add it to exclusion list)
23:57:00.59 +63:29:18.0 -- not an asteroid (will add it to exclusion list)
00:07:53.22 +57:56:32.6 -- not an asteroid (will add it to exclusion list)
00:17:57.20 +59:09:21.0 -- not an asteroid (will add it to exclusion list)
00:05:34.26 +62:32:06.0 -- not an asteroid (will add it to exclusion list)
00:03:11.57 +62:20:26.2 -- not an asteroid (will add it to exclusion list)
00:31:00.50 +61:24:59.0 -- not an asteroid (will add it to exclusion list)
00:09:06.05 +58:45:35.0 -- not an asteroid (will add it to exclusion list)
00:23:13.48 +60:17:38.6 -- not an asteroid (will add it to exclusion list)
00:19:25.32 +59:23:44.7 -- not an asteroid (will add it to exclusion list)
00:22:22.70 +59:28:18.3 -- not an asteroid (will add it to exclusion list)
23:47:42.13 +60:42:41.8 -- not an asteroid (will add it to exclusion list)
00:07:11.59 +57:51:19.1 -- not an asteroid (will add it to exclusion list)
00:28:07.61 +63:12:32.1 -- not an asteroid (will add it to exclusion list)
00:16:23.24 +61:54:20.2 -- not an asteroid (will add it to exclusion list)
00:12:20.24 +60:34:40.1 -- not an asteroid (will add it to exclusion list)
23:23:46.63 +58:23:54.3 -- not an asteroid (will add it to exclusion list)
00:11:48.21 +61:45:41.6 -- not an asteroid (will add it to exclusion list)
00:18:23.17 +58:05:04.5 -- not an asteroid (will add it to exclusion list)
23:24:56.01 +63:49:19.9 -- not an asteroid (will add it to exclusion list)
00:32:48.60 +63:15:27.0 -- not an asteroid (will add it to exclusion list)
00:19:14.18 +63:35:38.4 -- not an asteroid (will add it to exclusion list)
00:41:32.04 +65:49:07.4 -- not an asteroid (will add it to exclusion list)
00:07:03.07 +57:49:55.7 -- not an asteroid (will add it to exclusion list)
23:52:22.47 +65:38:11.6 -- not an asteroid (will add it to exclusion list)
00:05:12.19 +60:11:01.0 -- not an asteroid (will add it to exclusion list)
00:19:14.22 +63:34:52.2 -- not an asteroid (will add it to exclusion list)
00:00:08.90 +62:26:20.2 -- not an asteroid (will add it to exclusion list)
00:08:01.59 +60:10:45.0 -- not an asteroid (will add it to exclusion list)
23:42:11.64 +58:56:31.7 -- not an asteroid (will add it to exclusion list)
23:25:42.11 +59:45:26.6 -- not an asteroid (will add it to exclusion list)
23:33:19.80 +64:36:26.4 -- not an asteroid (will add it to exclusion list)
00:05:24.83 +57:58:26.9 -- not an asteroid (will add it to exclusion list)
00:17:24.69 +57:53:58.0 -- not an asteroid (will add it to exclusion list)
00:01:45.01 +60:05:35.4 -- not an asteroid (will add it to exclusion list)
23:27:39.45 +59:32:06.7 -- not an asteroid (will add it to exclusion list)
00:06:54.65 +63:35:56.0 -- not an asteroid (will add it to exclusion list)
00:23:27.65 +63:43:17.2 -- not an asteroid (will add it to exclusion list)
23:49:38.25 +61:05:21.3 -- not an asteroid (will add it to exclusion list)
00:15:13.00 +58:24:17.6 -- not an asteroid (will add it to exclusion list)
00:05:23.38 +63:17:40.0 -- not an asteroid (will add it to exclusion list)
00:16:54.20 +61:35:20.9 -- not an asteroid (will add it to exclusion list)
23:26:00.02 +64:22:29.1 -- not an asteroid (will add it to exclusion list)
00:36:10.66 +62:54:05.7 -- not an asteroid (will add it to exclusion list)
00:16:51.50 +60:16:09.8 -- not an asteroid (will add it to exclusion list)
00:15:55.27 +60:47:49.1 -- not an asteroid (will add it to exclusion list)
23:23:22.99 +63:17:59.9 -- not an asteroid (will add it to exclusion list)
23:24:53.86 +65:29:15.0 -- not an asteroid (will add it to exclusion list)
00:16:04.88 +58:06:35.8 -- not an asteroid (will add it to exclusion list)
00:08:02.17 +58:55:55.2 -- not an asteroid (will add it to exclusion list)
23:30:14.31 +59:03:26.7 -- not an asteroid (will add it to exclusion list)
23:26:18.02 +57:28:13.5 -- not an asteroid (will add it to exclusion list)
00:03:38.27 +60:59:26.0 -- not an asteroid (will add it to exclusion list)
23:48:28.53 +60:08:08.0 -- not an asteroid (will add it to exclusion list)
23:23:44.21 +58:37:42.3 -- not an asteroid (will add it to exclusion list)
00:10:34.05 +64:29:07.2 -- not an asteroid (will add it to exclusion list)
00:00:57.37 +59:27:05.5 -- not an asteroid (will add it to exclusion list)
00:07:32.23 +62:23:56.2 -- not an asteroid (will add it to exclusion list)
00:41:03.48 +65:48:56.9 -- not an asteroid (will add it to exclusion list)
23:35:28.05 +65:23:02.0 -- not an asteroid (will add it to exclusion list)
23:48:55.65 +64:22:26.8 -- not an asteroid (will add it to exclusion list)
23:39:12.94 +57:49:42.3 -- not an asteroid (will add it to exclusion list)
23:22:26.56 +64:30:36.2 -- not an asteroid (will add it to exclusion list)
00:09:06.21 +65:47:19.6 -- not an asteroid (will add it to exclusion list)
23:24:39.02 +59:02:46.5 -- not an asteroid (will add it to exclusion list)
00:29:28.08 +60:49:54.1 -- not an asteroid (will add it to exclusion list)
00:07:41.01 +64:42:26.4 -- not an asteroid (will add it to exclusion list)
23:58:37.40 +58:25:46.6 -- not an asteroid (will add it to exclusion list)
23:29:38.28 +64:59:14.5 -- not an asteroid (will add it to exclusion list)
00:07:06.08 +61:48:59.0 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:08.90 +62:26:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:30.32 +65:48:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:34.43 +62:49:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:57.37 +59:27:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:10.87 +64:55:36.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:45.01 +60:05:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:55.45 +63:10:47.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:05.62 +63:18:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:52.95 +62:04:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:10.72 +64:44:02.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:11.57 +62:20:26.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:30.11 +58:28:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:35.60 +63:34:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:38.27 +60:59:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:36.75 +60:35:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:12.19 +60:11:01.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:23.38 +63:17:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:24.83 +57:58:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:34.26 +62:32:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:54.65 +63:35:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:56.79 +62:32:10.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:03.07 +57:49:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:06.08 +61:48:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:11.59 +57:51:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:32.23 +62:23:56.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:41.01 +64:42:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:46.77 +61:54:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:53.22 +57:56:32.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:57.70 +63:21:39.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:01.59 +60:10:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:02.17 +58:55:55.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:06.05 +58:45:35.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:06.21 +65:47:19.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:16.33 +59:38:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:21.55 +61:47:56.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:26.28 +60:01:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:34.05 +64:29:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:45.95 +63:25:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:14.87 +64:53:33.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:32.58 +61:13:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:48.21 +61:45:41.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:20.24 +60:34:40.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:36.08 +62:53:08.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:25.13 +63:15:27.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:51.00 +59:58:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:02.92 +61:26:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:12.25 +58:24:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:13.00 +58:24:17.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:28.13 +61:28:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:43.58 +59:34:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:55.27 +60:47:49.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:04.88 +58:06:35.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:14.03 +60:59:38.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:23.24 +61:54:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:40.71 +65:59:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:47.48 +64:42:54.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:51.50 +60:16:09.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:54.20 +61:35:20.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:18.73 +61:39:29.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:24.69 +57:53:58.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:57.20 +59:09:21.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:23.17 +58:05:04.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:14.18 +63:35:38.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:14.22 +63:34:52.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:25.32 +59:23:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:21.88 +60:15:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:43.12 +62:52:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:26.52 +59:13:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:47.83 +61:02:51.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:21:57.21 +61:46:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:22.70 +59:28:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:11.84 +63:49:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:13.48 +60:17:38.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:13.57 +62:26:43.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:25.11 +61:50:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:27.65 +63:43:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:31.68 +65:19:46.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:45.40 +59:32:00.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:28:07.61 +63:12:32.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:28.08 +60:49:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:05.13 +60:13:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:30:23.76 +60:12:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:31:00.50 +61:24:59.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:32:48.60 +63:15:27.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:22.09 +60:00:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:34:23.05 +64:31:55.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:16.36 +63:00:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:35:29.49 +61:53:07.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:36:10.66 +62:54:05.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:40:45.95 +64:16:35.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:03.48 +65:48:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:41:32.04 +65:49:07.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:21.62 +62:39:45.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:22:26.56 +64:30:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:22.99 +63:17:59.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:44.21 +58:37:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:46.63 +58:23:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:23:48.81 +65:45:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:19.46 +64:02:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:39.02 +59:02:46.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:53.86 +65:29:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:24:56.01 +63:49:19.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:05.21 +64:43:23.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:18.81 +57:37:12.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:25:42.11 +59:45:26.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:00.02 +64:22:29.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:26:18.02 +57:28:13.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:27:39.45 +59:32:06.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:38.28 +64:59:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:14.31 +59:03:26.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:56.96 +65:42:21.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:19.80 +64:36:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:28.05 +65:23:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:12.94 +57:49:42.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:35.07 +59:35:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:11.64 +58:56:31.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:42.13 +60:42:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:28.53 +60:08:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:55.65 +64:22:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:38.25 +61:05:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:13.37 +65:38:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:22.47 +65:38:11.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:25.66 +64:08:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:57.21 +64:02:12.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:00.59 +63:29:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:03.44 +61:22:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:37.40 +58:25:46.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:59:26.60 +63:49:12.2 -- does not seem to be a hot pixel (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_nohotpixels' -> 'exclusion_list_index_html.txt'
# Count candidates with no identification (that also don't look like hot pix)
00:00:08.90 +62:26:20.2 -- a known variable star
00:00:30.32 +65:48:24.4 -- not a known variable star
00:00:34.43 +62:49:36.3 -- not a known variable star
00:00:57.37 +59:27:05.5 -- a known variable star
00:01:10.87 +64:55:36.9 -- not a known variable star
00:01:45.01 +60:05:35.4 -- not a known variable star
00:01:55.45 +63:10:47.0 -- a known variable star
00:02:05.62 +63:18:19.2 -- not a known variable star
00:02:52.95 +62:04:53.3 -- not a known variable star
00:03:10.72 +64:44:02.1 -- not a known variable star
00:03:11.57 +62:20:26.2 -- not a known variable star
00:03:30.11 +58:28:54.0 -- not a known variable star
00:03:35.60 +63:34:46.8 -- a known variable star
00:03:38.27 +60:59:26.0 -- not a known variable star
00:04:36.75 +60:35:02.5 -- not a known variable star
00:05:12.19 +60:11:01.0 -- not a known variable star
00:05:23.38 +63:17:40.0 -- not a known variable star
00:05:24.83 +57:58:26.9 -- not a known variable star
00:05:34.26 +62:32:06.0 -- not a known variable star
00:06:54.65 +63:35:56.0 -- not a known variable star
00:06:56.79 +62:32:10.1 -- not a known variable star
00:07:03.07 +57:49:55.7 -- not a known variable star
00:07:06.08 +61:48:59.0 -- a known variable star
00:07:11.59 +57:51:19.1 -- not a known variable star
00:07:32.23 +62:23:56.2 -- not a known variable star
00:07:41.01 +64:42:26.4 -- not a known variable star
00:07:46.77 +61:54:28.1 -- not a known variable star
00:07:53.22 +57:56:32.6 -- not a known variable star
00:07:57.70 +63:21:39.1 -- not a known variable star
00:08:01.59 +60:10:45.0 -- a known variable star
00:08:02.17 +58:55:55.2 -- not a known variable star
00:09:06.05 +58:45:35.0 -- not a known variable star
00:09:06.21 +65:47:19.6 -- not a known variable star
00:09:16.33 +59:38:42.3 -- not a known variable star
00:09:21.55 +61:47:56.5 -- not a known variable star
00:10:26.28 +60:01:06.0 -- not a known variable star
00:10:34.05 +64:29:07.2 -- not a known variable star
00:10:45.95 +63:25:28.6 -- not a known variable star
00:11:14.87 +64:53:33.2 -- not a known variable star
00:11:32.58 +61:13:57.0 -- not a known variable star
00:11:48.21 +61:45:41.6 -- not a known variable star
00:12:20.24 +60:34:40.1 -- a known variable star
00:12:36.08 +62:53:08.1 -- not a known variable star
00:13:25.13 +63:15:27.0 -- not a known variable star
00:13:51.00 +59:58:37.1 -- not a known variable star
00:15:02.92 +61:26:04.5 -- not a known variable star
00:15:12.25 +58:24:53.0 -- a known variable star
00:15:13.00 +58:24:17.6 -- not a known variable star
00:15:28.13 +61:28:18.7 -- not a known variable star
00:15:43.58 +59:34:01.8 -- not a known variable star
00:15:55.27 +60:47:49.1 -- not a known variable star
00:16:04.88 +58:06:35.8 -- a known variable star
00:16:14.03 +60:59:38.4 -- not a known variable star
00:16:23.24 +61:54:20.2 -- a known variable star
00:16:40.71 +65:59:41.4 -- not a known variable star
00:16:47.48 +64:42:54.8 -- not a known variable star
00:16:51.50 +60:16:09.8 -- not a known variable star
00:16:54.20 +61:35:20.9 -- not a known variable star
00:17:18.73 +61:39:29.8 -- not a known variable star
00:17:24.69 +57:53:58.0 -- not a known variable star
00:17:57.20 +59:09:21.0 -- a known variable star
00:18:23.17 +58:05:04.5 -- not a known variable star
00:19:14.18 +63:35:38.4 -- not a known variable star
00:19:14.22 +63:34:52.2 -- not a known variable star
00:19:25.32 +59:23:44.7 -- not a known variable star
00:20:21.88 +60:15:51.5 -- not a known variable star
00:20:43.12 +62:52:57.2 -- not a known variable star
00:21:26.52 +59:13:56.8 -- a known variable star
00:21:47.83 +61:02:51.6 -- not a known variable star
00:21:57.21 +61:46:06.0 -- a known variable star
00:22:22.70 +59:28:18.3 -- not a known variable star
00:23:11.84 +63:49:18.6 -- not a known variable star
00:23:13.48 +60:17:38.6 -- a known variable star
00:23:13.57 +62:26:43.2 -- not a known variable star
00:23:25.11 +61:50:19.2 -- a known variable star
00:23:27.65 +63:43:17.2 -- a known variable star
00:23:31.68 +65:19:46.1 -- not a known variable star
00:23:45.40 +59:32:00.7 -- a known variable star
00:28:07.61 +63:12:32.1 -- not a known variable star
00:29:28.08 +60:49:54.1 -- a known variable star
00:30:05.13 +60:13:25.0 -- not a known variable star
00:30:23.76 +60:12:41.2 -- not a known variable star
00:31:00.50 +61:24:59.0 -- not a known variable star
00:32:48.60 +63:15:27.0 -- not a known variable star
00:34:22.09 +60:00:43.8 -- not a known variable star
00:34:23.05 +64:31:55.3 -- not a known variable star
00:35:16.36 +63:00:43.9 -- not a known variable star
00:35:29.49 +61:53:07.8 -- not a known variable star
00:36:10.66 +62:54:05.7 -- not a known variable star
00:40:45.95 +64:16:35.6 -- not a known variable star
00:41:03.48 +65:48:56.9 -- not a known variable star
00:41:32.04 +65:49:07.4 -- not a known variable star
23:22:21.62 +62:39:45.7 -- not a known variable star
23:22:26.56 +64:30:36.2 -- not a known variable star
23:23:22.99 +63:17:59.9 -- not a known variable star
23:23:44.21 +58:37:42.3 -- not a known variable star
23:23:46.63 +58:23:54.3 -- not a known variable star
23:23:48.81 +65:45:07.0 -- not a known variable star
23:24:19.46 +64:02:47.3 -- not a known variable star
23:24:39.02 +59:02:46.5 -- not a known variable star
23:24:53.86 +65:29:15.0 -- not a known variable star
23:24:56.01 +63:49:19.9 -- not a known variable star
23:25:05.21 +64:43:23.9 -- not a known variable star
23:25:18.81 +57:37:12.2 -- not a known variable star
23:25:42.11 +59:45:26.6 -- not a known variable star
23:26:00.02 +64:22:29.1 -- a known variable star
23:26:18.02 +57:28:13.5 -- not a known variable star
23:27:39.45 +59:32:06.7 -- not a known variable star
23:29:38.28 +64:59:14.5 -- not a known variable star
23:30:14.31 +59:03:26.7 -- not a known variable star
23:31:56.96 +65:42:21.6 -- not a known variable star
23:33:19.80 +64:36:26.4 -- not a known variable star
23:35:28.05 +65:23:02.0 -- not a known variable star
23:39:12.94 +57:49:42.3 -- not a known variable star
23:41:35.07 +59:35:28.8 -- a known variable star
23:42:11.64 +58:56:31.7 -- a known variable star
23:47:42.13 +60:42:41.8 -- a known variable star
23:48:28.53 +60:08:08.0 -- not a known variable star
23:48:55.65 +64:22:26.8 -- not a known variable star
23:49:38.25 +61:05:21.3 -- a known variable star
23:52:13.37 +65:38:33.0 -- not a known variable star
23:52:22.47 +65:38:11.6 -- not a known variable star
23:55:25.66 +64:08:38.7 -- not a known variable star
23:55:57.21 +64:02:12.2 -- not a known variable star
23:57:00.59 +63:29:18.0 -- not a known variable star
23:57:03.44 +61:22:15.0 -- not a known variable star
23:58:37.40 +58:25:46.6 -- a known variable star
23:59:26.60 +63:49:12.2 -- not a known variable star
Found 104 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
128 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 128 (excluding asteroids and hot pixels, 104 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)2461208.91997828 -observatory V36
07:28:20.68 +22:37:10.1 Mercury (0.7mag)
08:28:20.61 +21:09:28.8 Venus (-4.0mag)
03:16:31.98 +17:40:38.4 Mars (1.3mag)
07:56:16.33 +21:11:04.4 Jupiter (-1.8mag)
00:51:47.90 +03:01:35.8 Saturn (0.8mag)
04:02:21.98 +20:31:36.8 Uranus (5.8mag)
00:16:36.21 +00:19:16.7 Neptune (7.8mag)
20:32:47.00 -23:08:09.7 Pluto (14.5mag)
08:05:10.26 +22:22:53.0 Moon (-8.9mag)
-rw-r--r-- 1 apache apache 361 Jun 17 05:29 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461208.91997828:
07:56:23.99 +21:10:41.0 Io (6.2mag)
07:56:12.27 +21:11:16.7 Europa (6.3mag)
07:56:19.64 +21:10:59.3 Ganymede (5.6mag)
07:56:09.22 +21:11:33.2 Callisto (6.9mag)
07:56:00.84 +20:48:28.6 Himalia (15.6mag)
07:56:15.77 +21:11:07.6 Thebe (16.5mag)
07:55:45.07 +21:00:02.8 Elara (17.6mag)
07:58:54.33 +21:17:43.7 Pasiphae (17.8mag)
08:02:26.11 +21:13:32.3 Carme (18.9mag)
00:51:54.87 +03:01:55.8 Titan (8.6mag)
00:51:43.83 +03:01:46.3 Rhea (9.9mag)
00:52:08.19 +03:04:07.1 Iapetus (11.3mag)
00:52:01.35 +03:01:44.1 Hyperion (14.6mag)
00:52:18.64 +03:02:11.9 Phoebe (16.7mag)
-rw-r--r-- 1 apache apache 568 Jun 17 05:29 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461208.91997828:
17:27:32.94 -35:35:19.3 JWST
17:59:21.56 +31:33:18.7 Chandra
10:03:43.71 -56:42:07.3 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jun 17 05:29 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461208.91997828 -observatory V36
18:36:39.42 -33:17:13.3 13.6mag P/2010 H2 (Vales)
06:02:37.88 -68:00:02.4 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
05:52:28.50 +32:05:34.4 17.5mag C/2017 K2 (PANSTARRS)
17:11:03.69 +15:44:16.7 17.8mag C/2021 G2 (ATLAS)
22:43:26.14 -40:52:53.0 16.1mag P/2021 N1 (ZTF)
23:10:06.89 +31:54:39.6 17.2mag C/2022 E2 (ATLAS)
05:45:18.06 +27:00:35.4 16.5mag C/2022 N2 (PANSTARRS)
09:36:36.61 +30:44:35.1 16.7mag C/2022 QE78 (ATLAS)
08:55:40.58 +04:20:01.1 17.7mag C/2022 R6 (PANSTARRS)
18:22:07.45 +21:42:12.4 17.8mag C/2023 A3 (Tsuchinshan-ATLAS)
15:16:19.14 -11:02:52.8 17.6mag P/2023 B1 (PANSTARRS)
22:10:10.38 +67:02:35.8 17.8mag C/2023 H5 (Lemmon)
17:23:24.92 -07:37:39.3 13.7mag C/2023 R1 (PANSTARRS)
13:16:52.51 +80:50:28.4 18.0mag C/2023 X2 (Lemmon)
07:23:42.32 +64:38:42.0 17.8mag C/2024 A1 (ATLAS)
07:01:01.02 +28:35:29.3 14.0mag C/2024 E1 (Wierzchos)
15:30:19.74 +14:14:53.5 17.4mag C/2024 G6 (ATLAS)
20:06:02.49 +33:48:36.6 13.9mag C/2024 J3 (ATLAS)
04:27:15.63 -15:11:42.7 15.9mag C/2024 T5 (ATLAS)
06:14:26.99 +32:54:25.5 17.9mag C/2025 J1 (Borisov)
11:32:14.43 +52:11:22.7 17.7mag C/2025 L1 (ATLAS)
06:55:08.10 -11:18:50.9 14.9mag C/2025 R3 (PANSTARRS)
09:32:11.79 +23:10:41.4 17.9mag C/2025 V2 (Rankin)
12:39:56.31 +04:36:19.6 17.1mag C/2025 Y1 (ATLAS)
17:55:14.02 +76:54:58.5 17.7mag C/2026 A2 (Bok)
02:15:54.94 +44:01:55.4 16.3mag C/2026 B2 (Sun-Gao)
11:13:55.04 -00:45:46.8 16.6mag A/2026 E1
20:40:12.97 -09:31:05.2 8.2mag 10P/Tempel
11:04:30.45 -01:08:16.3 16.0mag 29P/Schwassmann-Wachmann
03:25:56.03 +26:50:56.3 17.7mag 47P/Ashbrook-Jackson
09:19:39.14 +21:04:56.5 16.9mag 63P/Wild
00:34:24.30 -05:50:02.6 15.6mag 65P/Gunn
07:13:26.01 +34:09:08.3 17.2mag 76P/West-Kohoutek-Ikemura
03:31:34.07 +18:18:29.4 13.8mag 78P/Gehrels
01:40:10.19 +06:45:31.3 15.8mag 88P/Howell
05:24:16.69 +30:48:51.1 15.4mag 93P/Lovas
03:09:39.81 +28:59:36.0 17.4mag 114P/Wiseman-Skiff
07:12:43.74 +32:36:38.6 15.5mag 123P/West-Hartley
10:06:24.24 +10:42:38.0 16.6mag 124P/Mrkos
04:14:15.90 +19:49:17.1 16.3mag 128P/Shoemaker-Holt
04:51:51.20 +19:26:21.4 17.8mag 131P/Mueller
06:36:08.57 +17:24:37.8 15.8mag 141P/Machholz
06:39:26.37 +17:54:06.6 15.8mag 141P-A/Machholz
05:39:14.27 +17:07:12.4 12.6mag 141P-D/Machholz
03:03:59.37 -23:29:23.4 16.5mag 161P/Hartley-IRAS
04:12:24.54 +27:18:27.9 15.0mag 162P/SidingSpring
19:34:10.14 +04:40:28.5 16.3mag 169P/NEAT
00:42:57.30 +04:11:45.9 17.8mag 220P/McNaught
16:45:33.82 -08:09:00.7 16.5mag 235P/LINEAR
07:55:23.63 +35:01:55.6 17.6mag 240P/NEAT
00:56:44.68 +01:32:34.1 16.2mag 260P/McNaught
04:29:48.25 +34:03:04.8 17.5mag 295P/LINEAR
00:42:30.61 +00:38:19.8 17.8mag 320P/McNaught
15:11:29.76 +07:41:57.6 17.5mag 391P/Kowalski
08:14:39.90 +20:29:20.2 17.9mag 450P/LONEOS
07:15:00.36 +41:01:28.6 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.7K Jun 17 05:29 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 17 05:29 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
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
-rw-r--r-- 1 apache apache 189K Jun 17 05:29 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
10:28:01.958 +34:35:58.69 AT 2026osk 2026-06-08.18 19.2799
12:28:37.599 +41:40:10.18 AT 2026osj 2026-06-02.17 20.1092
10:59:20.450 +40:48:48.90 AT 2026osi 2026-06-02.17 19.8695
10:57:02.077 +24:20:34.59 AT 2026osh 2026-06-03.20 19.8092
14:46:28.312 +01:33:28.69 AT 2026osg 2026-06-05.29 20.5651
15:08:15.449 -04:43:16.48 SN 2026osf 2026-06-06.32 20.375
14:51:30.247 +22:37:57.23 AT 2026ose 2026-06-03.23 20.5827
17:19:28.178 -01:48:39.65 SN 2026osd 2026-06-07.33 20.757
21:42:45.017 +13:53:40.78 SN 2026osc 2026-06-05.13 18.87
10:04:17.793 +10:47:28.54 AT 2026osb 2026-06-08.89 18.473
17:01:33.332 +50:43:50.85 AT 2026osa 2026-06-07.10 20.02
15:52:00.811 +48:12:41.81 AT 2026orz 2026-06-03.97 19.6
16:57:43.679 +55:34:29.61 SN 2026ory 2026-06-09.06 19.74
17:06:48.379 +56:34:34.28 AT 2026orx 2026-06-09.06 19.96
15:50:02.310 +47:40:40.67 AT 2026orw 2026-06-06.100 20.04
15:13:24.305 +58:43:44.69 AT 2026orv 2026-06-05.81 20.34
16:25:01.930 +43:59:23.83 AT 2026oru 2026-06-08.86 20.51
15:54:39.489 +41:09:29.50 AT 2026ort 2026-06-08.88 18.75
16:16:12.071 +25:03:21.02 AT 2026ors 2026-06-08.83 20.53
17:19:04.503 +56:21:42.34 AT 2026orr 2026-06-08.99 19.83
-rw-r--r-- 1 apache apache 30K Jun 17 05:29 tns_transients_list.txt
