This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ
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 23.4400 2461214.9400 10.66 23:54:24.39 +53:21:11.5
114.38246 -8.56921 galactic Cas Second-epoch detections are separated by 7.4" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:54:24.39 +53:21:11.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:24.39 +53:21:11.5: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:24.39 +53:21:11.5: 15.57 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 23 54 24.39 +53 21 11.5 10.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,2461214.9400,10.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 20260623.4400 10.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 23.4400 2461214.9400 11.14 00:22:45.50 +53:12:12.4
118.58573 -9.42611 galactic Cas Second-epoch detections are separated by 1.7" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:22:45.50 +53:12:12.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:45.50 +53:12:12.4: 13.84 +/- 0.06 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:45.50 +53:12:12.4: 13.83 +/- 0.07 detection
Forced photometry reference-image weighted average: 13.83 +/- 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 23.4400* 00 22 45.50 +53 12 12.4 11.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,11.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 11.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 11.24 00:20:44.33 +50:11:40.6
117.91035 -12.37758 galactic Cas Second-epoch detections are separated by 4.7" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:20:44.33 +50:11:40.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:44.33 +50:11:40.6: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:44.33 +50:11:40.6: 15.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 00 20 44.33 +50 11 40.6 11.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,11.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 20260623.4400 11.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 23.4400 2461214.9400 7.95 23:58:26.59 +51:26:22.2
114.57598 -10.57041 galactic Cas Second-epoch detections are separated by 4.3" and 3.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:58:26.59 +51:26:22.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:26.59 +51:26:22.2: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:26.59 +51:26:22.2: 15.33 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.33 +/- 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 23.4400* 23 58 26.59 +51 26 22.2 8.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,2461214.9400,7.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 7.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 14.15 00:12:13.17 +52:49:02.5
116.94069 -9.59757 galactic Cas Second-epoch detections are separated by 6.3" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.0533+52.8220 | 00:12:13.17 +52:49:02.5 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:13.17 +52:49:02.5: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:13.17 +52:49:02.5: 15.81 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 12 13.17 +52 49 02.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
ATO J003.0533+52.8220,2461214.9400,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
ATO J003.0533+52.8220 20260623.4400 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 23.4400 2461214.9400 13.98 23:51:17.15 +52:36:29.9
113.74781 -9.18751 galactic Cas Second-epoch detections are separated by 5.5" and 2.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:51:17.15 +52:36:29.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:51:17.15 +52:36:29.9: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:17.15 +52:36:29.9: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 51 17.15 +52 36 29.9 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 14.08 00:25:48.32 +54:30:11.3
119.17786 -8.18167 galactic Cas Second-epoch detections are separated by 8.1" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:25:48.32 +54:30:11.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:25:48.32 +54:30:11.3: 15.31 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:25:48.32 +54:30:11.3: 15.28 +/- 0.21 detection
Forced photometry reference-image weighted average: 15.29 +/- 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 23.4400* 00 25 48.32 +54 30 11.3 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,14.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 14.08CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.88 23:39:00.92 +51:32:11.8
111.62122 -9.73763 galactic Cas Second-epoch detections are separated by 7.3" and 3.0 pix
The object was found in VSX23" Gaia DR3 1944776554733485696
Type: RS
# Max. Min./Amp. JD0 Period
15.860 G 15.960 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:39:00.92 +51:32:11.8: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:39:00.92 +51:32:11.8: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 39 00.92 +51 32 11.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1944776554733485696,2461214.9400,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1944776554733485696 20260623.4400 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.88 23:36:40.03 +52:50:54.2
111.64973 -8.37769 galactic Cas Second-epoch detections are separated by 5.2" and 3.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:36:40.03 +52:50:54.2 (user input) | T | P | (position from user input) J-Ks=0.684+/-0.238 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:36:40.03 +52:50:54.2: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:36:40.03 +52:50:54.2: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 36 40.03 +52 50 54.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.85 00:27:57.77 +52:56:17.6
119.34683 -9.77004 galactic Cas Second-epoch detections are separated by 8.0" and 3.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:27:57.77 +52:56:17.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:27:57.77 +52:56:17.6: 15.60 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:27:57.77 +52:56:17.6: 15.52 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 00 27 57.77 +52 56 17.6 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.69 23:52:26.37 +51:58:00.1
113.77092 -9.85254 galactic Cas Second-epoch detections are separated by 6.0" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:26.37 +51:58:00.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:26.37 +51:58:00.1: 15.97 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:26.37 +51:58:00.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 23.4400* 23 52 26.37 +51 58 00.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,2461214.9400,13.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.69CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.73 00:15:30.65 +52:00:09.6
117.32281 -10.47737 galactic Cas Second-epoch detections are separated by 8.8" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:15:30.65 +52:00:09.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:15:30.65 +52:00:09.6: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:15:30.65 +52:00:09.6: 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 23.4400* 00 15 30.65 +52 00 09.6 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.80 23:44:02.82 +52:45:15.7
112.70823 -8.77448 galactic Cas Second-epoch detections are separated by 6.6" and 2.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 J356.0324+52.7552 | 23:44:02.82 +52:45:15.7 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:44:02.82 +52:45:15.7: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:44:02.82 +52:45:15.7: 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 23.4400* 23 44 02.82 +52 45 15.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.0324+52.7552,2461214.9400,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J356.0324+52.7552 20260623.4400 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.65 23:34:47.78 +49:57:41.5
110.50872 -11.05246 galactic And Second-epoch detections are separated by 4.3" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:34:47.78 +49:57:41.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:34:47.78 +49:57:41.5: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:34:47.78 +49:57:41.5: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 34 47.78 +49 57 41.5 13.7 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.67 00:04:32.26 +52:54:14.9
115.79689 -9.31665 galactic Cas Second-epoch detections are separated by 3.4" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J001.1222+52.9025 | 00:04:32.26 +52:54:14.9 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:32.26 +52:54:14.9: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:32.26 +52:54:14.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 23.4400* 00 04 32.26 +52 54 14.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
ATO J001.1222+52.9025,2461214.9400,13.67,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.1222+52.9025 20260623.4400 13.67CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.62 23:54:00.86 +53:15:51.5
114.30470 -8.64284 galactic Cas Second-epoch detections are separated by 3.1" and 2.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:54:00.86 +53:15:51.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:00.86 +53:15:51.5: 15.93 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:00.86 +53:15:51.5: 15.83 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 54 00.86 +53 15 51.5 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 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 23.4400 2461214.9400 13.65 23:35:22.75 +56:30:59.1
112.53973 -4.81292 galactic Cas Second-epoch detections are separated by 5.4" and 2.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:35:22.75 +56:30:59.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:35:22.75 +56:30:59.1: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:35:22.75 +56:30:59.1: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 35 22.75 +56 30 59.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,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.33 23:29:21.38 +56:41:00.5
111.79762 -4.40338 galactic Cas Second-epoch detections are separated by 6.3" and 2.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:21.38 +56:41:00.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:29:21.38 +56:41:00.5: 15.55 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:29:21.38 +56:41:00.5: 15.50 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 23 29 21.38 +56 41 00.5 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.32 00:04:18.78 +51:51:28.6
115.56733 -10.33868 galactic Cas Second-epoch detections are separated by 3.3" and 2.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:04:18.78 +51:51:28.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:18.78 +51:51:28.6: 15.79 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:18.78 +51:51:28.6: 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 23.4400* 00 04 18.78 +51 51 28.6 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.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 20260623.4400 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.52 00:22:04.39 +54:21:20.5
118.61662 -8.26983 galactic Cas Second-epoch detections are separated by 8.2" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 419726301779641216 | 00:22:07.02 +54:21:09.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:04.39 +54:21:20.5: 15.57 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:04.39 +54:21:20.5: 15.07 +/- 0.17 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 23.4400* 00 22 04.39 +54 21 20.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 419726301779641216,2461214.9400,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 419726301779641216 20260623.4400 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 23.4400 2461214.9400 13.28 23:54:28.93 +54:05:57.2
114.56031 -7.84416 galactic Cas Second-epoch detections are separated by 3.1" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1993577588059112704 | 23:54:28.90 +54:05:37.0 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:28.93 +54:05:57.2: 14.67 +/- 0.13 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:28.93 +54:05:57.2: 14.67 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.67 +/- 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 23.4400* 23 54 28.93 +54 05 57.2 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993577588059112704,2461214.9400,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993577588059112704 20260623.4400 13.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.11 23:55:09.34 +53:04:27.6
114.43098 -8.86593 galactic Cas Second-epoch detections are separated by 3.2" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:09.34 +53:04:27.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:09.34 +53:04:27.6: 15.95 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:09.34 +53:04:27.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 23.4400* 23 55 09.34 +53 04 27.6 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.84 23:31:54.42 +51:39:12.2
110.58602 -9.30178 galactic Cas Second-epoch detections are separated by 3.3" and 2.5 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:54.42 +51:39:12.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:31:54.42 +51:39:12.2: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:31:54.42 +51:39:12.2: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 31 54.42 +51 39 12.2 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,12.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 12.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.81 00:10:28.35 +53:34:40.5
116.79982 -8.80538 galactic Cas Second-epoch detections are separated by 4.7" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:10:28.35 +53:34:40.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:10:28.35 +53:34:40.5: 15.61 +/- 0.28 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:10:28.35 +53:34:40.5: 15.44 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.51 +/- 0.18
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 10 28.35 +53 34 40.5 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,12.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 12.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.55 23:29:17.55 +55:18:44.9
111.35786 -5.70255 galactic Cas Second-epoch detections are separated by 3.7" and 2.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 1997633755177085440 | 23:29:16.09 +55:18:13.1 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:29:17.55 +55:18:44.9: 15.13 +/- 0.23 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:29:17.55 +55:18:44.9: 15.02 +/- 0.21 detection
Forced photometry reference-image weighted average: 15.07 +/- 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 23.4400* 23 29 17.55 +55 18 44.9 12.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997633755177085440,2461214.9400,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997633755177085440 20260623.4400 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.46 23:30:30.27 +53:48:13.0
111.05211 -7.19092 galactic Cas Second-epoch detections are separated by 4.1" and 2.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J352.6137+53.8124 | 23:30:30.27 +53:48:13.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:30:30.27 +53:48:13.0: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:30:30.27 +53:48:13.0: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 30 30.27 +53 48 13.0 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.6137+53.8124,2461214.9400,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.6137+53.8124 20260623.4400 12.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.52 00:23:24.72 +54:55:51.3
118.87616 -7.71998 galactic Cas Second-epoch detections are separated by 6.9" and 3.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 419675758603946752 | 00:23:29.13 +54:55:52.6 (Gaia DR3) | DSCT/GDOR (local) | A (local) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:24.72 +54:55:51.3: 15.77 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:24.72 +54:55:51.3: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 23 24.72 +54 55 51.3 12.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 419675758603946752,2461214.9400,12.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 419675758603946752 20260623.4400 12.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 23.4400 2461214.9400 12.04 23:43:36.00 +53:16:05.4
112.77856 -8.26099 galactic Cas Second-epoch detections are separated by 8.2" and 2.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:36.00 +53:16:05.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:36.00 +53:16:05.4: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:36.00 +53:16:05.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 23.4400* 23 43 36.00 +53 16 05.4 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,12.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 20260623.4400 12.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 11.88 00:12:02.04 +54:02:13.5
117.10298 -8.38811 galactic Cas Second-epoch detections are separated by 3.4" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 420123328556205696 | 00:12:05.75 +54:02:01.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:02.04 +54:02:13.5: 13.54 +/- 0.04 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:02.04 +54:02:13.5: 13.50 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.52 +/- 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 23.4400* 00 12 02.04 +54 02 13.5 11.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420123328556205696,2461214.9400,11.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420123328556205696 20260623.4400 11.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 11.81 23:46:43.19 +54:28:54.3
113.54082 -7.20569 galactic Cas Second-epoch detections are separated by 4.8" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1993783609051194496 | 23:46:41.95 +54:28:18.6 (Gaia DR3) | VAR (local) | F (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:46:43.19 +54:28:54.3: 14.74 +/- 0.15 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:46:43.19 +54:28:54.3: 14.75 +/- 0.17 detection
Forced photometry reference-image weighted average: 14.74 +/- 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 23.4400* 23 46 43.19 +54 28 54.3 11.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993783609051194496,2461214.9400,11.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993783609051194496 20260623.4400 11.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.13 00:14:53.87 +53:15:44.1
117.41118 -9.21737 galactic Cas Second-epoch detections are separated by 4.2" and 2.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 419245673457567232 | 00:14:52.39 +53:15:02.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: F5 1927AnHar.100...33C HD 232145
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:14:53.87 +53:15:44.1: 13.63 +/- 0.06 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:53.87 +53:15:44.1: 13.65 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.64 +/- 0.04
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 14 53.87 +53 15 44.1 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
Gaia DR3 419245673457567232,2461214.9400,12.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
Gaia DR3 419245673457567232 20260623.4400 12.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 23.4400 2461214.9400 12.68 00:16:25.15 +53:58:12.8
117.73764 -8.54798 galactic Cas Second-epoch detections are separated by 4.8" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:16:25.15 +53:58:12.8 (user input) | T | P | (position from user input) J-Ks=0.301+/- (F)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:16:25.15 +53:58:12.8: 15.45 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:16:25.15 +53:58:12.8: 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 23.4400* 00 16 25.15 +53 58 12.8 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,12.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 20260623.4400 12.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.98 00:22:44.33 +52:23:06.3
118.48909 -10.23892 galactic Cas Second-epoch detections are separated by 8.6" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J005.6923+52.3782 | 00:22:46.35 +52:22:32.8 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:44.33 +52:23:06.3: 15.28 +/- 0.25 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:44.33 +52:23:06.3: 15.05 +/- 0.20 detection
Forced photometry reference-image weighted average: 15.14 +/- 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 23.4400* 00 22 44.33 +52 23 06.3 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J005.6923+52.3782,2461214.9400,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.6923+52.3782 20260623.4400 12.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 12.99 23:53:28.16 +53:32:37.4
114.28799 -8.35233 galactic Cas Second-epoch detections are separated by 2.5" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:53:28.16 +53:32:37.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:53:28.16 +53:32:37.4: 15.48 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:53:28.16 +53:32:37.4: 15.48 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 23 53 28.16 +53 32 37.4 13.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,12.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 12.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.09 00:23:22.91 +55:49:16.0
118.97014 -6.83467 galactic Cas Second-epoch detections are separated by 3.9" and 3.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 J005.8518+55.8256 | 00:23:22.91 +55:49:16.0 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:22.91 +55:49:16.0: 14.42 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:22.91 +55:49:16.0: 14.57 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.48 +/- 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 23.4400* 00 23 22.91 +55 49 16.0 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J005.8518+55.8256,2461214.9400,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.8518+55.8256 20260623.4400 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.09 23:49:55.72 +53:28:37.1
113.75486 -8.29524 galactic Cas Second-epoch detections are separated by 5.2" and 2.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:49:55.72 +53:28:37.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:49:55.72 +53:28:37.1: 15.51 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:49:55.72 +53:28:37.1: 15.62 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new 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 23.4400* 23 49 55.72 +53 28 37.1 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.18 23:41:19.91 +51:37:00.2
111.99464 -9.76008 galactic Cas Second-epoch detections are separated by 5.3" and 2.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:41:19.91 +51:37:00.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:41:19.91 +51:37:00.2: 15.83 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:19.91 +51:37:00.2: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 41 19.91 +51 37 00.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
target,2461214.9400,13.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.12 00:13:38.26 +52:03:14.7
117.04051 -10.38474 galactic Cas Second-epoch detections are separated by 6.7" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:13:38.26 +52:03:14.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:13:38.26 +52:03:14.7: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:13:38.26 +52:03:14.7: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 13 38.26 +52 03 14.7 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.28 00:24:51.26 +53:02:41.0
118.88522 -9.61803 galactic Cas Second-epoch detections are separated by 8.8" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:24:51.26 +53:02:41.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:24:51.26 +53:02:41.0: 15.66 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:24:51.26 +53:02:41.0: 15.64 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 24 51.26 +53 02 41.0 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.14 23:31:59.77 +55:07:37.1
111.66889 -5.99808 galactic Cas Second-epoch detections are separated by 4.3" and 2.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 1997431032719635200 | 23:32:02.67 +55:07:46.5 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:31:59.77 +55:07:37.1: 15.34 +/- 0.27 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:31:59.77 +55:07:37.1: 14.83 +/- 0.18 detection
Forced photometry reference-image weighted average: 14.98 +/- 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 23.4400* 23 31 59.77 +55 07 37.1 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997431032719635200,2461214.9400,13.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997431032719635200 20260623.4400 13.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.13 23:43:30.48 +50:59:05.1
112.15537 -10.46011 galactic Cas Second-epoch detections are separated by 8.0" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:30.48 +50:59:05.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:30.48 +50:59:05.1: 14.69 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:30.48 +50:59:05.1: 14.79 +/- 0.13 detection
Forced photometry reference-image weighted average: 14.73 +/- 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 23.4400* 23 43 30.48 +50 59 05.1 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.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 20260623.4400 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.28 00:07:37.81 +53:34:10.0
116.37736 -8.74387 galactic Cas Second-epoch detections are separated by 4.3" and 2.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:37.81 +53:34:10.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:07:37.81 +53:34:10.0: 14.50 +/- 0.12 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:07:37.81 +53:34:10.0: 14.59 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.54 +/- 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 23.4400* 00 07 37.81 +53 34 10.0 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.19 23:30:26.62 +57:57:21.1
112.33365 -3.23957 galactic Cas Second-epoch detections are separated by 4.0" and 2.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 J352.6192+57.9493 | 23:30:26.62 +57:57:21.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:30:26.62 +57:57:21.1: 14.37 +/- 0.14 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:30:26.62 +57:57:21.1: 14.39 +/- 0.15 detection
Forced photometry reference-image weighted average: 14.38 +/- 0.10
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 30 26.62 +57 57 21.1 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.6192+57.9493,2461214.9400,13.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.6192+57.9493 20260623.4400 13.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.29 00:12:57.96 +50:00:22.6
116.61984 -12.39338 galactic Cas Second-epoch detections are separated by 6.9" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J003.2549+50.0089 | 00:12:57.96 +50:00:22.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:57.96 +50:00:22.6: 15.92 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:57.96 +50:00:22.6: 15.13 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.13 +/- 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 23.4400* 00 12 57.96 +50 00 22.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
ATO J003.2549+50.0089,2461214.9400,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J003.2549+50.0089 20260623.4400 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 23.4400 2461214.9400 13.30 00:03:31.23 +49:57:58.4
115.08183 -12.17375 galactic Cas Second-epoch detections are separated by 8.2" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:03:31.23 +49:57:58.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:31.23 +49:57:58.4: 15.87 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:31.23 +49:57:58.4: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 03 31.23 +49 57 58.4 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.29 23:56:33.64 +53:45:01.9
114.78549 -8.25097 galactic Cas Second-epoch detections are separated by 3.9" and 3.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 J359.1339+53.7382 | 23:56:33.64 +53:45:01.9 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:56:33.64 +53:45:01.9: 15.63 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:56:33.64 +53:45:01.9: 15.63 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 56 33.64 +53 45 01.9 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J359.1339+53.7382,2461214.9400,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.1339+53.7382 20260623.4400 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 23.4400 2461214.9400 13.31 23:47:35.27 +52:37:29.4
113.20010 -9.03626 galactic Cas Second-epoch detections are separated by 5.2" and 2.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:47:35.27 +52:37:29.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:35.27 +52:37:29.4: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:35.27 +52:37:29.4: 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 23.4400* 23 47 35.27 +52 37 29.4 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.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 20260623.4400 13.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.30 23:39:33.81 +52:05:04.0
111.85889 -9.23529 galactic Cas Second-epoch detections are separated by 8.7" and 2.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:39:33.81 +52:05:04.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:39:33.81 +52:05:04.0: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:39:33.81 +52:05:04.0: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 39 33.81 +52 05 04.0 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.37 00:07:59.19 +53:41:22.8
116.45074 -8.63440 galactic Cas Second-epoch detections are separated by 5.4" and 3.0 pix
The object was found in VSX16" Gaia DR3 420056189628253696
Type: ROT
# Max. Min./Amp. JD0 Period
16.210 G 16.250 G K
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:07:59.19 +53:41:22.8: 15.88 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:07:59.19 +53:41:22.8: 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 23.4400* 00 07 59.19 +53 41 22.8 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420056189628253696,2461214.9400,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 420056189628253696 20260623.4400 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 23.4400 2461214.9400 13.38 23:43:08.43 +52:00:45.7
112.37555 -9.45368 galactic Cas Second-epoch detections are separated by 8.9" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:08.43 +52:00:45.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:08.43 +52:00:45.7: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:43:08.43 +52:00:45.7: 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 23.4400* 23 43 08.43 +52 00 45.7 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 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 23.4400 2461214.9400 13.38 00:04:15.87 +50:02:41.5
115.21703 -12.11893 galactic Cas Second-epoch detections are separated by 8.3" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:04:15.87 +50:02:41.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:15.87 +50:02:41.5: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:15.87 +50:02:41.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 23.4400* 00 04 15.87 +50 02 41.5 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 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 23.4400 2461214.9400 13.54 00:29:26.06 +55:19:08.2
119.77870 -7.41803 galactic Cas Second-epoch detections are separated by 7.6" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J007.3685+55.3103 | 00:29:26.06 +55:19:08.2 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:29:26.06 +55:19:08.2: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:29:26.06 +55:19:08.2: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 29 26.06 +55 19 08.2 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J007.3685+55.3103,2461214.9400,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
ATO J007.3685+55.3103 20260623.4400 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 23.4400 2461214.9400 13.30 23:33:48.12 +52:45:00.8
111.20217 -8.34437 galactic Cas Second-epoch detections are separated by 7.9" and 3.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:33:48.12 +52:45:00.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:48.12 +52:45:00.8: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:48.12 +52:45:00.8: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 33 48.12 +52 45 00.8 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,2461214.9400,13.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.48 23:47:22.86 +50:57:27.1
112.74761 -10.64317 galactic Cas Second-epoch detections are separated by 5.6" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:22.86 +50:57:27.1 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:22.86 +50:57:27.1: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:22.86 +50:57:27.1: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 47 22.86 +50 57 27.1 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.62 00:00:55.41 +51:38:18.2
115.00111 -10.45382 galactic Cas Second-epoch detections are separated by 7.3" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:55.41 +51:38:18.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:00:55.41 +51:38:18.2: 15.76 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:00:55.41 +51:38:18.2: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 00 55.41 +51 38 18.2 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 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 23.4400 2461214.9400 13.54 23:58:58.97 +53:17:25.0
115.04433 -8.77624 galactic Cas Second-epoch detections are separated by 1.9" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:58:58.97 +53:17:25.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:58.97 +53:17:25.0: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:58.97 +53:17:25.0: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 58 58.97 +53 17 25.0 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.52 00:22:18.95 +54:07:08.2
118.62482 -8.50908 galactic Cas Second-epoch detections are separated by 8.0" and 3.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 J005.5831+54.1276 | 00:22:15.96 +54:07:35.4 (Gaia DR3) | dubious (ATLAS) | (ATLAS) | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:18.95 +54:07:08.2: 15.71 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:18.95 +54:07:08.2: 15.06 +/- 0.17 detection
Forced photometry reference-image weighted average: 15.21 +/- 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 23.4400* 00 22 18.95 +54 07 08.2 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J005.5831+54.1276,2461214.9400,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
ATO J005.5831+54.1276 20260623.4400 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 23.4400 2461214.9400 13.60 00:11:48.20 +52:52:43.8
116.88736 -9.52713 galactic Cas Second-epoch detections are separated by 5.7" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:11:48.20 +52:52:43.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:48.20 +52:52:43.8: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:48.20 +52:52:43.8: 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 23.4400* 00 11 48.20 +52 52 43.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,2461214.9400,13.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.55 00:09:34.15 +53:25:48.0
116.64143 -8.92960 galactic Cas Second-epoch detections are separated by 7.3" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:09:34.15 +53:25:48.0 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:09:34.15 +53:25:48.0: 15.90 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:09:34.15 +53:25:48.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 23.4400* 00 09 34.15 +53 25 48.0 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.64 23:40:43.27 +51:15:01.6
111.80010 -10.08641 galactic Cas Second-epoch detections are separated by 8.3" and 3.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J355.1621+51.2503 | 23:40:43.27 +51:15:01.6 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:40:43.27 +51:15:01.6: 15.85 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:40:43.27 +51:15:01.6: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 40 43.27 +51 15 01.6 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.1621+51.2503,2461214.9400,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J355.1621+51.2503 20260623.4400 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 23.4400 2461214.9400 13.59 00:11:46.89 +54:49:20.0
117.18864 -7.60670 galactic Cas Second-epoch detections are separated by 6.5" and 3.3 pix
The object was found in VSX21" Gaia DR3 420549080074063744
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.400 G 13.470 G 0.042846600000 F
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:11:46.89 +54:49:20.0: 15.45 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:11:46.89 +54:49:20.0: 15.46 +/- 0.35 detection
Forced photometry reference-image weighted average: 15.46 +/- 0.35
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 11 46.89 +54 49 20.0 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 420549080074063744,2461214.9400,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 420549080074063744 20260623.4400 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.65 23:50:25.88 +54:13:28.8
114.00674 -7.58650 galactic Cas Second-epoch detections are separated by 5.9" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:50:25.88 +54:13:28.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:50:25.88 +54:13:28.8: 15.76 +/- 0.34 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:50:25.88 +54:13:28.8: 15.74 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.76 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 50 25.88 +54 13 28.8 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.50 23:41:04.30 +52:46:31.2
112.27503 -8.63431 galactic Cas Second-epoch detections are separated by 7.7" and 2.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:41:04.30 +52:46:31.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:41:04.30 +52:46:31.2: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:04.30 +52:46:31.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 23.4400* 23 41 04.30 +52 46 31.2 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.55 00:22:24.89 +53:06:33.1
118.52304 -9.51392 galactic Cas Second-epoch detections are separated by 6.4" and 2.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 J005.6228+53.1112 | 00:22:24.89 +53:06:33.1 (user input) | dubious (ATLAS) | (ATLAS) | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:24.89 +53:06:33.1: 15.82 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:24.89 +53:06:33.1: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 22 24.89 +53 06 33.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
ATO J005.6228+53.1112,2461214.9400,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J005.6228+53.1112 20260623.4400 13.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.65 23:48:29.28 +54:40:54.6
113.84076 -7.07496 galactic Cas Second-epoch detections are separated by 5.5" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:48:29.28 +54:40:54.6 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:48:29.28 +54:40:54.6: 15.38 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:48:29.28 +54:40:54.6: 15.38 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.38 +/- 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 23.4400* 23 48 29.28 +54 40 54.6 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 13.66 23:33:29.11 +52:54:08.4
111.20205 -8.18491 galactic Cas Second-epoch detections are separated by 7.5" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:29.11 +52:54:08.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:29.11 +52:54:08.4: 15.61 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:33:29.11 +52:54:08.4: 15.67 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 33 29.11 +52 54 08.4 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.82 00:27:59.44 +53:40:04.0
119.41920 -9.04397 galactic Cas Second-epoch detections are separated by 8.0" and 2.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 419449534092615296 | 00:27:59.15 +53:39:25.4 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:27:59.44 +53:40:04.0: 15.80 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:27:59.44 +53:40:04.0: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 27 59.44 +53 40 04.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 419449534092615296,2461214.9400,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 419449534092615296 20260623.4400 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 23.4400 2461214.9400 13.68 23:54:48.61 +54:09:11.2
114.61961 -7.80218 galactic Cas Second-epoch detections are separated by 4.8" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:54:48.61 +54:09:11.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:48.61 +54:09:11.2: 15.70 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:48.61 +54:09:11.2: 15.67 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 54 48.61 +54 09 11.2 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.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 20260623.4400 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.85 00:05:11.36 +52:08:40.3
115.75534 -10.08161 galactic Cas Second-epoch detections are separated by 3.6" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:11.36 +52:08:40.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:11.36 +52:08:40.3: 15.94 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:05:11.36 +52:08:40.3: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 05 11.36 +52 08 40.3 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.76 23:52:39.04 +53:51:31.7
114.24089 -8.01799 galactic Cas Second-epoch detections are separated by 5.7" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:52:39.04 +53:51:31.7 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:39.04 +53:51:31.7: 15.96 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:52:39.04 +53:51:31.7: 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 23.4400* 23 52 39.04 +53 51 31.7 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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
target 20260623.4400 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 23.4400 2461214.9400 13.84 00:01:25.63 +53:19:29.9
115.41337 -8.81515 galactic Cas Second-epoch detections are separated by 7.5" and 3.3 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:01:25.63 +53:19:29.9 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:01:25.63 +53:19:29.9: 15.73 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:01:25.63 +53:19:29.9: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 01 25.63 +53 19 29.9 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.84CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.83 23:57:06.73 +52:12:25.4
114.53527 -9.77679 galactic Cas Second-epoch detections are separated by 6.1" and 3.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:06.73 +52:12:25.4 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:57:06.73 +52:12:25.4: 15.91 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:57:06.73 +52:12:25.4: 15.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 57 06.73 +52 12 25.4 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.83,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.83CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 13.93 00:00:50.24 +53:37:24.2
115.38549 -8.50532 galactic Cas Second-epoch detections are separated by 3.3" and 2.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:00:50.24 +53:37:24.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:00:50.24 +53:37:24.2: 15.74 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:00:50.24 +53:37:24.2: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 00 50.24 +53 37 24.2 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,13.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 13.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 14.04 00:04:13.00 +51:49:48.3
115.54723 -10.36331 galactic Cas Second-epoch detections are separated by 3.4" and 2.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:04:13.00 +51:49:48.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:13.00 +51:49:48.3: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:13.00 +51:49:48.3: 15.58 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 04 13.00 +51 49 48.3 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 14.24 00:12:16.05 +57:18:49.5
117.64035 -5.15501 galactic Cas Second-epoch detections are separated by 5.3" and 2.7 pix
The object was found in VSX12" FL Cas
Type: M
# Max. Min./Amp. JD0 Period
14.600 pg < 17.500 pg 2428140.00000 278.000000000000
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:16.05 +57:18:49.5: 15.86 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:16.05 +57:18:49.5: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 12 16.05 +57 18 49.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
FL Cas,2461214.9400,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
FL Cas 20260623.4400 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 23.4400 2461214.9400 14.23 00:05:48.09 +53:57:50.5
116.17794 -8.30819 galactic Cas Second-epoch detections are separated by 5.8" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:05:48.09 +53:57:50.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:48.09 +53:57:50.5: 15.81 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:05:48.09 +53:57:50.5: 15.82 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 05 48.09 +53 57 50.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,2461214.9400,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 20260623.4400 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 23.4400 2461214.9400 10.71 00:04:41.28 +55:32:13.3
116.30368 -6.73193 galactic Cas Second-epoch detections are separated by 4.0" and 3.0 pix
The object was found in VSX 5" DI Cas
Type: M
# Max. Min./Amp. JD0 Period
11.200 V 16.500 V 2437170.00000 363.900000000000 M5
The object was not found in astcheck.
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:41.28 +55:32:13.3: 14.61 +/- 0.11 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:41.28 +55:32:13.3: 14.59 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.60 +/- 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 23.4400* 00 04 41.28 +55 32 13.3 10.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
DI Cas,2461214.9400,10.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
DI Cas 20260623.4400 10.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 23.4400 2461214.9400 11.52 00:20:45.67 +50:12:00.8
117.91468 -12.37244 galactic Cas Second-epoch detections are separated by 6.8" and 3.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:20:45.67 +50:12:00.8 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:45.67 +50:12:00.8: 15.84 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:45.67 +50:12:00.8: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 00 20 45.67 +50 12 00.8 11.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,11.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 11.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 23.4400 2461214.9400 10.73 23:55:50.69 +53:44:35.5
114.67946 -8.23542 galactic Cas Second-epoch detections are separated by 0.9" and 3.1 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:55:50.69 +53:44:35.5 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:50.69 +53:44:35.5: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:55:50.69 +53:44:35.5: 15.73 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 55 50.69 +53 44 35.5 10.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,2461214.9400,10.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 20260623.4400 10.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 23.4400 2461214.9400 10.61 23:38:17.08 +56:01:51.2
112.78846 -5.39344 galactic Cas Second-epoch detections are separated by 8.6" and 2.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:38:17.08 +56:01:51.2 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:17.08 +56:01:51.2: 15.75 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:38:17.08 +56:01:51.2: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 38 17.08 +56 01 51.2 10.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,2461214.9400,10.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260623.4400 10.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 23.4400 2461214.9400 8.29 23:58:26.06 +51:26:29.3
114.57503 -10.56819 galactic Cas Second-epoch detections are separated by 2.1" and 3.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:58:26.06 +51:26:29.3 (user input) | T | P | (position from user input)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:26.06 +51:26:29.3: 15.67 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:26.06 +51:26:29.3: 15.64 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 23.4400* 23 58 26.06 +51 26 29.3 8.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461214.9400,8.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 20260623.4400 8.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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461214.94019346 23.06.2026 10:33:42.715 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 10
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.78
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: 6 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): 22868
Objects passed selection criteria: 22769
Measurements per detected object (mean, median, min, max): 2.7 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.7 2.0 2 4
Average stars detected per image: 16112.8
Average stars matched: 14935.8 (92.6952 %)
Memory usage VmPeak: 126840 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sun Jun 21 14:44:16 CDT 2026
VaST build number 1.0rc89-107-g3b0f95a5
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-21)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Tue Jun 23 07:51:42 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: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
First image: 2461082.59778519 11.02.2026 02:20:38.640 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Last image: 2461214.94019346 23.06.2026 10:33:42.715 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 272
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.39
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: 93 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): 183520
Objects passed selection criteria: 183006
Measurements per detected object (mean, median, min, max): 2.8 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.8 2.0 2 4
Average stars detected per image: 138558
Average stars matched: 127113 (91.7401 %)
Memory usage VmPeak: 1938240 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sun Jun 21 14:44:16 CDT 2026
VaST build number 1.0rc89-107-g3b0f95a5
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-21)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Tue Jun 23 08:19:47 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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.cat to cache
SExtractor catalog cache: saved Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_onlybrightstars_v1
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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: 2461214.93973023
Plate-solving the images
'tocp_transients_list.txt' -> '../tocp_transients_list.txt'
'asassn_transients_list.txt' -> '../asassn_transients_list.txt'
'tns_transients_list.txt' -> '../tns_transients_list.txt'
wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits'
wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits exists and is non-empty
Saving wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits to local_wcs_cache/
'wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits' -> 'local_wcs_cache/wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits'
wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits'
wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits'
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits (1st reference image)
verification OK: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Image size: 941.8'x627.0' 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: 23:59:52.581 +53:59:29.78 J2000 4789.000 3195.000
###################################
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:58.344 +54:00:53.04 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:52.581 +53:59:29.78
Second-epoch image center 23:59:58.344 +54:00:53.04
Angular distance between the image centers 0.0271 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# fov_of_wcs_calibrated_image.sh output for wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:57.263 +54:00:38.08 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:52.581 +53:59:29.78
Second-epoch image center 23:59:57.263 +54:00:38.08
Angular distance between the image centers 0.0222 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 23:59:58.344 +54:00:53.04
Second-epoch second image center 23:59:57.263 +54:00:38.08
Angular distance between the image centers 0.00493 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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits &> /tmp/tmp.rv68SKXbpB
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits &> /tmp/tmp.5A2Gw2L5dw
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits &> /tmp/tmp.X7ay6lwJsX
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits &> /tmp/tmp.9StkkLZQKo
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Calibrating the magnitude scale
Found non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
____ Start of magnitude calibration ____
PHOTOMETRIC_CALIBRATION=TYCHO2_V
Calibrating the magnitude scale with Tycho-2 stars
util/transients/transient_factory_test31.sh is checking for the presence of non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
wait (drain background util/solve_plate_with_UCAC5 jobs before Tycho-2 calibration -- avoids wcs_.fits write race)
Tycho-2 catalog is found at lib/catalogs/tycho2
Tycho-2 catalog and the derived bright star exclusion list are ready
Checking for the presence of non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
Found non-empty wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits and wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
The reference image (wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits) and catalog (wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat) found
'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat' -> 'wcsmag.cat'
Read 29225 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0002 to 359.9995 deg, Dec +47.7049 to +59.3705 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.0002 to 359.9995 deg, Dec 47.7049 to 59.3705 deg
Loaded 162590 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): 14935 out of 16561 total matches.
Matched with Tycho-2 16561 out of 29225 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.842700
a=0.000000 b=1.000000 c=22.842700
From vast_summary.log: estimated ref. image limiting mag.: -7.78
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.06
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.06
Lightcurve magnitude calibration plot:
Preparing per-reference-image forced-photometry calibration (method=tycho2 band=V)
Read 29225 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0002 to 359.9995 deg, Dec +47.7049 to +59.3705 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.0002 to 359.9995 deg, Dec 47.7049 to 59.3705 deg
Loaded 162590 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): 14935 out of 16561 total matches.
Matched with Tycho-2 16561 out of 29225 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits (aperture=6.0)
Read 29065 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 0.0009 to 359.9998 deg, Dec +47.6373 to +59.3623 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.0009 to 359.9998 deg, Dec 47.6373 to 59.3623 deg
Loaded 163448 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): 14807 out of 16429 total matches.
Matched with Tycho-2 16429 out of 29065 detected stars.
util/calibrate_single_image_with_tycho2.sh: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits via Tycho-2
Single-image forced-photometry magnitude calibration plot for wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits:
Forced-photometry filter: calibrated wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits -> calib.txt_param_ref_wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits (aperture=6.0)
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 9 candidate transients before the final filtering. (Hard limit: 8000)
Median FWHM seeing for isolated stars:
2.1 pix Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
2.1 pix Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
2.3 pix fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
2.3 pix fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
2.1 pix wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
2.1 pix wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Limiting magnitude estimates:
15.1 mag. Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
15.1 mag. Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
14.2 mag. fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
14.2 mag. fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
All-image limiting magnitude estimate: 14.2 (SNR ) 11.3 (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.rv68SKXbpB (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh: line 136: echo: write error: Broken pipe
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits' -> 'wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3209, bad_region=7497, passed=29225
Got 29225 stars (including 19224 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat
util/solve_plate_with_UCAC5 got 29225 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.8'
Seting catalog search parameters based on the expected field of view 941.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013081 (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.010464 (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 345.4494 through 0 to 15.3164, gap 15.3164 to 345.4494
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 968 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.56"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22315 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.4506 through 0 to 15.3182, gap 15.3182 to 345.4506
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.7 to 59.4)
Done reading UCAC5 zone files...
Matched 975 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22314 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.54"
Accuracy estimation diagnostic: 973 matched stars entering correct_measured_positions(), 22315 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.46"
Excluding outliers - 973 stars left (next iteration limit 1070)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits N_match=973 sigma_overall_arcsec=0.484 sigma_q1_arcsec=0.551 sigma_q2_arcsec=0.430 sigma_q3_arcsec=0.487 sigma_q4_arcsec=0.426 n_q1=280 n_q2=198 n_q3=285 n_q4=210 worst_quadrant_to_overall_ratio=1.137
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits -region wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.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.5A2Gw2L5dw (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits' -> 'wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS_IMAGE_NAME=wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS-calibrated image found: wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
Checking if the catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits alredy exist and is non-empty...
Catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat corresponding to the image wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits
WCS catalog name: wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=3195, bad_region=7496, passed=29065
Got 29065 stars (including 19086 good ones) from the SExtractor catalog wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat
util/solve_plate_with_UCAC5 got 29065 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.8'
Seting catalog search parameters based on the expected field of view 941.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013081 (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.010464 (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 345.4479 through 0 to 15.3165, gap 15.3165 to 345.4479
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 964 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.55"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22203 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.4487 through 0 to 15.3181, gap 15.3181 to 345.4487
Reading UCAC5 zone files...
Searching UCAC5 zones 688 to 748 (Dec 47.6 to 59.4)
Done reading UCAC5 zone files...
Matched 974 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.53"
Accuracy estimation diagnostic: 972 matched stars entering correct_measured_positions(), 22202 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.48"
Excluding outliers - 972 stars left (next iteration limit 1069)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
WCS_QUALITY_DIAG: file=Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits N_match=972 sigma_overall_arcsec=0.506 sigma_q1_arcsec=0.539 sigma_q2_arcsec=0.430 sigma_q3_arcsec=0.560 sigma_q4_arcsec=0.425 n_q1=282 n_q2=199 n_q3=280 n_q4=211 worst_quadrant_to_overall_ratio=1.107
The image catalog is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits -region wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.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.X7ay6lwJsX (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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1084, bad_region=3520, passed=14479
Got 14479 stars (including 10072 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat
util/solve_plate_with_UCAC5 got 14479 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0820 through 0 to 14.8809, gap 14.8809 to 345.0820
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 315 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 237 matched stars entering correct_measured_positions(), 169 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.88"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 228 matched stars entering correct_measured_positions(), 3083 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.96"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0696 through 0 to 14.9070, gap 14.9070 to 345.0696
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 385 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 328 matched stars entering correct_measured_positions(), 3128 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.83"
Accuracy estimation diagnostic: 320 matched stars entering correct_measured_positions(), 4255 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.40"
Excluding outliers - 320 stars left (next iteration limit 250)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits N_match=320 sigma_overall_arcsec=9.669 sigma_q1_arcsec=24.865 sigma_q2_arcsec=25.976 sigma_q3_arcsec=6.400 sigma_q4_arcsec=9.876 n_q1=33 n_q2=25 n_q3=124 n_q4=138 worst_quadrant_to_overall_ratio=2.687
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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.9StkkLZQKo (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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1053, bad_region=3451, passed=14010
Got 14010 stars (including 9711 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat
util/solve_plate_with_UCAC5 got 14010 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0819 through 0 to 14.8813, gap 14.8813 to 345.0819
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 312 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 236 matched stars entering correct_measured_positions(), 168 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.60"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 227 matched stars entering correct_measured_positions(), 2758 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.60"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0690 through 0 to 14.9068, gap 14.9068 to 345.0690
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 330 matched stars entering correct_measured_positions(), 2814 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.43"
Accuracy estimation diagnostic: 322 matched stars entering correct_measured_positions(), 3802 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.00"
Excluding outliers - 322 stars left (next iteration limit 249)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits N_match=322 sigma_overall_arcsec=9.288 sigma_q1_arcsec=24.640 sigma_q2_arcsec=25.693 sigma_q3_arcsec=6.042 sigma_q4_arcsec=9.530 n_q1=32 n_q2=24 n_q3=120 n_q4=146 worst_quadrant_to_overall_ratio=2.766
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits sigma_overall=0.484 worst_q_ratio=1.137
ref2=Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits sigma_overall=0.506 worst_q_ratio=1.107
new1=fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits sigma_overall=9.669 worst_q_ratio=2.687
new2=fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits sigma_overall=9.288 worst_q_ratio=2.766
reference average sigma_overall=0.495 worst_q_ratio=1.122
warn-on-ratio threshold: 2.0x reference
###################################
WCS_QUALITY_RETRY: 1st new image (fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits) flagged: sigma=9.669 (ref avg 0.495), ratio=2.687 (ref avg 1.122), 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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/lib/make_outxyls_for_astrometric_calibration found 13915 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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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: "out1364647.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1364647.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 28.3799 (2.11472e+12), 7 match, 0 conflict, 16 distractors, 25 index.
RA,Dec = (359.99,54.0131), pixel scale 5.93146 arcsec/pix.
Hit/miss: Hit/miss: ---++-----+-----+++---+(best)---------+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1364647.solved to indicate this.
Field: out1364647.xyls
Field center: (RA,Dec) = (359.991710, 54.013913) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.010, +54:00:50.088).
Field size: 15.6063 x 10.4329 degrees
Field rotation angle: up is 4.1204 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 23 08:00 fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
-rw-r--r-- 1 apache apache 8.5K Jun 23 08:00 out1364647.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits (fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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: "out1364647.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1364647.axy"...
Only searching for solutions within 15.445 degrees of RA,Dec (359.993,54.0147)
log-odds ratio 28.3799 (2.11472e+12), 7 match, 0 conflict, 16 distractors, 25 index.
RA,Dec = (359.99,54.0131), pixel scale 5.93146 arcsec/pix.
Hit/miss: Hit/miss: ---++-----+-----+++---+(best)---------+-------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1364647.solved to indicate this.
Field: out1364647.xyls
Field center: (RA,Dec) = (359.991710, 54.013913) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.010, +54:00:50.088).
Field size: 15.6063 x 10.4329 degrees
Field rotation angle: up is 4.1204 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 23 08:00 fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
-rw-r--r-- 1 apache apache 8.5K Jun 23 08:00 out1364647.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.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-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 83103 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.axy"...
Verifying WCS using indices with quads of size [63.1503, 946.661] 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.1503, 946.661] 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).
Total CPU time limit reached!
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:58.344 +54:00:53.04 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 14479 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/correct_sextractor_wcs_catalog_usingxy2sky3284051.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1084, bad_region=3520, passed=14479
Got 14479 stars (including 10072 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat
util/solve_plate_with_UCAC5 got 14479 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0820 through 0 to 14.8809, gap 14.8809 to 345.0820
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 315 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 237 matched stars entering correct_measured_positions(), 169 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.88"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 228 matched stars entering correct_measured_positions(), 3083 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.96"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0696 through 0 to 14.9070, gap 14.9070 to 345.0696
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 385 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 328 matched stars entering correct_measured_positions(), 3128 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.83"
Accuracy estimation diagnostic: 320 matched stars entering correct_measured_positions(), 4255 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.40"
Excluding outliers - 320 stars left (next iteration limit 250)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits N_match=320 sigma_overall_arcsec=9.669 sigma_q1_arcsec=24.865 sigma_q2_arcsec=25.976 sigma_q3_arcsec=6.400 sigma_q4_arcsec=9.876 n_q1=33 n_q2=25 n_q3=124 n_q4=138 worst_quadrant_to_overall_ratio=2.687
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 1st new image (fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits): sigma 9.669->9.669, ratio 2.687->2.687; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits) flagged: sigma=9.288 (ref avg 0.495), ratio=2.766 (ref avg 1.122), 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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/lib/make_outxyls_for_astrometric_calibration found 13442 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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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: "out3286462.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3286462.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
log-odds ratio 28.1121 (1.61783e+12), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.986,54.0089), pixel scale 5.93143 arcsec/pix.
Hit/miss: Hit/miss: ---++-----+---+--++---+-----+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3286462.solved to indicate this.
Field: out3286462.xyls
Field center: (RA,Dec) = (359.987205, 54.009758) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.929, +54:00:35.130).
Field size: 15.6061 x 10.4327 degrees
Field rotation angle: up is 4.12711 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits'
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 23 08:08 fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
-rw-r--r-- 1 apache apache 8.5K Jun 23 08:08 out3286462.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits (fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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: "out3286462.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out3286462.axy"...
Only searching for solutions within 15.445 degrees of RA,Dec (359.989,54.0106)
log-odds ratio 28.1121 (1.61783e+12), 8 match, 0 conflict, 21 distractors, 26 index.
RA,Dec = (359.986,54.0089), pixel scale 5.93143 arcsec/pix.
Hit/miss: Hit/miss: ---++-----+---+--++---+-----+(best)-----------------------------------------------------------------------
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out3286462.solved to indicate this.
Field: out3286462.xyls
Field center: (RA,Dec) = (359.987205, 54.009758) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.929, +54:00:35.130).
Field size: 15.6061 x 10.4327 degrees
Field rotation angle: up is 4.12711 degrees E of N
Field parity: neg
WCS keywords and Astrometry.net provenance markers have been successfully stripped from all HDUs in the file.
-rw-r--r-- 1 apache apache 117M Jun 23 08:08 fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
-rw-r--r-- 1 apache apache 8.5K Jun 23 08:08 out3286462.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.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-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 80954 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.axy"...
Verifying WCS using indices with quads of size [63.15, 946.656] 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 7.78735
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 8.2022
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 6.89573
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 5.72392
Verifying WCS using indices with quads of size [63.15, 946.656] 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 7.78735
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 8.2022
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 6.89573
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 5.72392
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).
Total CPU time limit reached!
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
Image size: 926.7'x616.3' 15.4(deg)x10.3(deg) 9576x6388 pix
Image scale: 5.81"/pix along the X axis and 5.79"/pix along the Y axis
Image center: 23:59:57.263 +54:00:38.08 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 14010 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/correct_sextractor_wcs_catalog_usingxy2sky152422.tmp' -> 'vast_debug_catalog_after_xy2sky_correction.cat.log'
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat
Excluding image region: -1.0 -1.0 1.0 1.0 (defined in bad_region.lst)
Excluding image region: 7500.0 0.0 9576.0 6388.0 (defined in bad_region.lst)
Excluding image region: 1122.0 1550.0 1124.0 1552.0 (defined in bad_region.lst)
Excluding image region: 1637.0 2824.0 1639.0 2826.0 (defined in bad_region.lst)
Excluding image region: 1831.0 2839.0 1833.0 2841.0 (defined in bad_region.lst)
Excluding image region: 1905.0 4570.0 1907.0 4572.0 (defined in bad_region.lst)
Excluding image region: 2012.0 4693.0 2014.0 4695.0 (defined in bad_region.lst)
Excluding image region: 2397.0 4241.0 2399.0 4243.0 (defined in bad_region.lst)
Excluding image region: 2679.0 2807.0 2681.0 2809.0 (defined in bad_region.lst)
Excluding more image regions!.. (will not print them all)
Excluded a total of 31 image regions (defined in bad_region.lst).
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1053, bad_region=3451, passed=14010
Got 14010 stars (including 9711 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat
util/solve_plate_with_UCAC5 got 14010 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.7'
Seting catalog search parameters based on the expected field of view 926.7 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012871 (46.3 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010297 (37.1 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0819 through 0 to 14.8813, gap 14.8813 to 345.0819
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 312 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 236 matched stars entering correct_measured_positions(), 168 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.60"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 227 matched stars entering correct_measured_positions(), 2758 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.60"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 345.0690 through 0 to 14.9068, gap 14.9068 to 345.0690
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.3 to 59.3)
Done reading UCAC5 zone files...
Matched 389 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 330 matched stars entering correct_measured_positions(), 2814 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.43"
Accuracy estimation diagnostic: 322 matched stars entering correct_measured_positions(), 3802 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.00"
Excluding outliers - 322 stars left (next iteration limit 249)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits N_match=322 sigma_overall_arcsec=9.288 sigma_q1_arcsec=24.640 sigma_q2_arcsec=25.693 sigma_q3_arcsec=6.042 sigma_q4_arcsec=9.530 n_q1=32 n_q2=24 n_q3=120 n_q4=146 worst_quadrant_to_overall_ratio=2.766
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
WCS_QUALITY_RETRY: --tweak-order 2 did NOT improve 2nd new image (fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits): sigma 9.288->9.288, ratio 2.766->2.766; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=9.669 -- 19.53x the reference average (0.495); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=9.288 -- 18.76x the reference average (0.495); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=2.687 -- 2.39x the reference average (1.122); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=2.766 -- 2.47x the reference average (1.122); plate solution may be of low accuracy
Astrometric residual vector field (catalog-matched stars):
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006_astrometric_residuals.png (973 matched stars from wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.43 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007_astrometric_residuals.png (972 matched stars from wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 0.46 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472_astrometric_residuals.png (320 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 4.08 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473_astrometric_residuals.png (322 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 3.66 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-02_20.00sec_5.00C_LIGHT_0472.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-23_CI_Cas-04-Q2b1x1_061204_TTUQ2b1x1_221461_uKs78KfQ/wcs_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473.fits'
Preparing the HTML report for the field Cas-04-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:44.33 +50:11:40.6: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:54:24.39 +53:21:11.5: 15.57 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:22:45.50 +53:12:12.4: 13.84 +/- 0.06 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:58:26.59 +51:26:22.2: 15.64 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:44.33 +50:11:40.6: 15.62 +/- 99.00 upperlimit
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:45.50 +53:12:12.4: 13.83 +/- 0.07 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:54:24.39 +53:21:11.5: 15.57 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 13.83 +/- 0.05
Forced photometry filter KEPT candidate at 00:22:45.50 +53:12:12.4: ref_mag=13.83 +/- 0.05 new_mean_mag=11.1416 delta=2.69 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:26.59 +51:26:22.2: 15.33 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.33 +/- 0.29
Forced photometry filter KEPT candidate at 23:58:26.59 +51:26:22.2: ref_mag=15.33 +/- 0.29 new_mean_mag=7.9444 delta=7.38 (need > 0.90)
Adding exclusion_list_local.txt__out21888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31471.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33069.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33280.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 18s
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: 5s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31471_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 31471_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32420_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 32420_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:04:40.61 +55:32:10.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32488_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 32488_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:55:49.97 +53:44:29.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33069_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 33069_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33200_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 33200_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:06:02.62 +55:11:56.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33280_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 33280_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34253_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 34253_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:50:44.66 +53:34:44.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 21888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 09534_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 09534_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243674_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243674_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243678_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243678_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243687_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243687_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243691_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243691_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243694_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243694_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243696_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243696_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243698_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243698_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243703_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243703_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243705_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243705_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243714_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243714_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243716_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243716_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243718_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243718_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243719_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243719_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243720_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243720_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243724_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243724_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243734_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243734_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243736_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243736_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243737_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243737_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243740_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243740_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243743_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243743_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243748_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243748_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243752_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243752_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243760_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243760_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243763_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243763_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243765_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243765_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243768_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243768_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243769_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243769_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243770_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243770_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243771_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243771_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243772_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243772_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243776_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243776_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (30.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243777_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243777_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243779_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243779_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243783_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243783_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243793_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243793_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243795_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243795_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243797_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243797_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243801_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243801_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243802_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243802_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243804_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243804_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243811_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243811_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243812_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243812_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243819_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243819_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243820_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243820_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243822_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243822_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243823_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243823_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243827_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243827_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243828_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243828_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243830_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243830_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243835_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243835_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243839_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243839_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243842_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243842_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243844_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243844_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243846_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243846_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243847_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243847_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243849_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243849_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243851_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243851_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243855_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243855_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243859_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243859_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243860_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243860_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243862_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243862_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243863_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243863_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243864_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243864_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243865_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243865_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243869_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243869_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243871_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243871_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243873_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243873_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243875_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243875_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243876_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243876_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243879_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243879_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243882_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243882_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243883_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243883_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243884_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 243884_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 243888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:56:37.80 +54:36:43.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244546_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 244546_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244737_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 244737_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244838_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 244838_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245677_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 245677_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245693_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 245693_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:06:03.04 +55:11:50.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247394_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 247394_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247423_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 247423_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248478_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 248478_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248487_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 248487_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248987_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 248987_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:44:11.02 +56:38:05.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250437_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 250437_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:04:18.77 +54:17:21.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250596_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 250596_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:42:05.85 +57:16:03.7 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250989_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 250989_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (12.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251178_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 251178_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251231_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 251231_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251613_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 251613_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251634_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 251634_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251847_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 251847_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:47:14.50 +57:25:40.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252018_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 252018_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252374_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 252374_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252394_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 252394_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253021_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 253021_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253092_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 253092_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:42:07.29 +57:15:32.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253614_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 253614_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (19.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253629_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 253629_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253666_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 253666_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253817_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 253817_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254219_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 254219_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254260_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 254260_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254331_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 254331_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254378_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 254378_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254896_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 254896_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:02:36.69 +55:35:34.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255002_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255002_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255106_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255106_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255185_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255185_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255236_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255236_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255445_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255445_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255504_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255504_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255576_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255576_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255584_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255584_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255610_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255610_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255622_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255622_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255790_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255790_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255796_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 255796_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255947_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 255947_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256169_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 256169_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256352_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 256352_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256439_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 256439_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256500_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 256500_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256801_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 256801_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (20.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256904_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 256904_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256942_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 256942_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257025_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257025_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257092_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257092_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257216_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 257216_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257219_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257219_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257299_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257299_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257514_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257514_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257522_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257522_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257637_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 257637_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257645_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 257645_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257667_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257667_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257955_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257955_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257957_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 257957_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257975_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 257975_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258180_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 258180_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258186_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 258186_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258314_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258314_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258344_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258344_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258497_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258497_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258505_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258505_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258524_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258524_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258632_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258632_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258664_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 258664_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258665_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258665_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258739_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 258739_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258874_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258874_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258953_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258953_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 258975_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 258975_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259253_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259253_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259355_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 259355_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259376_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 259376_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259512_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259512_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (29.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259535_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259535_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259541_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259541_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259548_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259548_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259665_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259665_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (13.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259787_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259787_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259922_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 259922_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (16.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260107_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260107_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260109_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260109_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260187_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260187_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260235_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 260235_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260459_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260459_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260511_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260511_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:14:00.99 +55:16:09.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260577_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 260577_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260602_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260602_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:18:30.92 +55:38:52.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260608_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 260608_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260612_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260612_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 00:04:14.66 +54:16:38.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260844_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260844_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260871_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 260871_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 260888_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260990_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 260990_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261012_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 261012_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261158_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261158_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261262_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 261262_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261296_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261296_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261393_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261393_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261410_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261410_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261433_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 261433_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261439_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261439_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261525_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261525_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261638_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261638_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261759_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 261759_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261899_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261899_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261978_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 261978_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261986_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 261986_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262000_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 262000_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262156_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262156_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262461_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 262461_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262503_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262503_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262529_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262529_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262549_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262549_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262747_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 262747_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262818_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262818_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262894_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 262894_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263003_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 263003_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263088_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263088_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263095_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263095_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263265_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263265_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263379_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263379_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263623_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263623_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263810_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 263810_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263885_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 263885_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264072_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 264072_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264324_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 264324_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264369_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 264369_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264558_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 264558_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264806_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 264806_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264834_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 264834_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264885_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 264885_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265073_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 265073_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265451_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 265451_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265668_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 265668_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265879_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 265879_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265987_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 265987_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266053_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 266053_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266312_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 266312_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266770_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 266770_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266774_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 266774_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267141_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 267141_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267162_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 267162_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:58:35.19 +54:07:50.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268131_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 268131_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268176_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 268176_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268543_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 268543_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269027_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 269027_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (14.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269647_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 269647_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
Rejecting candidate due to large distance (10.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269827_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 269827_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270192_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 270192_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270221_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 270221_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58579_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 58579_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:44:32.20 +56:34:45.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 79234_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 79234_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179137_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 179137_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125040_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 125040_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71796_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 71796_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 53473_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 53473_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:52:38.84 +56:44:29.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 130430_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
The candidate 130430_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473 did not pass the final checks
**** FOUND 23:50:45.37 +53:34:44.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174810_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
Preparing report for the candidate 174810_fd_Cas-04-Q2b1x1_2026-06-23_05-33-42_20.00sec_4.90C_LIGHT_0473
make_report_in_HTML.sh Phase 2 (HTML assembly): 4s
make_report_in_HTML.sh TOTAL: 195s
Prepared the HTML report for the field Cas-04-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
23:58:26.59 +51:26:22.2
23:54:24.39 +53:21:11.5
00:22:45.50 +53:12:12.4
00:20:44.33 +50:11:40.6
23:55:50.69 +53:44:35.5
23:58:26.06 +51:26:29.3
00:20:45.67 +50:12:00.8
00:12:13.17 +52:49:02.5
23:51:17.15 +52:36:29.9
00:25:48.32 +54:30:11.3
23:39:00.92 +51:32:11.8
23:36:40.03 +52:50:54.2
00:27:57.77 +52:56:17.6
23:52:26.37 +51:58:00.1
00:15:30.65 +52:00:09.6
23:44:02.82 +52:45:15.7
23:34:47.78 +49:57:41.5
00:04:32.26 +52:54:14.9
23:54:00.86 +53:15:51.5
23:35:22.75 +56:30:59.1
23:29:21.38 +56:41:00.5
00:04:18.78 +51:51:28.6
00:22:04.39 +54:21:20.5
23:54:28.93 +54:05:57.2
23:55:09.34 +53:04:27.6
23:31:54.42 +51:39:12.2
00:10:28.35 +53:34:40.5
23:29:17.55 +55:18:44.9
23:30:30.27 +53:48:13.0
00:23:24.72 +54:55:51.3
23:43:36.00 +53:16:05.4
00:12:02.04 +54:02:13.5
23:46:43.19 +54:28:54.3
00:14:53.87 +53:15:44.1
00:16:25.15 +53:58:12.8
00:22:44.33 +52:23:06.3
23:53:28.16 +53:32:37.4
00:23:22.91 +55:49:16.0
23:49:55.72 +53:28:37.1
23:41:19.91 +51:37:00.2
00:13:38.26 +52:03:14.7
00:24:51.26 +53:02:41.0
23:31:59.77 +55:07:37.1
23:43:30.48 +50:59:05.1
00:07:37.81 +53:34:10.0
23:30:26.62 +57:57:21.1
00:12:57.96 +50:00:22.6
00:03:31.23 +49:57:58.4
23:56:33.64 +53:45:01.9
23:47:35.27 +52:37:29.4
23:39:33.81 +52:05:04.0
00:07:59.19 +53:41:22.8
23:43:08.43 +52:00:45.7
00:04:15.87 +50:02:41.5
00:29:26.06 +55:19:08.2
23:33:48.12 +52:45:00.8
23:47:22.86 +50:57:27.1
00:00:55.41 +51:38:18.2
23:58:58.97 +53:17:25.0
00:22:18.95 +54:07:08.2
00:11:48.20 +52:52:43.8
00:09:34.15 +53:25:48.0
23:40:43.27 +51:15:01.6
00:11:46.89 +54:49:20.0
23:50:25.88 +54:13:28.8
23:41:04.30 +52:46:31.2
00:22:24.89 +53:06:33.1
23:48:29.28 +54:40:54.6
23:33:29.11 +52:54:08.4
00:27:59.44 +53:40:04.0
23:54:48.61 +54:09:11.2
00:05:11.36 +52:08:40.3
23:52:39.04 +53:51:31.7
00:01:25.63 +53:19:29.9
23:57:06.73 +52:12:25.4
00:00:50.24 +53:37:24.2
00:04:13.00 +51:49:48.3
00:12:16.05 +57:18:49.5
00:05:48.09 +53:57:50.5
23:38:17.08 +56:01:51.2
00:04:41.28 +55:32:13.3
########### Completed Cas-04-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
23:54:24.39 +53:21:11.5
00:22:45.50 +53:12:12.4
00:20:44.33 +50:11:40.6
23:58:26.59 +51:26:22.2
00:12:13.17 +52:49:02.5
23:51:17.15 +52:36:29.9
00:25:48.32 +54:30:11.3
23:39:00.92 +51:32:11.8
23:36:40.03 +52:50:54.2
00:27:57.77 +52:56:17.6
23:52:26.37 +51:58:00.1
00:15:30.65 +52:00:09.6
23:44:02.82 +52:45:15.7
23:34:47.78 +49:57:41.5
00:04:32.26 +52:54:14.9
23:54:00.86 +53:15:51.5
23:35:22.75 +56:30:59.1
23:29:21.38 +56:41:00.5
00:04:18.78 +51:51:28.6
00:22:04.39 +54:21:20.5
23:54:28.93 +54:05:57.2
23:55:09.34 +53:04:27.6
23:31:54.42 +51:39:12.2
00:10:28.35 +53:34:40.5
23:29:17.55 +55:18:44.9
23:30:30.27 +53:48:13.0
00:23:24.72 +54:55:51.3
23:43:36.00 +53:16:05.4
00:12:02.04 +54:02:13.5
23:46:43.19 +54:28:54.3
00:14:53.87 +53:15:44.1
00:16:25.15 +53:58:12.8
00:22:44.33 +52:23:06.3
23:53:28.16 +53:32:37.4
00:23:22.91 +55:49:16.0
23:49:55.72 +53:28:37.1
23:41:19.91 +51:37:00.2
00:13:38.26 +52:03:14.7
00:24:51.26 +53:02:41.0
23:31:59.77 +55:07:37.1
23:43:30.48 +50:59:05.1
00:07:37.81 +53:34:10.0
23:30:26.62 +57:57:21.1
00:12:57.96 +50:00:22.6
00:03:31.23 +49:57:58.4
23:56:33.64 +53:45:01.9
23:47:35.27 +52:37:29.4
23:39:33.81 +52:05:04.0
00:07:59.19 +53:41:22.8
23:43:08.43 +52:00:45.7
00:04:15.87 +50:02:41.5
00:29:26.06 +55:19:08.2
23:33:48.12 +52:45:00.8
23:47:22.86 +50:57:27.1
00:00:55.41 +51:38:18.2
23:58:58.97 +53:17:25.0
00:22:18.95 +54:07:08.2
00:11:48.20 +52:52:43.8
00:09:34.15 +53:25:48.0
23:40:43.27 +51:15:01.6
00:11:46.89 +54:49:20.0
23:50:25.88 +54:13:28.8
23:41:04.30 +52:46:31.2
00:22:24.89 +53:06:33.1
23:48:29.28 +54:40:54.6
23:33:29.11 +52:54:08.4
00:27:59.44 +53:40:04.0
23:54:48.61 +54:09:11.2
00:05:11.36 +52:08:40.3
23:52:39.04 +53:51:31.7
00:01:25.63 +53:19:29.9
23:57:06.73 +52:12:25.4
00:00:50.24 +53:37:24.2
00:04:13.00 +51:49:48.3
00:12:16.05 +57:18:49.5
00:05:48.09 +53:57:50.5
00:04:41.28 +55:32:13.3
00:20:45.67 +50:12:00.8
23:55:50.69 +53:44:35.5
23:38:17.08 +56:01:51.2
23:58:26.06 +51:26:29.3
###################################################################################
23:54:24.39 +53:21:11.5 -- not an asteroid (will add it to exclusion list)
00:22:45.50 +53:12:12.4 -- not an asteroid (will add it to exclusion list)
00:20:44.33 +50:11:40.6 -- not an asteroid (will add it to exclusion list)
23:58:26.59 +51:26:22.2 -- not an asteroid (will add it to exclusion list)
00:12:13.17 +52:49:02.5 -- not an asteroid (will add it to exclusion list)
23:51:17.15 +52:36:29.9 -- not an asteroid (will add it to exclusion list)
00:25:48.32 +54:30:11.3 -- not an asteroid (will add it to exclusion list)
23:39:00.92 +51:32:11.8 -- not an asteroid (will add it to exclusion list)
23:36:40.03 +52:50:54.2 -- not an asteroid (will add it to exclusion list)
00:27:57.77 +52:56:17.6 -- not an asteroid (will add it to exclusion list)
23:52:26.37 +51:58:00.1 -- not an asteroid (will add it to exclusion list)
00:15:30.65 +52:00:09.6 -- not an asteroid (will add it to exclusion list)
23:44:02.82 +52:45:15.7 -- not an asteroid (will add it to exclusion list)
23:34:47.78 +49:57:41.5 -- not an asteroid (will add it to exclusion list)
00:04:32.26 +52:54:14.9 -- not an asteroid (will add it to exclusion list)
23:54:00.86 +53:15:51.5 -- not an asteroid (will add it to exclusion list)
23:35:22.75 +56:30:59.1 -- not an asteroid (will add it to exclusion list)
23:29:21.38 +56:41:00.5 -- not an asteroid (will add it to exclusion list)
00:04:18.78 +51:51:28.6 -- not an asteroid (will add it to exclusion list)
00:22:04.39 +54:21:20.5 -- not an asteroid (will add it to exclusion list)
23:54:28.93 +54:05:57.2 -- not an asteroid (will add it to exclusion list)
23:55:09.34 +53:04:27.6 -- not an asteroid (will add it to exclusion list)
23:31:54.42 +51:39:12.2 -- not an asteroid (will add it to exclusion list)
00:10:28.35 +53:34:40.5 -- not an asteroid (will add it to exclusion list)
23:29:17.55 +55:18:44.9 -- not an asteroid (will add it to exclusion list)
23:30:30.27 +53:48:13.0 -- not an asteroid (will add it to exclusion list)
00:23:24.72 +54:55:51.3 -- not an asteroid (will add it to exclusion list)
23:43:36.00 +53:16:05.4 -- not an asteroid (will add it to exclusion list)
00:12:02.04 +54:02:13.5 -- not an asteroid (will add it to exclusion list)
23:46:43.19 +54:28:54.3 -- not an asteroid (will add it to exclusion list)
00:14:53.87 +53:15:44.1 -- not an asteroid (will add it to exclusion list)
00:16:25.15 +53:58:12.8 -- not an asteroid (will add it to exclusion list)
00:22:44.33 +52:23:06.3 -- not an asteroid (will add it to exclusion list)
23:53:28.16 +53:32:37.4 -- not an asteroid (will add it to exclusion list)
00:23:22.91 +55:49:16.0 -- not an asteroid (will add it to exclusion list)
23:49:55.72 +53:28:37.1 -- not an asteroid (will add it to exclusion list)
23:41:19.91 +51:37:00.2 -- not an asteroid (will add it to exclusion list)
00:13:38.26 +52:03:14.7 -- not an asteroid (will add it to exclusion list)
00:24:51.26 +53:02:41.0 -- not an asteroid (will add it to exclusion list)
23:31:59.77 +55:07:37.1 -- not an asteroid (will add it to exclusion list)
23:43:30.48 +50:59:05.1 -- not an asteroid (will add it to exclusion list)
00:07:37.81 +53:34:10.0 -- not an asteroid (will add it to exclusion list)
23:30:26.62 +57:57:21.1 -- not an asteroid (will add it to exclusion list)
00:12:57.96 +50:00:22.6 -- not an asteroid (will add it to exclusion list)
00:03:31.23 +49:57:58.4 -- not an asteroid (will add it to exclusion list)
23:56:33.64 +53:45:01.9 -- not an asteroid (will add it to exclusion list)
23:47:35.27 +52:37:29.4 -- not an asteroid (will add it to exclusion list)
23:39:33.81 +52:05:04.0 -- not an asteroid (will add it to exclusion list)
00:07:59.19 +53:41:22.8 -- not an asteroid (will add it to exclusion list)
23:43:08.43 +52:00:45.7 -- not an asteroid (will add it to exclusion list)
00:04:15.87 +50:02:41.5 -- not an asteroid (will add it to exclusion list)
00:29:26.06 +55:19:08.2 -- not an asteroid (will add it to exclusion list)
23:33:48.12 +52:45:00.8 -- not an asteroid (will add it to exclusion list)
23:47:22.86 +50:57:27.1 -- not an asteroid (will add it to exclusion list)
00:00:55.41 +51:38:18.2 -- not an asteroid (will add it to exclusion list)
23:58:58.97 +53:17:25.0 -- not an asteroid (will add it to exclusion list)
00:22:18.95 +54:07:08.2 -- not an asteroid (will add it to exclusion list)
00:11:48.20 +52:52:43.8 -- not an asteroid (will add it to exclusion list)
00:09:34.15 +53:25:48.0 -- not an asteroid (will add it to exclusion list)
23:40:43.27 +51:15:01.6 -- not an asteroid (will add it to exclusion list)
00:11:46.89 +54:49:20.0 -- not an asteroid (will add it to exclusion list)
23:50:25.88 +54:13:28.8 -- not an asteroid (will add it to exclusion list)
23:41:04.30 +52:46:31.2 -- not an asteroid (will add it to exclusion list)
00:22:24.89 +53:06:33.1 -- not an asteroid (will add it to exclusion list)
23:48:29.28 +54:40:54.6 -- not an asteroid (will add it to exclusion list)
23:33:29.11 +52:54:08.4 -- not an asteroid (will add it to exclusion list)
00:27:59.44 +53:40:04.0 -- not an asteroid (will add it to exclusion list)
23:54:48.61 +54:09:11.2 -- not an asteroid (will add it to exclusion list)
00:05:11.36 +52:08:40.3 -- not an asteroid (will add it to exclusion list)
23:52:39.04 +53:51:31.7 -- not an asteroid (will add it to exclusion list)
00:01:25.63 +53:19:29.9 -- not an asteroid (will add it to exclusion list)
23:57:06.73 +52:12:25.4 -- not an asteroid (will add it to exclusion list)
00:00:50.24 +53:37:24.2 -- not an asteroid (will add it to exclusion list)
00:04:13.00 +51:49:48.3 -- not an asteroid (will add it to exclusion list)
00:12:16.05 +57:18:49.5 -- not an asteroid (will add it to exclusion list)
00:05:48.09 +53:57:50.5 -- not an asteroid (will add it to exclusion list)
00:04:41.28 +55:32:13.3 -- not an asteroid (will add it to exclusion list)
00:20:45.67 +50:12:00.8 -- not an asteroid (will add it to exclusion list)
23:55:50.69 +53:44:35.5 -- not an asteroid (will add it to exclusion list)
23:38:17.08 +56:01:51.2 -- not an asteroid (will add it to exclusion list)
23:58:26.06 +51:26:29.3 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:50.24 +53:37:24.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:55.41 +51:38:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:25.63 +53:19:29.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:31.23 +49:57:58.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:13.00 +51:49:48.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:15.87 +50:02:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:18.78 +51:51:28.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:32.26 +52:54:14.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:41.28 +55:32:13.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:11.36 +52:08:40.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:48.09 +53:57:50.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:37.81 +53:34:10.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:59.19 +53:41:22.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:09:34.15 +53:25:48.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:28.35 +53:34:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:46.89 +54:49:20.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:11:48.20 +52:52:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:02.04 +54:02:13.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:13.17 +52:49:02.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:16.05 +57:18:49.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:57.96 +50:00:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:38.26 +52:03:14.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:53.87 +53:15:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:15:30.65 +52:00:09.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:16:25.15 +53:58:12.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:44.33 +50:11:40.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:45.67 +50:12:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:04.39 +54:21:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:18.95 +54:07:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:24.89 +53:06:33.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:44.33 +52:23:06.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:45.50 +53:12:12.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:22.91 +55:49:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:24.72 +54:55:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:24:51.26 +53:02:41.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:25:48.32 +54:30:11.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:57.77 +52:56:17.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:59.44 +53:40:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:29:26.06 +55:19:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:17.55 +55:18:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:21.38 +56:41:00.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:26.62 +57:57:21.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:30.27 +53:48:13.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:54.42 +51:39:12.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:59.77 +55:07:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:29.11 +52:54:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:48.12 +52:45:00.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:47.78 +49:57:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:22.75 +56:30:59.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:40.03 +52:50:54.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:17.08 +56:01:51.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:00.92 +51:32:11.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:33.81 +52:05:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:43.27 +51:15:01.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:04.30 +52:46:31.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:19.91 +51:37:00.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:08.43 +52:00:45.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:30.48 +50:59:05.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:36.00 +53:16:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:02.82 +52:45:15.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:43.19 +54:28:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:22.86 +50:57:27.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:35.27 +52:37:29.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:48:29.28 +54:40:54.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:49:55.72 +53:28:37.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:25.88 +54:13:28.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:17.15 +52:36:29.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:26.37 +51:58:00.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:39.04 +53:51:31.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:53:28.16 +53:32:37.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:00.86 +53:15:51.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:24.39 +53:21:11.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:28.93 +54:05:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:54:48.61 +54:09:11.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:09.34 +53:04:27.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:50.69 +53:44:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:33.64 +53:45:01.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:06.73 +52:12:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:26.06 +51:26:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:26.59 +51:26:22.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:58.97 +53:17:25.0 -- 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:50.24 +53:37:24.2 -- not a known variable star
00:00:55.41 +51:38:18.2 -- not a known variable star
00:01:25.63 +53:19:29.9 -- not a known variable star
00:03:31.23 +49:57:58.4 -- not a known variable star
00:04:13.00 +51:49:48.3 -- not a known variable star
00:04:15.87 +50:02:41.5 -- not a known variable star
00:04:18.78 +51:51:28.6 -- not a known variable star
00:04:32.26 +52:54:14.9 -- not a known variable star
00:04:41.28 +55:32:13.3 -- a known variable star
00:05:11.36 +52:08:40.3 -- not a known variable star
00:05:48.09 +53:57:50.5 -- not a known variable star
00:07:37.81 +53:34:10.0 -- not a known variable star
00:07:59.19 +53:41:22.8 -- a known variable star
00:09:34.15 +53:25:48.0 -- not a known variable star
00:10:28.35 +53:34:40.5 -- not a known variable star
00:11:46.89 +54:49:20.0 -- a known variable star
00:11:48.20 +52:52:43.8 -- not a known variable star
00:12:02.04 +54:02:13.5 -- not a known variable star
00:12:13.17 +52:49:02.5 -- not a known variable star
00:12:16.05 +57:18:49.5 -- a known variable star
00:12:57.96 +50:00:22.6 -- not a known variable star
00:13:38.26 +52:03:14.7 -- not a known variable star
00:14:53.87 +53:15:44.1 -- not a known variable star
00:15:30.65 +52:00:09.6 -- not a known variable star
00:16:25.15 +53:58:12.8 -- not a known variable star
00:20:44.33 +50:11:40.6 -- not a known variable star
00:20:45.67 +50:12:00.8 -- not a known variable star
00:22:04.39 +54:21:20.5 -- not a known variable star
00:22:18.95 +54:07:08.2 -- not a known variable star
00:22:24.89 +53:06:33.1 -- not a known variable star
00:22:44.33 +52:23:06.3 -- not a known variable star
00:22:45.50 +53:12:12.4 -- not a known variable star
00:23:22.91 +55:49:16.0 -- not a known variable star
00:23:24.72 +54:55:51.3 -- not a known variable star
00:24:51.26 +53:02:41.0 -- not a known variable star
00:25:48.32 +54:30:11.3 -- not a known variable star
00:27:57.77 +52:56:17.6 -- not a known variable star
00:27:59.44 +53:40:04.0 -- not a known variable star
00:29:26.06 +55:19:08.2 -- not a known variable star
23:29:17.55 +55:18:44.9 -- not a known variable star
23:29:21.38 +56:41:00.5 -- not a known variable star
23:30:26.62 +57:57:21.1 -- not a known variable star
23:30:30.27 +53:48:13.0 -- not a known variable star
23:31:54.42 +51:39:12.2 -- not a known variable star
23:31:59.77 +55:07:37.1 -- not a known variable star
23:33:29.11 +52:54:08.4 -- not a known variable star
23:33:48.12 +52:45:00.8 -- not a known variable star
23:34:47.78 +49:57:41.5 -- not a known variable star
23:35:22.75 +56:30:59.1 -- not a known variable star
23:36:40.03 +52:50:54.2 -- not a known variable star
23:38:17.08 +56:01:51.2 -- not a known variable star
23:39:00.92 +51:32:11.8 -- a known variable star
23:39:33.81 +52:05:04.0 -- not a known variable star
23:40:43.27 +51:15:01.6 -- not a known variable star
23:41:04.30 +52:46:31.2 -- not a known variable star
23:41:19.91 +51:37:00.2 -- not a known variable star
23:43:08.43 +52:00:45.7 -- not a known variable star
23:43:30.48 +50:59:05.1 -- not a known variable star
23:43:36.00 +53:16:05.4 -- not a known variable star
23:44:02.82 +52:45:15.7 -- not a known variable star
23:46:43.19 +54:28:54.3 -- not a known variable star
23:47:22.86 +50:57:27.1 -- not a known variable star
23:47:35.27 +52:37:29.4 -- not a known variable star
23:48:29.28 +54:40:54.6 -- not a known variable star
23:49:55.72 +53:28:37.1 -- not a known variable star
23:50:25.88 +54:13:28.8 -- not a known variable star
23:51:17.15 +52:36:29.9 -- not a known variable star
23:52:26.37 +51:58:00.1 -- not a known variable star
23:52:39.04 +53:51:31.7 -- not a known variable star
23:53:28.16 +53:32:37.4 -- not a known variable star
23:54:00.86 +53:15:51.5 -- not a known variable star
23:54:24.39 +53:21:11.5 -- not a known variable star
23:54:28.93 +54:05:57.2 -- not a known variable star
23:54:48.61 +54:09:11.2 -- not a known variable star
23:55:09.34 +53:04:27.6 -- not a known variable star
23:55:50.69 +53:44:35.5 -- not a known variable star
23:56:33.64 +53:45:01.9 -- not a known variable star
23:57:06.73 +52:12:25.4 -- not a known variable star
23:58:26.06 +51:26:29.3 -- not a known variable star
23:58:26.59 +51:26:22.2 -- not a known variable star
23:58:58.97 +53:17:25.0 -- not a known variable star
Found 76 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
81 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 81 (excluding asteroids and hot pixels, 76 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)2461214.93973023 -observatory V36
07:44:43.44 +20:41:24.5 Mercury (1.1mag)
08:56:51.51 +19:17:29.4 Venus (-4.0mag)
03:34:12.06 +18:49:21.1 Mars (1.3mag)
08:01:31.48 +20:56:37.7 Jupiter (-1.8mag)
00:53:08.71 +03:08:25.7 Saturn (0.8mag)
04:03:43.44 +20:35:25.3 Uranus (5.8mag)
00:16:48.91 +00:20:18.3 Neptune (7.8mag)
20:32:20.80 -23:10:39.7 Pluto (14.5mag)
13:03:05.56 -11:26:20.0 Moon (-10.8mag)
-rw-r--r-- 1 apache apache 362 Jun 23 07:51 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461214.93973023:
08:01:28.65 +20:56:46.3 Io (6.1mag)
08:01:43.04 +20:55:59.4 Europa (6.3mag)
08:01:19.81 +20:57:20.1 Ganymede (5.6mag)
08:02:00.29 +20:55:01.8 Callisto (6.9mag)
08:00:55.38 +20:35:15.7 Himalia (15.6mag)
08:01:29.78 +20:56:44.8 Thebe (16.6mag)
08:00:30.76 +20:44:36.4 Elara (17.6mag)
08:04:25.70 +20:59:59.2 Pasiphae (17.8mag)
08:07:23.60 +20:59:40.2 Carme (18.9mag)
00:52:57.63 +03:08:30.0 Titan (8.6mag)
00:53:09.24 +03:08:14.9 Rhea (9.9mag)
00:53:15.25 +03:10:32.4 Iapetus (11.3mag)
00:52:59.61 +03:08:51.0 Hyperion (14.6mag)
00:53:31.73 +03:08:08.8 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jun 23 07:51 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461214.93973023:
17:29:41.53 -35:18:53.5 JWST
19:33:50.36 -03:42:25.0 Chandra
10:23:22.83 -57:54:14.8 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jun 23 07:51 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461214.93973023 -observatory V36
18:31:46.68 -33:38:44.8 13.7mag P/2010 H2 (Vales)
06:08:40.00 -67:59:47.0 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
05:54:42.24 +32:10:47.1 17.6mag C/2017 K2 (PANSTARRS)
17:08:45.51 +15:54:23.3 17.9mag C/2021 G2 (ATLAS)
23:42:58.62 -29:53:32.7 15.7mag P/2021 N1 (ZTF)
23:07:55.79 +32:04:30.5 17.2mag C/2022 E2 (ATLAS)
05:52:33.45 +27:00:38.1 16.6mag C/2022 N2 (PANSTARRS)
09:41:21.12 +30:30:15.9 16.7mag C/2022 QE78 (ATLAS)
08:59:12.59 +04:33:07.2 17.8mag C/2022 R6 (PANSTARRS)
18:18:06.63 +21:41:07.8 17.8mag C/2023 A3 (Tsuchinshan-ATLAS)
15:14:39.11 -11:06:12.3 17.6mag P/2023 B1 (PANSTARRS)
22:06:02.38 +67:18:29.7 17.8mag C/2023 H5 (Lemmon)
17:08:36.60 -08:16:07.6 13.7mag C/2023 R1 (PANSTARRS)
13:18:49.21 +79:23:18.8 18.0mag C/2023 X2 (Lemmon)
07:32:53.09 +64:53:35.9 17.8mag C/2024 A1 (ATLAS)
07:09:41.18 +29:01:01.2 14.1mag C/2024 E1 (Wierzchos)
15:26:09.13 +14:37:31.9 17.5mag C/2024 G6 (ATLAS)
20:00:29.56 +35:26:56.9 13.9mag C/2024 J3 (ATLAS)
22:01:53.71 +43:10:41.7 18.0mag C/2024 R4 (PANSTARRS)
04:33:14.25 -14:45:43.9 15.9mag C/2024 T5 (ATLAS)
06:19:54.47 +31:53:28.5 17.9mag C/2025 J1 (Borisov)
11:32:12.14 +51:48:40.6 17.9mag C/2025 L1 (ATLAS)
07:00:50.62 -11:39:06.6 15.4mag C/2025 R3 (PANSTARRS)
09:37:57.30 +23:01:43.2 17.8mag C/2025 V2 (Rankin)
12:40:36.56 +04:29:24.4 17.1mag C/2025 Y1 (ATLAS)
17:40:31.06 +77:48:59.0 17.6mag C/2026 A2 (Bok)
02:24:56.54 +44:23:26.1 16.4mag C/2026 B2 (Sun-Gao)
11:16:20.27 +00:53:11.0 16.7mag A/2026 E1
20:50:46.77 -10:30:12.6 8.0mag 10P/Tempel
11:06:30.20 -01:17:27.5 16.1mag 29P/Schwassmann-Wachmann
03:35:05.78 +27:35:52.2 17.8mag 47P/Ashbrook-Jackson
09:32:26.86 +19:16:31.1 16.9mag 63P/Wild
00:38:44.70 -05:33:22.4 15.6mag 65P/Gunn
07:32:58.82 +34:23:59.6 17.3mag 76P/West-Kohoutek-Ikemura
03:46:13.91 +18:55:09.8 13.8mag 78P/Gehrels
01:52:06.38 +07:53:37.5 15.9mag 88P/Howell
05:43:24.73 +30:56:52.6 15.4mag 93P/Lovas
03:27:44.74 +29:44:44.0 17.2mag 114P/Wiseman-Skiff
07:27:21.12 +32:13:38.7 15.4mag 123P/West-Hartley
10:17:10.44 +08:10:37.8 16.6mag 124P/Mrkos
04:24:10.51 +20:08:29.6 16.3mag 128P/Shoemaker-Holt
05:03:40.74 +19:35:41.0 17.8mag 131P/Mueller
06:58:53.01 +16:25:11.7 16.6mag 141P/Machholz
07:02:48.29 +17:47:48.4 16.5mag 141P-A/Machholz
06:07:02.34 +17:24:10.3 13.4mag 141P-D/Machholz
03:07:49.51 -22:46:44.6 16.2mag 161P/Hartley-IRAS
04:33:06.11 +29:20:59.1 15.1mag 162P/SidingSpring
19:30:17.05 +06:53:38.4 16.0mag 169P/NEAT
00:58:41.48 +05:13:30.4 17.8mag 220P/McNaught
16:41:56.93 -08:04:34.0 16.7mag 235P/LINEAR
08:08:44.68 +34:39:11.7 17.7mag 240P/NEAT
01:12:52.71 +04:15:03.6 16.0mag 260P/McNaught
04:47:01.55 +34:56:51.5 17.5mag 295P/LINEAR
15:09:33.94 +07:20:58.9 17.5mag 391P/Kowalski
08:19:45.29 +20:17:53.6 17.9mag 450P/LONEOS
07:24:45.79 +40:34:06.3 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.7K Jun 23 07:51 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 23 07:51 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
15:41:11.68 +59:18:26.8 TCP J15411168+5918268 2026-04-12.9625 19.2mag
00:43:35.02 +41:46:28.0 PNV J00433502+4146280 2026-04-23.056 15.9mag
00:42:55.64 +41:14:12.2 PNV J00425564+4114122 2026-04-24.042 16.2mag
21:14:03.38 +56:46:44.1 TCP J21140338+5646441 2026-05-05.3534 16.7mag
15:03:05.19 +22:02:04.1 TCP J15030519+2202041 2026-05-08.3260 13.9mag
07:15:18.25 +47:53:16.7 TCP J07151825+4753167 2026-05-09.1599 14.4mag
16:00:18.44 -22:30:10.6 TCP J16001844-2230106 2026-05-09.6135 13.3mag
00:42:47.45 +41:16:58.5 PNV J00424745+4116585 2026-05-10.030 16.8mag
09:55:02.89 +69:02:13.8 PNV J09550289+6902138 2026-05-18.925 20.7mag
00:43:01.82 +41:18:16.6 PNV J00430182+4118166 2026-05-21.8651 18.83Cmag
00:42:51.20 +41:16:59.4 PNV J00425120+4116594 2022-10-26.135 19.3mag
12:24:25.10 +28:47:12.0 TCP J12242510+2847120 2026-05-31.6015 14.8mag
00:56:07.13 +43:01:40.6 TCP J00560713+4301406 2026-06-01.4135 12.2mag
00:42:41.64 +41:15:16.2 PNV J00424164+4115162 2026-06-02.029 17.4mag
00:42:38.68 +41:15:58.2 PNV J00423868+4115582 2026-06-05.1224 19.97Umag
19:00:42.95 -48:31:01.7 PNV J19004295-4831017 2026-05-25.0752 14.2mag
09:55:21.28 +69:02:52.6 PNV J09552128+6902526 2026-06-13.933 18.9mag
19:51:21.42 +37:06:40.0 TCP J19512142+3706400 2026-06-17.2942 16.8mag
19:57:03.87 +37:41:46.4 TCP J19570387+3741464 2026-06-18.2638 17.5mag
-rw-r--r-- 1 apache apache 189K Jun 23 07:51 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
14:21:04.130 +03:12:44.02 AT 2026pfu 2026-06-02.73 20.7
14:12:56.050 -00:47:40.71 AT 2026pft 2026-06-02.72 20.75
14:00:08.000 -00:22:03.52 AT 2026pfs 2026-06-02.72 21.39
13:48:40.890 +01:37:22.75 AT 2026pfr 2026-06-02.72 20.72
13:49:23.100 -00:28:17.60 AT 2026pfq 2026-06-02.71 21.6
13:40:58.320 -00:10:56.98 AT 2026pfp 2026-06-02.71 20.87
13:30:45.650 +03:46:42.75 AT 2026pfo 2026-06-02.71 21.48
13:09:47.460 +01:51:23.52 AT 2026pfn 2026-06-02.70 20.7
13:04:27.660 +01:03:38.69 AT 2026pfm 2026-06-02.70 20.61
13:02:48.460 -00:02:57.35 AT 2026pfl 2026-06-02.70 20.42
13:32:29.920 -00:51:10.16 AT 2026pfk 2026-06-08.70 21.85
22:56:19.417 -34:42:19.31 AT 2026pfj 2026-05-18.41 20.44
17:18:30.019 +34:15:44.23 AT 2026pfi 2026-06-14.39 21
14:56:10.823 +09:51:29.24 AT 2026pfh 2026-05-12.12 20.36
14:14:37.201 +14:25:05.82 AT 2026pfg 2026-06-14.19 19.2685
23:15:33.309 +78:21:30.20 AT 2026pff 2026-06-04.38 20.0549
21:04:19.065 -12:09:15.14 AT 2026pfe 2026-05-14.45 20.4546
22:12:18.808 +78:44:00.16 AT 2026pfd 2026-06-04.38 20.0909
20:22:23.781 +14:16:24.43 AT 2026pfc 2026-06-11.40 20.7598
22:15:43.151 +19:13:42.63 AT 2026pfb 2026-06-14.54 20.6
-rw-r--r-- 1 apache apache 30K Jun 23 07:51 tns_transients_list.txt
