This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a
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 24.3312 2461215.8312 11.01 00:20:46.35 +50:11:43.8
117.91594 -12.37735 galactic Cas Second-epoch detections are separated by 3.7" 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:46.35 +50:11:43.8 (user input) | T | P | (position from user input) J-Ks=0.721+/-0.254 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:46.35 +50:11:43.8: 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:46.35 +50:11:43.8: 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 24.3312* 00 20 46.35 +50 11 43.8 11.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,11.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 11.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 11.55 00:14:54.68 +53:15:41.5
117.41310 -9.21837 galactic Cas Second-epoch detections are separated by 5.7" 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 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:54.68 +53:15:41.5: 12.87 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:54.68 +53:15:41.5: 12.88 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.87 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 14 54.68 +53 15 41.5 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 419245673457567232,2461215.8312,11.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 419245673457567232 20260624.3312 11.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 24.3312 2461215.8312 11.79 00:17:35.62 +51:28:57.1
117.57516 -11.03687 galactic Cas Second-epoch detections are separated by 5.6" 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:17:35.62 +51:28:57.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 00:17:35.62 +51:28:57.1: 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:17:35.62 +51:28:57.1: 15.13 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.13 +/- 0.24
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 17 35.62 +51 28 57.1 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
target,2461215.8312,11.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 11.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 11.99 00:03:57.95 +54:07:59.6
115.94125 -8.09293 galactic Cas Second-epoch detections are separated by 6.1" 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.0029+54.1348 | 00:03:59.75 +54:07:47.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:03:57.95 +54:07:59.6: 13.19 +/- 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:03:57.95 +54:07:59.6: 13.07 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.13 +/- 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 24.3312* 00 03 57.95 +54 07 59.6 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.0029+54.1348,2461215.8312,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.0029+54.1348 20260624.3312 11.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 24.3312 2461215.8312 11.97 00:02:38.42 +53:39:39.6
115.65793 -8.52015 galactic Cas Second-epoch detections are separated by 5.4" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 396262380046129408 | 00:02:40.18 +53:39:02.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:02:38.42 +53:39:39.6: 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:02:38.42 +53:39:39.6: 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 24.3312* 00 02 38.42 +53 39 39.6 12.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 396262380046129408,2461215.8312,11.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 396262380046129408 20260624.3312 11.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.05 23:46:43.93 +51:45:27.9
112.85186 -9.84312 galactic Cas Second-epoch detections are separated by 6.9" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:46:43.93 +51:45:27.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:46:43.93 +51:45:27.9: 15.72 +/- 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:46:43.93 +51:45:27.9: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 46 43.93 +51 45 27.9 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
target,2461215.8312,12.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.04 00:08:00.55 +52:54:45.0
116.32052 -9.40086 galactic Cas Second-epoch detections are separated by 3.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 | target | 00:08:00.55 +52:54:45.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:08:00.55 +52:54:45.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 00:08:00.55 +52:54:45.0: 15.84 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 08 00.55 +52 54 45.0 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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 12.06 23:56:10.80 +50:38:48.7
114.05073 -11.26956 galactic Cas Second-epoch detections are separated by 6.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 | 23:56:10.80 +50:38:48.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:56:10.80 +50:38:48.7: 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:56:10.80 +50:38:48.7: 15.66 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 56 10.80 +50 38 48.7 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.11 00:00:59.75 +53:46:33.9
115.43911 -8.36022 galactic Cas Second-epoch detections are separated by 6.1" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 396276428875775232 | 00:01:01.08 +53:45:51.6 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G5 (LAMOST DR5)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:00:59.75 +53:46:33.9: 15.71 +/- 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:59.75 +53:46:33.9: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 00 59.75 +53 46 33.9 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 396276428875775232,2461215.8312,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 396276428875775232 20260624.3312 12.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 24.3312 2461215.8312 12.14 23:43:37.78 +52:09:44.1
112.48902 -9.32926 galactic Cas Second-epoch detections are separated by 2.1" 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:43:37.78 +52:09:44.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:37.78 +52:09:44.1: 15.72 +/- 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:37.78 +52:09:44.1: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 43 37.78 +52 09 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
target,2461215.8312,12.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 20260624.3312 12.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 24.3312 2461215.8312 12.11 00:02:33.07 +54:00:25.4
115.71142 -8.17792 galactic Cas Second-epoch detections are separated by 4.9" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 396297186461775744 | 00:02:34.80 +54:00:09.3 (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:02:33.07 +54:00:25.4: 14.02 +/- 0.07 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:33.07 +54:00:25.4: 13.92 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.97 +/- 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 24.3312* 00 02 33.07 +54 00 25.4 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 396297186461775744,2461215.8312,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 396297186461775744 20260624.3312 12.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 24.3312 2461215.8312 12.15 23:55:40.48 +52:35:18.8
114.40114 -9.35711 galactic Cas Second-epoch detections are separated by 7.0" 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:55:40.48 +52:35:18.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:55:40.48 +52:35:18.8: 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:55:40.48 +52:35:18.8: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 55 40.48 +52 35 18.8 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.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 24.3312 2461215.8312 12.11 23:51:16.81 +52:09:16.1
113.63927 -9.62853 galactic Cas Second-epoch detections are separated by 6.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 | ATO J357.8125+52.1652 | 23:51:16.81 +52:09:16.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:51:16.81 +52:09:16.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:51:16.81 +52:09:16.1: 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 24.3312* 23 51 16.81 +52 09 16.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
ATO J357.8125+52.1652,2461215.8312,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.8125+52.1652 20260624.3312 12.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 24.3312 2461215.8312 12.07 00:20:14.58 +50:44:30.1
117.89882 -11.82495 galactic Cas Second-epoch detections are separated by 5.7" 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:14.58 +50:44:30.1 (user input) | T | P | (position from user input) J-Ks=0.934+/- (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:14.58 +50:44:30.1: 13.20 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:14.58 +50:44:30.1: 13.31 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.25 +/- 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 24.3312* 00 20 14.58 +50 44 30.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
target,2461215.8312,12.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.12 00:02:02.38 +53:59:18.7
115.63331 -8.18172 galactic Cas Second-epoch detections are separated by 8.3" and 3.4 pix
The object was found in VSX24" NSVS J0002034+535901
Type: SR
# Max. Min./Amp. JD0 Period
14.378 g Y 1.167 g 2458357.13120 216.381785400000
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:02:02.38 +53:59:18.7: 13.92 +/- 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:02:02.38 +53:59:18.7: 13.87 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.89 +/- 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 24.3312* 00 02 02.38 +53 59 18.7 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0002034+535901,2461215.8312,12.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0002034+535901 20260624.3312 12.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.16 23:52:20.14 +50:08:57.9
113.32778 -11.61697 galactic Cas Second-epoch detections are separated by 7.0" 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:52:20.14 +50:08:57.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:52:20.14 +50:08:57.9: 15.58 +/- 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:20.14 +50:08:57.9: 15.61 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 52 20.14 +50 08 57.9 12.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.11 00:04:14.31 +50:01:22.7
115.20867 -12.13965 galactic Cas Second-epoch detections are separated by 6.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 | 00:04:14.31 +50:01:22.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:04:14.31 +50:01:22.7: 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 00:04:14.31 +50:01:22.7: 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 24.3312* 00 04 14.31 +50 01 22.7 12.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.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 20260624.3312 12.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 24.3312 2461215.8312 7.60 23:58:27.05 +51:26:14.3
114.57671 -10.57280 galactic Cas Second-epoch detections are separated by 3.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 | 23:58:27.05 +51:26:14.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:27.05 +51:26:14.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 23:58:27.05 +51:26:14.3: 15.47 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.47 +/- 0.33
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 58 27.05 +51 26 14.3 7.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,2461215.8312,7.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 20260624.3312 7.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 24.3312 2461215.8312 7.53 00:23:11.74 +55:47:35.3
118.94086 -6.85960 galactic Cas Second-epoch detections are separated by 3.5" and 3.2 pix
The object was found in VSX21" T Cas
Type: M
# Max. Min./Amp. JD0 Period
6.900 V 12.400 V 2459170.00000 443.500000000000 M6e-M9.0e
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:23:11.74 +55:47:35.3: 9.18 +/- 0.00 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:11.74 +55:47:35.3: 9.22 +/- 0.00 detection
Forced photometry reference-image weighted average: 9.20 +/- 0.00
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 23 11.74 +55 47 35.3 7.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
T Cas,2461215.8312,7.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
T Cas 20260624.3312 7.53CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 10.55 23:38:16.00 +56:01:54.0
112.78625 -5.39199 galactic Cas Second-epoch detections are separated by 3.4" and 3.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:38:16.00 +56:01:54.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:38:16.00 +56:01:54.0: 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 23:38:16.00 +56:01:54.0: 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 24.3312* 23 38 16.00 +56 01 54.0 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,2461215.8312,10.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 20260624.3312 10.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 24.3312 2461215.8312 14.59 00:01:08.45 +56:27:05.4
115.98675 -5.74050 galactic Cas Second-epoch detections are separated by 2.1" 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 J000.2640+56.4465 | 00:01:08.45 +56:27:05.4 (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:01:08.45 +56:27:05.4: 15.60 +/- 0.30 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:01:08.45 +56:27:05.4: 15.58 +/- 0.29 detection
Forced photometry reference-image weighted average: 15.59 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 01 08.45 +56 27 05.4 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J000.2640+56.4465,2461215.8312,14.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.2640+56.4465 20260624.3312 14.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.66 23:42:06.30 +55:02:24.9
113.03851 -6.49415 galactic Cas Second-epoch detections are separated by 5.8" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:42:06.30 +55:02:24.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:42:06.30 +55:02:24.9: 15.83 +/- 0.33 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:42:06.30 +55:02:24.9: 15.64 +/- 0.27 detection
Forced photometry reference-image weighted average: 15.72 +/- 0.21
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 42 06.30 +55 02 24.9 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.18 00:08:07.20 +54:56:34.4
116.68417 -7.40252 galactic Cas Second-epoch detections are separated by 1.8" and 3.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 J002.0428+54.9424 | 00:08:07.20 +54:56:34.4 (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:08:07.20 +54:56:34.4: 15.61 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:08:07.20 +54:56:34.4: 15.80 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.61 +/- 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 24.3312* 00 08 07.20 +54 56 34.4 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.0428+54.9424,2461215.8312,14.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.0428+54.9424 20260624.3312 14.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.48 23:43:07.09 +53:23:28.1
112.74114 -8.12342 galactic Cas Second-epoch detections are separated by 3.5" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:07.09 +53:23:28.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:07.09 +53:23:28.1: 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:43:07.09 +53:23:28.1: 15.94 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 43 07.09 +53 23 28.1 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.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 20260624.3312 14.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 24.3312 2461215.8312 14.20 00:02:59.15 +51:30:26.5
115.29502 -10.64451 galactic Cas Second-epoch detections are separated by 7.8" and 3.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:02:59.15 +51:30:26.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:02:59.15 +51:30:26.5: 15.89 +/- 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:02:59.15 +51:30:26.5: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 02 59.15 +51 30 26.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,2461215.8312,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.29 23:31:33.68 +56:51:42.4
112.14098 -4.32709 galactic Cas Second-epoch detections are separated by 4.1" and 3.4 pix
The object was found in VSX 6" Gaia DR3 1998573081703142144
Type: VAR
# Max. Min./Amp. JD0 Period
17.340 G 17.390 G 0.017769500000 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:31:33.68 +56:51:42.4: 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:33.68 +56:51:42.4: 15.22 +/- 0.22 detection
Forced photometry reference-image weighted average: 15.22 +/- 0.22
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 31 33.68 +56 51 42.4 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998573081703142144,2461215.8312,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998573081703142144 20260624.3312 14.29CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.12 23:42:27.86 +53:37:18.0
112.70822 -7.87536 galactic Cas Second-epoch detections are separated by 4.0" 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:42:27.86 +53:37:18.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:42:27.86 +53:37:18.0: 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:42:27.86 +53:37:18.0: 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 24.3312* 23 42 27.86 +53 37 18.0 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.12CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.31 23:30:46.10 +56:37:26.0
111.96409 -4.52025 galactic Cas Second-epoch detections are separated by 3.4" and 3.8 pix
The object was found in VSX16" ZTF J233045.95+563742.0
Type: BY
# Max. Min./Amp. JD0 Period
16.371 r Y 0.041 r 2458300.93120 5.927110400000
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:30:46.10 +56:37:26.0: 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:30:46.10 +56:37:26.0: 15.76 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 46.10 +56 37 26.0 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ZTF J233045.95+563742.0,2461215.8312,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ZTF J233045.95+563742.0 20260624.3312 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.15 23:32:21.78 +54:31:58.0
111.53809 -6.58028 galactic Cas Second-epoch detections are separated by 2.4" 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 | Gaia DR3 1994352262721849728 | 23:32:16.85 +54:32:10.7 (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:32:21.78 +54:31:58.0: 15.72 +/- 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:32:21.78 +54:31:58.0: 15.33 +/- 0.27 detection
Forced photometry reference-image weighted average: 15.33 +/- 0.27
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 32 21.78 +54 31 58.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1994352262721849728,2461215.8312,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
Gaia DR3 1994352262721849728 20260624.3312 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 24.3312 2461215.8312 14.20 23:30:43.51 +51:31:34.5
110.36929 -9.36600 galactic Cas Second-epoch detections are separated by 7.2" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:43.51 +51:31:34.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:30:43.51 +51:31:34.5: 15.68 +/- 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:43.51 +51:31:34.5: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 43.51 +51 31 34.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,2461215.8312,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.88 00:00:11.35 +53:25:56.9
115.25171 -8.67333 galactic Cas Second-epoch detections are separated by 2.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 | Gaia DR3 396173525762390272 | 00:00:14.21 +53:26:35.8 (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:00:11.35 +53:25:56.9: 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:00:11.35 +53:25:56.9: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 00 11.35 +53 25 56.9 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 396173525762390272,2461215.8312,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 396173525762390272 20260624.3312 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 24.3312 2461215.8312 14.13 23:36:59.90 +53:05:01.7
111.76641 -8.16657 galactic Cas Second-epoch detections are separated by 7.4" and 3.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 J354.2682+53.0798 | 23:36:59.90 +53:05:01.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:36:59.90 +53:05:01.7: 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 23:36:59.90 +53:05:01.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 24.3312* 23 36 59.90 +53 05 01.7 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J354.2682+53.0798,2461215.8312,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J354.2682+53.0798 20260624.3312 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.08 23:30:35.20 +53:35:49.8
110.99921 -7.39095 galactic Cas Second-epoch detections are separated by 1.6" and 3.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:35.20 +53:35:49.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:30:35.20 +53:35:49.8: 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 23:30:35.20 +53:35:49.8: 15.78 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 35.20 +53 35 49.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 14.10 23:36:31.48 +54:23:09.4
112.07620 -6.89922 galactic Cas Second-epoch detections are separated by 5.9" and 3.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:36:31.48 +54:23:09.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:36:31.48 +54:23:09.4: 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:36:31.48 +54:23:09.4: 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 24.3312* 23 36 31.48 +54 23 09.4 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.01 23:42:55.34 +53:06:04.8
112.63513 -8.39515 galactic Cas Second-epoch detections are separated by 4.3" and 3.7 pix
The object was found in VSX21" Gaia DR3 1993097204558103040
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.480 G 13.510 G A
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:42:55.34 +53:06:04.8: 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:42:55.34 +53:06:04.8: 15.57 +/- 0.28 detection
Forced photometry reference-image weighted average: 15.57 +/- 0.28
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 42 55.34 +53 06 04.8 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993097204558103040,2461215.8312,14.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993097204558103040 20260624.3312 14.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.91 23:35:18.02 +54:24:57.3
111.91322 -6.81885 galactic Cas Second-epoch detections are separated by 3.7" and 3.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:18.02 +54:24:57.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:35:18.02 +54:24:57.3: 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:35:18.02 +54:24:57.3: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 35 18.02 +54 24 57.3 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.59 00:08:06.73 +54:49:22.0
116.66262 -7.52072 galactic Cas Second-epoch detections are separated by 6.4" and 3.0 pix
The object was found in VSX11" Gaia DR3 420232042770425856
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
14.970 G 15.010 G A
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:08:06.73 +54:49:22.0: 15.17 +/- 0.19 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:08:06.73 +54:49:22.0: 15.45 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.27 +/- 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 24.3312* 00 08 06.73 +54 49 22.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 420232042770425856,2461215.8312,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 420232042770425856 20260624.3312 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 24.3312 2461215.8312 13.84 23:38:58.59 +51:32:10.6
111.61525 -9.73626 galactic Cas Second-epoch detections are separated by 1.9" and 3.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:38:58.59 +51:32:10.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:38:58.59 +51:32:10.6: 15.78 +/- 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:58.59 +51:32:10.6: 15.73 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 38 58.59 +51 32 10.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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.77 23:44:02.93 +52:45:35.2
112.70993 -8.76933 galactic Cas Second-epoch detections are separated by 4.5" 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 | ATO J356.0324+52.7552 | 23:44:02.93 +52:45:35.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 23:44:02.93 +52:45:35.2: 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 23:44:02.93 +52:45:35.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 24.3312* 23 44 02.93 +52 45 35.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.0324+52.7552,2461215.8312,13.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J356.0324+52.7552 20260624.3312 13.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.38 00:08:49.88 +50:55:59.7
116.10778 -11.37309 galactic Cas Second-epoch detections are separated by 2.8" and 3.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 J002.1833+50.9491 | 00:08:47.04 +50:56:32.5 (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:08:49.88 +50:55:59.7: 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:08:49.88 +50:55:59.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 24.3312* 00 08 49.88 +50 55 59.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
ATO J002.1833+50.9491,2461215.8312,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.1833+50.9491 20260624.3312 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 24.3312 2461215.8312 13.71 23:31:18.09 +55:42:25.5
111.75245 -5.41556 galactic Cas Second-epoch detections are separated by 1.7" and 3.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:31:18.09 +55:42:25.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:31:18.09 +55:42:25.5: 15.23 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:31:18.09 +55:42:25.5: 14.92 +/- 0.19 detection
Forced photometry reference-image weighted average: 15.03 +/- 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 24.3312* 23 31 18.09 +55 42 25.5 13.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.63 23:35:59.94 +56:49:21.3
112.71051 -4.54456 galactic Cas Second-epoch detections are separated by 5.0" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 1998618844574643712 | 23:35:54.93 +56:49:07.7 (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:35:59.94 +56:49:21.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:35:59.94 +56:49:21.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 24.3312* 23 35 59.94 +56 49 21.3 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998618844574643712,2461215.8312,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998618844574643712 20260624.3312 13.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.76 23:30:04.32 +55:55:29.3
111.65491 -5.15518 galactic Cas Second-epoch detections are separated by 1.0" and 3.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:30:04.32 +55:55: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:30:04.32 +55:55:29.3: 15.69 +/- 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:04.32 +55:55:29.3: 15.69 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 04.32 +55 55 29.3 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.45 23:36:59.39 +56:58:25.7
112.88401 -4.43848 galactic Cas Second-epoch detections are separated by 4.3" and 3.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:36:59.39 +56:58:25.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:36:59.39 +56:58:25.7: 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 23:36:59.39 +56:58:25.7: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 36 59.39 +56 58 25.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,2461215.8312,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.41 23:55:25.83 +51:47:36.6
114.18821 -10.12488 galactic Cas Second-epoch detections are separated by 7.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 J358.8546+51.8043 | 23:55:25.83 +51:47:36.6 (user input) | CBH (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:55:25.83 +51:47:36.6: 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:55:25.83 +51:47:36.6: 15.97 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 55 25.83 +51 47 36.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J358.8546+51.8043,2461215.8312,13.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J358.8546+51.8043 20260624.3312 13.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.06 00:01:49.28 +50:18:52.1
114.87711 -11.77968 galactic Cas Second-epoch detections are separated by 2.4" 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 | ATO J000.4379+50.3119 | 00:01:49.28 +50:18:52.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:01:49.28 +50:18:52.1: 15.22 +/- 0.18 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:01:49.28 +50:18:52.1: 15.27 +/- 0.20 detection
Forced photometry reference-image weighted average: 15.24 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 01 49.28 +50 18 52.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
ATO J000.4379+50.3119,2461215.8312,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J000.4379+50.3119 20260624.3312 13.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.88 23:31:53.16 +51:39:04.1
110.58218 -9.30293 galactic Cas Second-epoch detections are separated by 2.9" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:53.16 +51:39:04.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:31:53.16 +51:39:04.1: 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 23:31:53.16 +51:39:04.1: 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 24.3312* 23 31 53.16 +51 39 04.1 12.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.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 20260624.3312 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.79 23:29:17.10 +55:18:52.3
111.35749 -5.70027 galactic Cas Second-epoch detections are separated by 0.4" and 3.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 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.10 +55:18:52.3: 15.58 +/- 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:17.10 +55:18:52.3: 15.54 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 29 17.10 +55 18 52.3 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997633755177085440,2461215.8312,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1997633755177085440 20260624.3312 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.47 00:22:29.68 +50:18:56.0
118.21026 -12.29066 galactic Cas Second-epoch detections are separated by 1.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 | 00:22:29.68 +50:18:56.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:22:29.68 +50:18:56.0: 15.70 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:22:29.68 +50:18:56.0: 15.84 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.70 +/- 0.31
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 22 29.68 +50 18 56.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
target,2461215.8312,12.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 11.78 23:37:54.53 +52:05:24.9
111.61344 -9.15823 galactic Cas Second-epoch detections are separated by 0.5" and 3.7 pix
The object was found in VSX 9" Gaia DR3 1992894516459719040
Type: DSCT|GDOR
# Max. Min./Amp. JD0 Period
13.730 G 13.760 G 0.059938500000 A
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:37:54.53 +52:05:24.9: 14.20 +/- 0.09 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:37:54.53 +52:05:24.9: 14.25 +/- 0.09 detection
Forced photometry reference-image weighted average: 14.22 +/- 0.06
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 37 54.53 +52 05 24.9 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 1992894516459719040,2461215.8312,11.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1992894516459719040 20260624.3312 11.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 11.66 23:39:01.86 +52:18:14.9
111.84162 -9.00155 galactic Cas Second-epoch detections are separated by 5.4" and 3.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:39:01.86 +52:18:14.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:39:01.86 +52:18:14.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 23:39:01.86 +52:18:14.9: 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 24.3312* 23 39 01.86 +52 18 14.9 11.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,11.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 20260624.3312 11.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 24.3312 2461215.8312 11.62 00:14:55.44 +53:15:47.3
117.41523 -9.21705 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 | 00:14:55.44 +53:15:47.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:14:55.44 +53:15:47.3: 13.94 +/- 0.08 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:55.44 +53:15:47.3: 14.02 +/- 0.08 detection
Forced photometry reference-image weighted average: 13.97 +/- 0.06
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 14 55.44 +53 15 47.3 11.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,11.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 11.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.77 23:31:40.28 +57:27:22.9
112.33672 -3.76529 galactic Cas Second-epoch detections are separated by 6.9" and 3.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 1998859607561085696 | 23:31:43.20 +57:26:57.9 (Gaia DR3) | T | P | Gaia3var=NOT_AVAILABLE SpType: G0 (LAMOST DR5) J-Ks=0.800+/-0.120 (K)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:31:40.28 +57:27:22.9: 15.50 +/- 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:31:40.28 +57:27:22.9: 15.70 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.50 +/- 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 24.3312* 23 31 40.28 +57 27 22.9 12.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998859607561085696,2461215.8312,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998859607561085696 20260624.3312 12.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.12 23:31:59.91 +55:07:36.7
111.66918 -5.99829 galactic Cas Second-epoch detections are separated by 2.0" and 3.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | Gaia DR3 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.91 +55:07:36.7: 15.08 +/- 0.21 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.91 +55:07:36.7: 14.61 +/- 0.14 detection
Forced photometry reference-image weighted average: 14.76 +/- 0.12
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 31 59.91 +55 07 36.7 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1997431032719635200,2461215.8312,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
Gaia DR3 1997431032719635200 20260624.3312 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 24.3312 2461215.8312 12.99 23:41:55.17 +52:45:28.4
112.39515 -8.68579 galactic Cas Second-epoch detections are separated by 1.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:41:55.17 +52:45:28.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:41:55.17 +52:45:28.4: 14.66 +/- 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:41:55.17 +52:45:28.4: 14.54 +/- 0.11 detection
Forced photometry reference-image weighted average: 14.59 +/- 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 24.3312* 23 41 55.17 +52 45 28.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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.21 00:07:39.42 +53:34:06.0
116.38114 -8.74564 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 | 00:07:39.42 +53:34:06.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:39.42 +53:34:06.0: 14.48 +/- 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:39.42 +53:34:06.0: 14.58 +/- 0.12 detection
Forced photometry reference-image weighted average: 14.53 +/- 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 24.3312* 00 07 39.42 +53 34 06.0 13.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.29 23:47:36.08 +52:37:54.3
113.20385 -9.03006 galactic Cas Second-epoch detections are separated by 2.8" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:47:36.08 +52:37:54.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:47:36.08 +52:37:54.3: 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:47:36.08 +52:37:54.3: 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 24.3312* 23 47 36.08 +52 37 54.3 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 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 24.3312 2461215.8312 13.31 23:43:07.15 +52:00:53.7
112.37294 -9.45067 galactic Cas Second-epoch detections are separated by 2.4" and 4.0 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:43:07.15 +52:00:53.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:07.15 +52:00:53.7: 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:43:07.15 +52:00:53.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 24.3312* 23 43 07.15 +52 00 53.7 13.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.41 23:39:32.32 +52:05:01.1
111.85495 -9.23500 galactic Cas Second-epoch detections are separated by 7.0" and 3.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:39:32.32 +52:05:01.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:39:32.32 +52:05:01.1: 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 23:39:32.32 +52:05:01.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 24.3312* 23 39 32.32 +52 05 01.1 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.38 23:38:55.92 +51:35:18.2
111.62336 -9.68430 galactic Cas Second-epoch detections are separated by 1.1" 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:38:55.92 +51:35: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 23:38:55.92 +51:35:18.2: 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 23:38:55.92 +51:35:18.2: 15.11 +/- 0.18 detection
Forced photometry reference-image weighted average: 15.11 +/- 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 24.3312* 23 38 55.92 +51 35 18.2 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.47 23:30:03.60 +54:40:05.4
111.26052 -6.34899 galactic Cas Second-epoch detections are separated by 3.5" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:03.60 +54:40: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:30:03.60 +54:40:05.4: 15.68 +/- 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:30:03.60 +54:40:05.4: 15.73 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.68 +/- 0.34
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 03.60 +54 40 05.4 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.43 23:33:33.56 +50:54:49.4
110.60761 -10.08499 galactic Cas Second-epoch detections are separated by 4.4" 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:33.56 +50:54:49.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:33.56 +50:54:49.4: 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:33:33.56 +50:54:49.4: 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 24.3312* 23 33 33.56 +50 54 49.4 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.45 23:41:05.57 +52:46:43.3
112.27907 -8.63194 galactic Cas Second-epoch detections are separated by 5.6" and 3.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J355.2845+52.7877 | 23:41:05.57 +52:46:43.3 (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:41:05.57 +52:46:43.3: 14.44 +/- 0.10 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:41:05.57 +52:46:43.3: 14.48 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.46 +/- 0.07
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 41 05.57 +52 46 43.3 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.2845+52.7877,2461215.8312,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J355.2845+52.7877 20260624.3312 13.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.44 00:04:16.40 +50:02:31.6
115.21793 -12.12189 galactic Cas Second-epoch detections are separated by 2.7" 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:04:16.40 +50:02:31.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:16.40 +50:02:31.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:04:16.40 +50:02:31.6: 15.92 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 04 16.40 +50 02 31.6 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.44CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.45 00:05:01.55 +51:13:22.9
115.55963 -10.98315 galactic Cas Second-epoch detections are separated by 5.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.2384+51.2194 | 00:05:01.55 +51:13:22.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:05:01.55 +51:13:22.9: 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 00:05:01.55 +51:13:22.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 24.3312* 00 05 01.55 +51 13 22.9 13.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J001.2384+51.2194,2461215.8312,13.45,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J001.2384+51.2194 20260624.3312 13.45CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.73 23:34:21.05 +54:04:08.8
111.67688 -7.10951 galactic Cas Second-epoch detections are separated by 1.0" and 3.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:34:21.05 +54:04:08.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:34:21.05 +54:04:08.8: 15.58 +/- 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:21.05 +54:04:08.8: 15.53 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 34 21.05 +54 04 08.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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.55 00:19:42.93 +50:48:25.6
117.82261 -11.74967 galactic Cas Second-epoch detections are separated by 1.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:19:42.93 +50:48:25.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:19:42.93 +50:48:25.6: 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:19:42.93 +50:48:25.6: 15.90 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 19 42.93 +50 48 25.6 13.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.62 23:51:10.27 +51:26:07.1
113.45126 -10.32365 galactic Cas Second-epoch detections are separated by 0.7" and 3.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J357.7886+51.4251 | 23:51:10.27 +51:26:07.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:51:10.27 +51:26:07.1: 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:51:10.27 +51:26:07.1: 15.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 51 10.27 +51 26 07.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 J357.7886+51.4251,2461215.8312,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
ATO J357.7886+51.4251 20260624.3312 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 24.3312 2461215.8312 13.73 23:33:32.02 +56:43:57.2
112.36018 -4.53165 galactic Cas Second-epoch detections are separated by 8.1" 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:32.02 +56:43:57.2 (user input) | T | P | (position from user input) J-Ks=0.917+/-0.145 (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:33:32.02 +56:43:57.2: 15.69 +/- 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:32.02 +56:43:57.2: 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 24.3312* 23 33 32.02 +56 43 57.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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.72 23:36:57.43 +55:34:22.6
112.47845 -5.77985 galactic Cas Second-epoch detections are separated by 1.3" and 3.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:36:57.43 +55:34:22.6 (user input) | T | P | (position from user input) J-Ks=1.154+/-0.254 (M)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:36:57.43 +55:34:22.6: 15.65 +/- 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:57.43 +55:34:22.6: 15.65 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 36 57.43 +55 34 22.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,2461215.8312,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.64 00:12:16.02 +57:18:54.5
117.64050 -5.15362 galactic Cas Second-epoch detections are separated by 1.7" and 3.5 pix
The object was found in VSX 7" 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.02 +57:18:54.5: 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 00:12:16.02 +57:18:54.5: 15.48 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.48 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 12 16.02 +57 18 54.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
FL Cas,2461215.8312,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
FL Cas 20260624.3312 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 24.3312 2461215.8312 13.48 00:27:54.16 +52:58:19.3
119.34085 -9.73554 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 | 00:27:54.16 +52:58:19.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:27:54.16 +52:58:19.3: 15.47 +/- 0.29 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:27:54.16 +52:58:19.3: 15.21 +/- 0.24 detection
Forced photometry reference-image weighted average: 15.32 +/- 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 24.3312* 00 27 54.16 +52 58 19.3 13.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.81 23:35:04.15 +50:23:35.1
110.68166 -10.65334 galactic And Second-epoch detections are separated by 7.2" and 3.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:35:04.15 +50:23:35.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:04.15 +50:23:35.1: 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:35:04.15 +50:23:35.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 24.3312* 23 35 04.15 +50 23 35.1 13.8 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.81CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.76 23:43:27.65 +51:45:09.0
112.35413 -9.71768 galactic Cas Second-epoch detections are separated by 0.8" and 3.5 pix
The object was found in VSX13" Gaia DR3 1944888739280134016
Type:
# Max. Min./Amp. JD0 Period
15.710 G 15.760 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:43:27.65 +51:45:09.0: 15.89 +/- 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:27.65 +51:45:09.0: 15.57 +/- 0.26 detection
Forced photometry reference-image weighted average: 15.57 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 43 27.65 +51 45 09.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 1944888739280134016,2461215.8312,13.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1944888739280134016 20260624.3312 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 24.3312 2461215.8312 13.88 23:43:10.12 +52:00:37.3
112.37916 -9.45708 galactic Cas Second-epoch detections are separated by 4.9" 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:10.12 +52:00:37.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:43:10.12 +52:00:37.3: 15.89 +/- 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:10.12 +52:00:37.3: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 43 10.12 +52 00 37.3 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 14.02 23:42:02.11 +57:24:41.8
113.66380 -4.20594 galactic Cas Second-epoch detections are separated by 3.7" and 3.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 1998663001138723456 | 23:41:58.50 +57:25:07.2 (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:42:02.11 +57:24:41.8: 15.08 +/- 0.21 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:42:02.11 +57:24:41.8: 14.91 +/- 0.16 detection
Forced photometry reference-image weighted average: 14.97 +/- 0.13
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 42 02.11 +57 24 41.8 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998663001138723456,2461215.8312,14.02,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998663001138723456 20260624.3312 14.02CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.77 00:18:12.84 +54:09:31.4
118.02694 -8.39631 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:18:12.84 +54:09:31.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:18:12.84 +54:09:31.4: 15.68 +/- 0.31 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:12.84 +54:09:31.4: 15.87 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.68 +/- 0.31
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 18 12.84 +54 09 31.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,2461215.8312,13.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.97 23:30:29.03 +55:42:38.3
111.64348 -5.37673 galactic Cas Second-epoch detections are separated by 4.4" and 4.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:30:29.03 +55:42:38.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:30:29.03 +55:42:38.3: 15.18 +/- 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:29.03 +55:42:38.3: 15.18 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 29.03 +55 42 38.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,2461215.8312,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.84 23:57:06.91 +52:12:21.2
114.53547 -9.77803 galactic Cas Second-epoch detections are separated by 1.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 | target | 23:57:06.91 +52:12:21.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:57:06.91 +52:12:21.2: 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:57:06.91 +52:12:21.2: 15.96 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 57 06.91 +52 12 21.2 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.77 00:19:48.27 +51:04:46.8
117.87164 -11.48101 galactic Cas Second-epoch detections are separated by 0.9" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 00:19:48.27 +51:04:46.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:19:48.27 +51:04:46.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:19:48.27 +51:04:46.8: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 19 48.27 +51 04 46.8 13.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.94 23:51:59.45 +56:02:30.5
114.65100 -5.87119 galactic Cas Second-epoch detections are separated by 3.6" and 3.4 pix
The object was found in VSX 7" QS Cas
Type: EA/SD
# Max. Min./Amp. JD0 Period
13.600 pg 16.500 pg 2427962.38200 5.289979000000
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:51:59.45 +56:02:30.5: 15.46 +/- 0.26 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:59.45 +56:02:30.5: 15.81 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.46 +/- 0.26
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 51 59.45 +56 02 30.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
QS Cas,2461215.8312,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
QS Cas 20260624.3312 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.08 23:32:13.49 +55:32:49.6
111.82820 -5.60762 galactic Cas Second-epoch detections are separated by 5.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 | target | 23:32:13.49 +55:32:49.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:32:13.49 +55:32:49.6: 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:32:13.49 +55:32:49.6: 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 24.3312* 23 32 13.49 +55 32 49.6 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.91 23:44:10.52 +53:03:33.5
112.80752 -8.48513 galactic Cas Second-epoch detections are separated by 2.7" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:44:10.52 +53:03:33.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:44:10.52 +53:03:33.5: 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:44:10.52 +53:03:33.5: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 44 10.52 +53 03 33.5 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.95 23:51:33.93 +51:33:35.4
113.54156 -10.21698 galactic Cas Second-epoch detections are separated by 2.4" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J357.8836+51.5693 | 23:51:33.93 +51:33:35.4 (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:51:33.93 +51:33:35.4: 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 23:51:33.93 +51:33:35.4: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 51 33.93 +51 33 35.4 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.8836+51.5693,2461215.8312,13.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.8836+51.5693 20260624.3312 13.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.97 23:35:17.66 +55:37:21.9
112.26690 -5.66437 galactic Cas Second-epoch detections are separated by 1.4" and 3.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:35:17.66 +55:37:21.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:35:17.66 +55:37:21.9: 15.44 +/- 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:17.66 +55:37:21.9: 15.45 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 35 17.66 +55 37 21.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,2461215.8312,13.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.04 23:38:10.32 +52:43:48.9
111.83606 -8.55588 galactic Cas Second-epoch detections are separated by 4.8" and 3.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:38:10.32 +52:43:48.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:38:10.32 +52:43:48.9: 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:38:10.32 +52:43:48.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 24.3312* 23 38 10.32 +52 43 48.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,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 14.04 23:29:09.11 +56:37:33.8
111.75281 -4.44911 galactic Cas Second-epoch detections are separated by 2.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:29:09.11 +56:37:33.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:29:09.11 +56:37:33.8: 15.40 +/- 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:09.11 +56:37:33.8: 15.47 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 29 09.11 +56 37 33.8 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,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 20260624.3312 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 24.3312 2461215.8312 13.94 00:18:52.21 +57:49:38.8
118.59199 -4.76961 galactic Cas Second-epoch detections are separated by 2.3" and 3.3 pix
The object was found in VSX 8" ASASSN-V J001851.51+574945.0
Type: L
# Max. Min./Amp. JD0 Period
14.930 V 15.900 V
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:18:52.21 +57:49:38.8: 15.38 +/- 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:18:52.21 +57:49:38.8: 15.36 +/- 0.25 detection
Forced photometry reference-image weighted average: 15.37 +/- 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 24.3312* 00 18 52.21 +57 49 38.8 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J001851.51+574945.0,2461215.8312,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J001851.51+574945.0 20260624.3312 13.94CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.92 00:06:22.19 +52:40:37.3
116.03172 -9.58987 galactic Cas Second-epoch detections are separated by 4.0" 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:06:22.19 +52:40:37.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:06:22.19 +52:40:37.3: 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:06:22.19 +52:40:37.3: 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 24.3312* 00 06 22.19 +52 40 37.3 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.92 00:10:00.85 +50:50:02.0
116.27871 -11.50196 galactic Cas Second-epoch detections are separated by 5.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 | target | 00:10:00.85 +50:50:02.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:10:00.85 +50:50:02.0: 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 00:10:00.85 +50:50:02.0: 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 24.3312* 00 10 00.85 +50 50 02.0 13.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.92CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.15 23:43:06.18 +52:46:20.8
112.57363 -8.71951 galactic Cas Second-epoch detections are separated by 2.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 | ATO J355.7806+52.7790 | 23:43:06.18 +52:46:20.8 (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:43:06.18 +52:46:20.8: 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:43:06.18 +52:46:20.8: 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 24.3312* 23 43 06.18 +52 46 20.8 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.7806+52.7790,2461215.8312,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 J355.7806+52.7790 20260624.3312 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 24.3312 2461215.8312 14.06 23:41:29.16 +52:56:27.7
112.38136 -8.49179 galactic Cas Second-epoch detections are separated by 5.1" and 3.6 pix
The object was found in VSX25" Gaia DR3 1993070953717430016
Type: ROT
# Max. Min./Amp. JD0 Period
14.440 G 14.470 G 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 23:41:29.16 +52:56:27.7: 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 23:41:29.16 +52:56:27.7: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 41 29.16 +52 56 27.7 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1993070953717430016,2461215.8312,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1993070953717430016 20260624.3312 14.06CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 13.96 00:01:19.68 +51:15:18.6
114.98708 -10.84194 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 | target | 00:01:19.68 +51:15:18.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:01:19.68 +51:15:18.6: 15.98 +/- 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:19.68 +51:15:18.6: 15.99 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 01 19.68 +51 15 18.6 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.18 23:42:24.87 +53:39:49.0
112.71231 -7.83297 galactic Cas Second-epoch detections are separated by 3.8" 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:42:24.87 +53:39:49.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:42:24.87 +53:39:49.0: 15.72 +/- 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:42:24.87 +53:39:49.0: 15.75 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 42 24.87 +53 39 49.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.18CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.33 23:38:25.92 +55:22:20.3
112.62289 -6.03142 galactic Cas Second-epoch detections are separated by 4.9" and 3.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:38:25.92 +55:22:20.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:38:25.92 +55:22:20.3: 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:38:25.92 +55:22:20.3: 15.71 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 38 25.92 +55 22 20.3 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.25 23:40:11.86 +51:49:34.2
111.88150 -9.51053 galactic Cas Second-epoch detections are separated by 8.0" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:40:11.86 +51:49:34.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:40:11.86 +51:49:34.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:40:11.86 +51:49:34.2: 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 24.3312* 23 40 11.86 +51 49 34.2 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.16 23:34:16.39 +54:04:44.7
111.66889 -7.09661 galactic Cas Second-epoch detections are separated by 2.2" 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:34:16.39 +54:04:44.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:34:16.39 +54:04:44.7: 15.38 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:34:16.39 +54:04:44.7: 15.41 +/- 0.34 detection
Forced photometry reference-image weighted average: 15.40 +/- 0.23
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 34 16.39 +54 04 44.7 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.17 23:46:45.93 +52:24:14.0
113.02157 -9.21901 galactic Cas Second-epoch detections are separated by 4.4" 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:46:45.93 +52:24:14.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:46:45.93 +52:24:14.0: 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 23:46:45.93 +52:24:14.0: 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 24.3312* 23 46 45.93 +52 24 14.0 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.17CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.13 00:08:30.90 +51:27:29.8
116.14802 -10.84721 galactic Cas Second-epoch detections are separated by 4.6" and 3.6 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J002.1354+51.4626 | 00:08:30.90 +51:27:29.8 (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:08:30.90 +51:27:29.8: 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 00:08:30.90 +51:27:29.8: 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 24.3312* 00 08 30.90 +51 27 29.8 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J002.1354+51.4626,2461215.8312,14.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J002.1354+51.4626 20260624.3312 14.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.33 23:56:55.59 +56:39:55.6
115.45906 -5.41332 galactic Cas Second-epoch detections are separated by 7.8" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J359.2235+56.6749 | 23:56:55.59 +56:39:55.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:56:55.59 +56:39:55.6: 15.07 +/- 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:55.59 +56:39:55.6: 15.01 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 56 55.59 +56 39 55.6 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J359.2235+56.6749,2461215.8312,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J359.2235+56.6749 20260624.3312 14.33CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.32 23:32:28.28 +53:27:00.9
111.22268 -7.61669 galactic Cas Second-epoch detections are separated by 3.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:32:28.28 +53:27:00.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:32:28.28 +53:27:00.9: 15.72 +/- 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:32:28.28 +53:27:00.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 24.3312* 23 32 28.28 +53 27 00.9 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.15 23:41:22.00 +55:49:29.6
113.14855 -5.71016 galactic Cas Second-epoch detections are separated by 7.2" and 3.7 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | ATO J355.3506+55.8360 | 23:41:22.00 +55:49:29.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:41:22.00 +55:49:29.6: 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:22.00 +55:49:29.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 24.3312* 23 41 22.00 +55 49 29.6 14.2 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J355.3506+55.8360,2461215.8312,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 J355.3506+55.8360 20260624.3312 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 24.3312 2461215.8312 14.11 00:07:47.70 +50:06:41.9
115.79925 -12.15472 galactic Cas Second-epoch detections are separated by 4.0" 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:07:47.70 +50:06:41.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:07:47.70 +50:06:41.9: 15.78 +/- 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:47.70 +50:06:41.9: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 07 47.70 +50 06 41.9 14.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.31 23:40:54.60 +53:47:05.5
112.52896 -7.65628 galactic Cas Second-epoch detections are separated by 4.4" and 3.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:40:54.60 +53:47:05.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:40:54.60 +53:47:05.5: 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:40:54.60 +53:47:05.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 24.3312* 23 40 54.60 +53 47 05.5 14.3 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.31CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.50 23:33:36.56 +53:30:57.9
111.40555 -7.60491 galactic Cas Second-epoch detections are separated by 2.1" and 3.9 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:33:36.56 +53:30:57.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:33:36.56 +53:30:57.9: 15.72 +/- 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:36.56 +53:30:57.9: 15.73 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 33 36.56 +53 30 57.9 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.50,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.50CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.37 23:34:16.76 +54:25:03.6
111.77078 -6.77349 galactic Cas Second-epoch detections are separated by 4.1" 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:16.76 +54:25:03.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:34:16.76 +54:25:03.6: 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:34:16.76 +54:25:03.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 24.3312* 23 34 16.76 +54 25 03.6 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.37CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.48 23:32:09.20 +53:57:19.8
111.33219 -7.12102 galactic Cas Second-epoch detections are separated by 0.9" and 3.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:32:09.20 +53:57:19.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:32:09.20 +53:57:19.8: 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:32:09.20 +53:57:19.8: 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 24.3312* 23 32 09.20 +53 57 19.8 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.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 20260624.3312 14.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 24.3312 2461215.8312 14.68 23:28:36.21 +57:27:57.2
111.94663 -3.62844 galactic Cas Second-epoch detections are separated by 1.6" and 3.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 1998848883020633088 | 23:28:36.60 +57:28:40.2 (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:28:36.21 +57:27:57.2: 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:28:36.21 +57:27:57.2: 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 24.3312* 23 28 36.21 +57 27 57.2 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998848883020633088,2461215.8312,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998848883020633088 20260624.3312 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.40 23:29:51.09 +56:53:56.4
111.92964 -4.21976 galactic Cas Second-epoch detections are separated by 1.8" and 3.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:29:51.09 +56:53:56.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:29:51.09 +56:53:56.4: 15.65 +/- 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:51.09 +56:53:56.4: 15.61 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 29 51.09 +56 53 56.4 14.4 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.40CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.57 23:35:21.51 +56:13:47.8
112.45328 -5.08615 galactic Cas Second-epoch detections are separated by 3.0" and 3.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:21.51 +56:13:47.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:35:21.51 +56:13:47.8: 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 23:35:21.51 +56:13:47.8: 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 24.3312* 23 35 21.51 +56 13 47.8 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.57CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.54 23:31:44.84 +51:29:36.6
110.51233 -9.44633 galactic Cas Second-epoch detections are separated by 5.4" 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:31:44.84 +51:29:36.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:31:44.84 +51:29:36.6: 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:31:44.84 +51:29:36.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 24.3312* 23 31 44.84 +51 29 36.6 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.48 23:47:57.58 +54:15:32.2
113.66156 -7.46628 galactic Cas Second-epoch detections are separated by 7.2" and 3.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 J356.9999+54.2539 | 23:47:57.58 +54:15:32.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 23:47:57.58 +54:15:32.2: 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 23:47:57.58 +54:15:32.2: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 47 57.58 +54 15 32.2 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J356.9999+54.2539,2461215.8312,14.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
ATO J356.9999+54.2539 20260624.3312 14.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 24.3312 2461215.8312 14.64 23:36:56.22 +52:44:46.2
111.65947 -8.48733 galactic Cas Second-epoch detections are separated by 3.1" 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:36:56.22 +52:44:46.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:36:56.22 +52:44:46.2: 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 23:36:56.22 +52:44:46.2: 15.85 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 36 56.22 +52 44 46.2 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.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 24.3312 2461215.8312 14.54 23:52:16.62 +51:29:29.7
113.63484 -10.30906 galactic Cas Second-epoch detections are separated by 2.2" and 3.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:52:16.62 +51:29:29.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:16.62 +51:29:29.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:16.62 +51:29:29.7: 15.98 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 52 16.62 +51 29 29.7 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.54CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.72 23:29:19.98 +54:59:47.1
111.26370 -6.00446 galactic Cas Second-epoch detections are separated by 3.8" and 4.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:19.98 +54:59:47.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:29:19.98 +54:59:47.1: 15.68 +/- 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:19.98 +54:59:47.1: 15.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 29 19.98 +54 59 47.1 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.69 23:31:23.21 +54:32:01.3
111.40262 -6.53625 galactic Cas Second-epoch detections are separated by 2.7" and 3.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:31:23.21 +54:32:01.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:31:23.21 +54:32:01.3: 15.72 +/- 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:23.21 +54:32:01.3: 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 24.3312* 23 31 23.21 +54 32 01.3 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.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 20260624.3312 14.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 24.3312 2461215.8312 14.81 23:29:30.64 +56:07:01.5
111.64024 -4.94804 galactic Cas Second-epoch detections are separated by 3.1" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:29:30.64 +56:07:01.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:30.64 +56:07:01.5: 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 23:29:30.64 +56:07:01.5: 15.60 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 29 30.64 +56 07 01.5 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.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 20260624.3312 14.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 24.3312 2461215.8312 14.62 23:37:58.17 +52:39:44.2
111.78683 -8.61238 galactic Cas Second-epoch detections are separated by 4.2" and 3.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 1992981549678260736 | 23:37:57.42 +52:39:01.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:37:58.17 +52:39:44.2: 15.72 +/- 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:37:58.17 +52:39:44.2: 15.61 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 37 58.17 +52 39 44.2 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1992981549678260736,2461215.8312,14.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1992981549678260736 20260624.3312 14.62CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.52 23:36:32.87 +53:13:26.0
111.74179 -8.01297 galactic Cas Second-epoch detections are separated by 1.6" 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:32.87 +53:13:26.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:36:32.87 +53:13:26.0: 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 23:36:32.87 +53:13:26.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 24.3312* 23 36 32.87 +53 13 26.0 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.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 20260624.3312 14.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 24.3312 2461215.8312 14.66 23:33:53.40 +54:37:16.9
111.77731 -6.56220 galactic Cas Second-epoch detections are separated by 1.9" and 3.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:33:53.40 +54:37:16.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:33:53.40 +54:37:16.9: 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 23:33:53.40 +54:37:16.9: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 33 53.40 +54 37 16.9 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.77 23:30:47.25 +56:59:47.3
112.08156 -4.16654 galactic Cas Second-epoch detections are separated by 2.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 | ATO J352.6926+56.9877 | 23:30:47.25 +56:59:47.3 (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:47.25 +56:59:47.3: 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:30:47.25 +56:59:47.3: 15.72 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 30 47.25 +56 59 47.3 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.6926+56.9877,2461215.8312,14.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.6926+56.9877 20260624.3312 14.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.63 23:31:09.91 +50:06:30.9
109.98864 -10.73499 galactic And Second-epoch detections are separated by 4.0" 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:31:09.91 +50:06:30.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:31:09.91 +50:06:30.9: 15.59 +/- 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:09.91 +50:06:30.9: 15.51 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 31 09.91 +50 06 30.9 14.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.69 23:31:39.19 +51:36:24.3
110.53351 -9.33407 galactic Cas Second-epoch detections are separated by 7.7" 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 | ATO J352.9045+51.6174 | 23:31:39.19 +51:36:24.3 (user input) | NSINE (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:31:39.19 +51:36:24.3: 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:39.19 +51:36:24.3: 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 24.3312* 23 31 39.19 +51 36 24.3 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.9045+51.6174,2461215.8312,14.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
ATO J352.9045+51.6174 20260624.3312 14.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 24.3312 2461215.8312 14.68 23:36:30.85 +57:01:15.2
112.83525 -4.37486 galactic Cas Second-epoch detections are separated by 4.5" and 3.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:36:30.85 +57:01:15.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:36:30.85 +57:01:15.2: 15.69 +/- 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:30.85 +57:01:15.2: 15.68 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 36 30.85 +57 01 15.2 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.71 23:32:59.53 +56:40:19.7
112.27092 -4.56711 galactic Cas Second-epoch detections are separated by 0.5" and 3.5 pix
The object was found in VSX21" Gaia DR3 1998531987455639040
Type: VAR
# Max. Min./Amp. JD0 Period
17.570 G 17.610 G 0.018148800000 M
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:32:59.53 +56:40:19.7: 15.78 +/- 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:32:59.53 +56:40:19.7: 15.77 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 32 59.53 +56 40 19.7 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1998531987455639040,2461215.8312,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1998531987455639040 20260624.3312 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.71 23:30:06.40 +53:32:17.7
110.91244 -7.42479 galactic Cas Second-epoch detections are separated by 3.4" and 3.9 pix
The object was found in VSX19" Gaia DR3 1992748728090161664
Type: ROT
# Max. Min./Amp. JD0 Period
16.380 G 16.470 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:30:06.40 +53:32:17.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:30:06.40 +53:32:17.7: 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 24.3312* 23 30 06.40 +53 32 17.7 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1992748728090161664,2461215.8312,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1992748728090161664 20260624.3312 14.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.65 23:31:51.43 +51:36:18.3
110.56354 -9.34539 galactic Cas Second-epoch detections are separated by 5.1" and 3.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 J352.9701+51.6121 | 23:31:51.43 +51:36:18.3 (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:31:51.43 +51:36:18.3: 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 23:31:51.43 +51:36:18.3: 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 24.3312* 23 31 51.43 +51 36 18.3 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.9701+51.6121,2461215.8312,14.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
ATO J352.9701+51.6121 20260624.3312 14.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 24.3312 2461215.8312 14.81 23:29:41.77 +57:15:16.9
112.02051 -3.87516 galactic Cas Second-epoch detections are separated by 3.4" and 4.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 J352.4146+57.2652 | 23:29:41.77 +57:15:16.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:29:41.77 +57:15:16.9: 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:29:41.77 +57:15:16.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 24.3312* 23 29 41.77 +57 15 16.9 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.4146+57.2652,2461215.8312,14.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
ATO J352.4146+57.2652 20260624.3312 14.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 24.3312 2461215.8312 14.77 23:31:53.48 +56:22:32.9
112.03600 -4.80383 galactic Cas Second-epoch detections are separated by 4.4" and 4.2 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:53.48 +56:22:32.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:31:53.48 +56:22:32.9: 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:31:53.48 +56:22:32.9: 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 24.3312* 23 31 53.48 +56 22 32.9 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.77CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.66 23:40:41.80 +51:33:51.3
111.88380 -9.78361 galactic Cas Second-epoch detections are separated by 1.7" and 3.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:40:41.80 +51:33:51.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:40:41.80 +51:33:51.3: 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:40:41.80 +51:33:51.3: 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 24.3312* 23 40 41.80 +51 33 51.3 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.87 23:30:23.05 +54:28:32.9
111.24529 -6.54642 galactic Cas Second-epoch detections are separated by 2.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:30:23.05 +54:28:32.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:30:23.05 +54:28:32.9: 15.54 +/- 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:23.05 +54:28:32.9: 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 24.3312* 23 30 23.05 +54 28 32.9 14.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.79 23:32:01.34 +57:16:57.3
112.32903 -3.94523 galactic Cas Second-epoch detections are separated by 6.6" and 3.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:32:01.34 +57:16:57.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:32:01.34 +57:16:57.3: 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 23:32:01.34 +57:16:57.3: 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 24.3312* 23 32 01.34 +57 16 57.3 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.60 23:32:04.03 +55:15:39.7
111.71955 -5.87344 galactic Cas Second-epoch detections are separated by 1.1" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:32:04.03 +55:15:39.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:32:04.03 +55:15:39.7: 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:32:04.03 +55:15:39.7: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 32 04.03 +55 15 39.7 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.60CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.85 23:40:24.51 +54:53:56.5
112.76419 -6.56438 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:40:24.51 +54:53:56.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:40:24.51 +54:53:56.5: 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:40:24.51 +54:53:56.5: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 40 24.51 +54 53 56.5 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.76 23:42:10.97 +56:45:18.7
113.50806 -4.84405 galactic Cas Second-epoch detections are separated by 1.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 | 23:42:10.97 +56:45:18.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:42:10.97 +56:45:18.7: 15.70 +/- 0.32 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:42:10.97 +56:45:18.7: 15.79 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 15.70 +/- 0.32
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 42 10.97 +56 45 18.7 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.72 23:31:21.75 +54:44:10.3
111.46172 -6.34242 galactic Cas Second-epoch detections are separated by 2.1" and 3.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:31:21.75 +54:44:10.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:31:21.75 +54:44:10.3: 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 23:31:21.75 +54:44:10.3: 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 24.3312* 23 31 21.75 +54 44 10.3 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.88 23:41:49.94 +53:59:51.3
112.71893 -7.48819 galactic Cas Second-epoch detections are separated by 5.1" and 3.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:49.94 +53:59:51.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:41:49.94 +53:59:51.3: 15.78 +/- 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:49.94 +53:59:51.3: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 41 49.94 +53 59 51.3 14.9 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.72 23:42:24.06 +55:49:09.1
113.28770 -5.75447 galactic Cas Second-epoch detections are separated by 5.5" 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:42:24.06 +55:49:09.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:42:24.06 +55:49:09.1: 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 23:42:24.06 +55:49:09.1: 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 24.3312* 23 42 24.06 +55 49 09.1 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.66 23:31:20.85 +50:23:20.5
110.10538 -10.47744 galactic And Second-epoch detections are separated by 5.3" and 3.8 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:31:20.85 +50:23:20.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:31:20.85 +50:23:20.5: 15.69 +/- 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:20.85 +50:23:20.5: 15.74 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 31 20.85 +50 23 20.5 14.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,2461215.8312,14.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.68 23:39:52.36 +52:19:51.6
111.97427 -9.01156 galactic Cas Second-epoch detections are separated by 6.0" and 3.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:52.36 +52:19:51.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:39:52.36 +52:19:51.6: 15.72 +/- 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:52.36 +52:19:51.6: 15.70 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 39 52.36 +52 19 51.6 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.72 23:31:13.06 +51:41:37.4
110.49558 -9.23050 galactic Cas Second-epoch detections are separated by 8.0" 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 | ATO J352.7852+51.6925 | 23:31:13.06 +51:41:37.4 (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:31:13.06 +51:41:37.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:31:13.06 +51:41:37.4: 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 24.3312* 23 31 13.06 +51 41 37.4 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J352.7852+51.6925,2461215.8312,14.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J352.7852+51.6925 20260624.3312 14.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.68 23:50:58.60 +50:27:24.9
113.18600 -11.26721 galactic Cas Second-epoch detections are separated by 0.7" and 3.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 J357.7449+50.4497 | 23:50:58.60 +50:27:24.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:50:58.60 +50:27:24.9: 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:50:58.60 +50:27:24.9: 15.95 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 50 58.60 +50 27 24.9 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J357.7449+50.4497,2461215.8312,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J357.7449+50.4497 20260624.3312 14.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.78 23:41:49.20 +52:55:47.4
112.42730 -8.51615 galactic Cas Second-epoch detections are separated by 2.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:41:49.20 +52:55:47.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:41:49.20 +52:55:47.4: 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:41:49.20 +52:55:47.4: 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 24.3312* 23 41 49.20 +52 55 47.4 14.8 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.47 00:13:10.02 +50:37:08.4
116.74733 -11.79261 galactic Cas Second-epoch detections are separated by 2.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 | target | 00:13:10.02 +50:37: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 00:13:10.02 +50:37:08.4: 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:13:10.02 +50:37:08.4: 15.89 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 13 10.02 +50 37 08.4 14.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.47CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.70 00:06:32.77 +52:20:36.8
115.99893 -9.92285 galactic Cas Second-epoch detections are separated by 6.6" 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 | 00:06:32.77 +52:20:36.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:06:32.77 +52:20:36.8: 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:06:32.77 +52:20:36.8: 15.88 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 06 32.77 +52 20 36.8 14.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.70,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.70CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 14.64 00:06:57.77 +51:44:16.0
115.95518 -10.53049 galactic Cas Second-epoch detections are separated by 2.7" 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:06:57.77 +51:44:16.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:06:57.77 +51:44:16.0: 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:06:57.77 +51:44:16.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 24.3312* 00 06 57.77 +51 44 16.0 14.6 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,14.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 14.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 24.3312 2461215.8312 7.72 00:23:10.55 +55:47:26.4
118.93779 -6.86175 galactic Cas Second-epoch detections are separated by 8.7" 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 | T Cas | 00:23:14.31 +55:47:33.1 (Gaia DR3) | M (local) | 443.500000000000 (local) | Gaia3var=VARIABLE SpType: M8e 1923ApJ....58..215M T Cas
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:23:10.55 +55:47:26.4: 10.12 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:10.55 +55:47:26.4: 10.15 +/- 0.01 detection
Forced photometry reference-image weighted average: 10.13 +/- 0.01
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 23 10.55 +55 47 26.4 7.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
T Cas,2461215.8312,7.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
T Cas 20260624.3312 7.72CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 7.83 23:58:25.86 +51:26:15.9
114.57373 -10.57173 galactic Cas Second-epoch detections are separated by 4.0" 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:25.86 +51:26:15.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:58:25.86 +51:26:15.9: 15.72 +/- 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:25.86 +51:26:15.9: 15.65 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 58 25.86 +51 26 15.9 7.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,2461215.8312,7.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 20260624.3312 7.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 24.3312 2461215.8312 11.63 23:34:59.80 +50:35:49.8
110.73196 -10.45500 galactic And Second-epoch detections are separated by 8.5" and 3.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:34:59.80 +50:35:49.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:34:59.80 +50:35:49.8: 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:34:59.80 +50:35:49.8: 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 24.3312* 23 34 59.80 +50 35 49.8 11.6 U And 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 11.63CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 10.39 00:04:41.20 +55:32:15.1
116.30359 -6.73140 galactic Cas Second-epoch detections are separated by 0.8" and 3.4 pix
The object was found in VSX 4" 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.20 +55:32:15.1: 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.20 +55:32:15.1: 14.58 +/- 0.10 detection
Forced photometry reference-image weighted average: 14.59 +/- 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 24.3312* 00 04 41.20 +55 32 15.1 10.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
DI Cas,2461215.8312,10.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
DI Cas 20260624.3312 10.39CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.71 23:57:27.85 +52:04:36.7
114.56090 -9.91546 galactic Cas Second-epoch detections are separated by 6.5" and 3.4 pix
The object was not found in VSX
The object was not found in ASASSN-V
The object was not found in astcheck.
online_id | target | 23:57:27.85 +52:04:36.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:57:27.85 +52:04:36.7: 15.78 +/- 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:27.85 +52:04:36.7: 15.80 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 57 27.85 +52 04 36.7 12.7 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 12.71CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 12.03 23:58:59.85 +54:51:05.1
115.36791 -7.24834 galactic Cas Second-epoch detections are separated by 6.8" and 3.3 pix
The object was found in VSX 7" EV Cas
Type: LB
# Max. Min./Amp. JD0 Period
14.700 pg 15.500 pg 134.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 23:58:59.85 +54:51:05.1: 13.10 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:59.85 +54:51:05.1: 13.14 +/- 0.03 detection
Forced photometry reference-image weighted average: 13.12 +/- 0.02
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 23 58 59.85 +54 51 05.1 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
EV Cas,2461215.8312,12.03,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
EV Cas 20260624.3312 12.03CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Mean magnitude and position on the discovery images:
2026 06 24.3312 2461215.8312 11.95 00:18:30.00 +53:39:27.2
118.00354 -8.89871 galactic Cas Second-epoch detections are separated by 2.4" 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 | ASASSN-V J001833.41+533914.7 | 00:18:33.43 +53:39:14.7 (Gaia DR3) | L (local) | (local) | Gaia3var=VARIABLE
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:18:30.00 +53:39:27.2: 15.11 +/- 0.19 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:18:30.00 +53:39:27.2: 15.27 +/- 0.23 detection
Forced photometry reference-image weighted average: 15.18 +/- 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 24.3312* 00 18 30.00 +53 39 27.2 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
ASASSN-V J001833.41+533914.7,2461215.8312,11.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
ASASSN-V J001833.41+533914.7 20260624.3312 11.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 24.3312 2461215.8312 13.10 00:13:25.75 +52:37:42.8
117.09537 -9.81193 galactic Cas Second-epoch detections are separated by 0.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:13:25.75 +52:37:42.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:13:25.75 +52:37:42.8: 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:13:25.75 +52:37:42.8: 15.86 +/- 99.00 upperlimit
Check this position in TNS.Manually check the ASAS-SN list of transients!Search this object in SIMBAD.Search this object in VizieR catalogs.WISE atlasAladin LiteSNAD ZTF viewer
Online MPChecker may fail to identify bright comets! Please manually check the Seiichi Yoshida's and Gideon van Buitenen's pages.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 06 24.3312* 00 13 25.75 +52 37 42.8 13.1 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461215.8312,13.10,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260624.3312 13.10CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## 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: 2461215.83145263 24.06.2026 07:57:07.507 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 67
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: 17 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): 27009
Objects passed selection criteria: 26925
Measurements per detected object (mean, median, min, max): 3.0 3.0 2 4
Measurements per selected object (mean, median, min, max): 3.0 3.0 2 4
Average stars detected per image: 21232.5
Average stars matched: 19076 (89.8434 %)
Memory usage VmPeak: 127984 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 23 15:09:51 CDT 2026
VaST build number 1.0rc89-109-g76dded0d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-23)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Jun 24 03:57:48 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: 2461215.83145263 24.06.2026 07:57:07.507 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 370
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: 294 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): 203424
Objects passed selection criteria: 202834
Measurements per detected object (mean, median, min, max): 2.9 2.0 2 4
Measurements per selected object (mean, median, min, max): 2.9 2.0 2 4
Average stars detected per image: 156979
Average stars matched: 140548 (89.5325 %)
Memory usage VmPeak: 1955440 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Tue Jun 23 15:09:51 CDT 2026
VaST build number 1.0rc89-109-g76dded0d
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-06-23)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Wed Jun 24 04:41:43 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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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: 2461215.83097344
Re-using ../asassn_transients_list.txt
'../asassn_transients_list.txt' -> 'asassn_transients_list.txt'
Re-using ../tocp_transients_list.txt
'../tocp_transients_list.txt' -> 'tocp_transients_list.txt'
Re-using ../tns_transients_list.txt
'../tns_transients_list.txt' -> 'tns_transients_list.txt'
Plate-solving the images
wcs_Cas-04-Q2b1x1_2026-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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits'
wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits exists and is non-empty
Saving wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits to local_wcs_cache/
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits' -> 'local_wcs_cache/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits (1st new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Image size: 926.8'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.044 +54:01:16.24 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:57.044 +54:01:16.24
Angular distance between the image centers 0.0315 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-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits (2nd new image)
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
Image size: 926.8'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:56.842 +54:01:36.38 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:56.842 +54:01:36.38
Angular distance between the image centers 0.0367 deg.
###################################
###################################
# Check the image center offset between the first and the second second-epoch image (shift should be applied between the second-epoch images)
Second-epoch first image center 23:59:57.044 +54:01:16.24
Second-epoch second image center 23:59:56.842 +54:01:36.38
Angular distance between the image centers 0.00562 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.tT7Q80s26y
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.k2XovbMTxo
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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits &> /tmp/tmp.8YWeFBilKE
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits &> /tmp/tmp.qtQPWyliha
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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 65 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.6 pix fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
2.6 pix fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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.8 mag. fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
14.8 mag. fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 12.0 (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.tT7Q80s26y (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/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
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.k2XovbMTxo (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/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.8YWeFBilKE (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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=2131, bad_region=4775, passed=25780
Got 25780 stars (including 19263 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat
util/solve_plate_with_UCAC5 got 25780 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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.0030 through 0 to 14.8805, gap 14.8805 to 345.0030
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 319 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 165 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.53"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 222 matched stars entering correct_measured_positions(), 5328 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.55"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 344.9859 through 0 to 14.9041, gap 14.9041 to 344.9859
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 409 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 342 matched stars entering correct_measured_positions(), 5398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.52"
Accuracy estimation diagnostic: 334 matched stars entering correct_measured_positions(), 7782 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.20"
Excluding outliers - 334 stars left (next iteration limit 244)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits N_match=334 sigma_overall_arcsec=10.982 sigma_q1_arcsec=25.161 sigma_q2_arcsec=32.035 sigma_q3_arcsec=7.680 sigma_q4_arcsec=10.198 n_q1=35 n_q2=19 n_q3=121 n_q4=159 worst_quadrant_to_overall_ratio=2.917
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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.qtQPWyliha (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
WCS-calibrated image found: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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=2095, bad_region=4810, passed=25903
Got 25903 stars (including 19387 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat
util/solve_plate_with_UCAC5 got 25903 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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 344.9607 through 0 to 14.8806, gap 14.8806 to 344.9607
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 322 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 232 matched stars entering correct_measured_positions(), 165 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.57"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 223 matched stars entering correct_measured_positions(), 5460 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.78"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 344.9497 through 0 to 14.9062, gap 14.9062 to 344.9497
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 408 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 338 matched stars entering correct_measured_positions(), 5522 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.58"
Accuracy estimation diagnostic: 331 matched stars entering correct_measured_positions(), 7532 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.85"
Excluding outliers - 331 stars left (next iteration limit 245)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits N_match=331 sigma_overall_arcsec=11.179 sigma_q1_arcsec=27.334 sigma_q2_arcsec=30.999 sigma_q3_arcsec=7.898 sigma_q4_arcsec=11.009 n_q1=35 n_q2=15 n_q3=123 n_q4=158 worst_quadrant_to_overall_ratio=2.773
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits sigma_overall=10.982 worst_q_ratio=2.917
new2=fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits sigma_overall=11.179 worst_q_ratio=2.773
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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits) flagged: sigma=10.982 (ref avg 0.495), ratio=2.917 (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/lib/make_outxyls_for_astrometric_calibration found 24394 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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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: "out671718.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out671718.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
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).
log-odds ratio 28.3064 (1.96476e+12), 8 match, 0 conflict, 7 distractors, 366 index.
RA,Dec = (0.107619,53.9575), pixel scale 5.88089 arcsec/pix.
Hit/miss: Hit/miss: ----++++---++++(best)------------------------++-----++--------------------------++--+--+++----------------
Field 1: solved with index index-4112.fits.
Field 1 solved: writing to file ./out671718.solved to indicate this.
Field: out671718.xyls
Field center: (RA,Dec) = (359.994215, 54.006232) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.612, +54:00:22.435).
Field size: 15.7344 x 10.5296 degrees
Field rotation angle: up is -0.949925 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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 24 04:11 fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
-rw-r--r-- 1 apache apache 12K Jun 24 04:11 out671718.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits (fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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: "out671718.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out671718.axy"...
Only searching for solutions within 15.665 degrees of RA,Dec (359.996,54.0071)
log-odds ratio 24.4032 (3.96424e+10), 8 match, 0 conflict, 21 distractors, 24 index.
RA,Dec = (359.985,54.0195), pixel scale 5.93184 arcsec/pix.
Hit/miss: Hit/miss: ----+-++-----++---+-----+---+(best)-----------------------------------------------------------------------
fit-wcs.c:118:fit_sip_wcs: Too few correspondences for the SIP order specified (5 < 6)
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out671718.solved to indicate this.
Field: out671718.xyls
Field center: (RA,Dec) = (359.986313, 54.020347) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.715, +54:01:13.251).
Field size: 15.6067 x 10.4341 degrees
Field rotation angle: up is 3.38397 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 24 04:11 fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:12 out671718.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.axy"...
Verifying WCS using indices with quads of size [63.1543, 946.721] 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.1543, 946.721] arcmin
Verifying WCS with index 87 of 109 (/usr/local/astrometry/data/index-4117.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 88 of 109 (/usr/local/astrometry/data/index-4116.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 89 of 109 (/usr/local/astrometry/data/index-4115.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 90 of 109 (/usr/local/astrometry/data/index-4114.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 91 of 109 (/usr/local/astrometry/data/index-4113.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 93 of 109 (/usr/local/astrometry/data/index-4111.fits)
Verifying WCS of field 1.
--> log-odds 0
Verifying WCS with index 94 of 109 (/usr/local/astrometry/data/index-4110.fits)
Verifying WCS of field 1.
--> log-odds 0
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat from image00003.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
Image size: 926.8'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.044 +54:01:16.24 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 25780 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/correct_sextractor_wcs_catalog_usingxy2sky1440631.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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=2131, bad_region=4775, passed=25780
Got 25780 stars (including 19263 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat
util/solve_plate_with_UCAC5 got 25780 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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.0030 through 0 to 14.8805, gap 14.8805 to 345.0030
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 319 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 165 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.53"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 222 matched stars entering correct_measured_positions(), 5328 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.55"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 344.9859 through 0 to 14.9041, gap 14.9041 to 344.9859
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 409 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 342 matched stars entering correct_measured_positions(), 5398 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.52"
Accuracy estimation diagnostic: 334 matched stars entering correct_measured_positions(), 7782 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.20"
Excluding outliers - 334 stars left (next iteration limit 244)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits N_match=334 sigma_overall_arcsec=10.982 sigma_q1_arcsec=25.161 sigma_q2_arcsec=32.035 sigma_q3_arcsec=7.680 sigma_q4_arcsec=10.198 n_q1=35 n_q2=19 n_q3=121 n_q4=159 worst_quadrant_to_overall_ratio=2.917
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.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-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits): sigma 10.982->10.982, ratio 2.917->2.917; reverting to order 3
WCS_QUALITY_RETRY: 2nd new image (fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits) flagged: sigma=11.179 (ref avg 0.495), ratio=2.773 (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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
WCS_IMAGE_NAME=wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
No image with WCS calibration found for /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/lib/make_outxyls_for_astrometric_calibration found 24438 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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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: "out1480699.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1480699.axy"...
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
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).
log-odds ratio 28.2118 (1.78737e+12), 8 match, 0 conflict, 7 distractors, 366 index.
RA,Dec = (0.107418,53.9632), pixel scale 5.88072 arcsec/pix.
Hit/miss: Hit/miss: ----++++---++++(best)------------------------++--+--++--------------------------++-----+++----------------
Field 1: solved with index index-4112.fits.
Field 1 solved: writing to file ./out1480699.solved to indicate this.
Field: out1480699.xyls
Field center: (RA,Dec) = (359.993426, 54.011762) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:58.422, +54:00:42.343).
Field size: 15.7343 x 10.5296 degrees
Field rotation angle: up is -0.944281 degrees E of N
Field parity: neg
Inserting WCS header... '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits' -> 'fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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 24 04:22 fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
-rw-r--r-- 1 apache apache 12K Jun 24 04:22 out1480699.wcs
Inserting WCS header (1st iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits (fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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: "out1480699.xyls"...
Reading sort column "FLUX_APER"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
Solving...
Reading file "./out1480699.axy"...
Only searching for solutions within 15.665 degrees of RA,Dec (359.995,54.0126)
log-odds ratio 25.7453 (1.51724e+11), 7 match, 0 conflict, 16 distractors, 24 index.
RA,Dec = (359.984,54.0251), pixel scale 5.93183 arcsec/pix.
Hit/miss: Hit/miss: ----+++------++---+---+(best)-----+-----------------------------------------------------------------------
fit-wcs.c:118:fit_sip_wcs: Too few correspondences for the SIP order specified (5 < 6)
Field 1: solved with index index-4116.fits.
Field 1 solved: writing to file ./out1480699.solved to indicate this.
Field: out1480699.xyls
Field center: (RA,Dec) = (359.985471, 54.025942) deg.
Field center: (RA H:M:S, Dec D:M:S) = (23:59:56.513, +54:01:33.391).
Field size: 15.6068 x 10.4342 degrees
Field rotation angle: up is 3.39053 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 24 04:22 fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
-rw-r--r-- 1 apache apache 8.5K Jun 24 04:22 out1480699.wcs
Inserting WCS header (2nd iteration local)... Opening FITS image file fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits for reading... done!
Creating new image file (wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits"...
Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 100000 sources.
Solving...
Reading file "./wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.axy"...
Verifying WCS using indices with quads of size [63.1542, 946.72] 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 1.83114
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0.337514
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 2.73671
Verifying WCS using indices with quads of size [63.1542, 946.72] 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 1.83114
Verifying WCS with index 92 of 109 (/usr/local/astrometry/data/index-4112.fits)
Verifying WCS of field 1.
--> log-odds 0.337514
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 2.73671
Got 0 solutions.
Field 1 did not solve (index index-5203-47.fits, field objects 1-10).
Field 1 did not solve (index index-5203-46.fits, field objects 1-10).
Field 1 did not solve (index index-5203-45.fits, field objects 1-10).
Field 1 did not solve (index index-5203-44.fits, field objects 1-10).
Field 1 did not solve (index index-5203-43.fits, field objects 1-10).
Field 1 did not solve (index index-5203-42.fits, field objects 1-10).
Field 1 did not solve (index index-5203-41.fits, field objects 1-10).
Field 1 did not solve (index index-5203-40.fits, field objects 1-10).
Field 1 did not solve (index index-5203-39.fits, field objects 1-10).
Field 1 did not solve (index index-5203-38.fits, field objects 1-10).
Field 1 did not solve (index index-5203-37.fits, field objects 1-10).
Field 1 did not solve (index index-5203-36.fits, field objects 1-10).
Field 1 did not solve (index index-5203-35.fits, field objects 1-10).
Field 1 did not solve (index index-5203-34.fits, field objects 1-10).
Field 1 did not solve (index index-5203-33.fits, field objects 1-10).
Field 1 did not solve (index index-5203-32.fits, field objects 1-10).
Field 1 did not solve (index index-5203-31.fits, field objects 1-10).
Field 1 did not solve (index index-5203-30.fits, field objects 1-10).
Field 1 did not solve (index index-5203-29.fits, field objects 1-10).
Field 1 did not solve (index index-5203-28.fits, field objects 1-10).
Field 1 did not solve (index index-5203-27.fits, field objects 1-10).
Field 1 did not solve (index index-5203-26.fits, field objects 1-10).
Field 1 did not solve (index index-5203-25.fits, field objects 1-10).
Field 1 did not solve (index index-5203-24.fits, field objects 1-10).
Field 1 did not solve (index index-5203-23.fits, field objects 1-10).
Field 1 did not solve (index index-5203-22.fits, field objects 1-10).
Field 1 did not solve (index index-5203-21.fits, field objects 1-10).
Field 1 did not solve (index index-5203-20.fits, field objects 1-10).
Field 1 did not solve (index index-5203-19.fits, field objects 1-10).
Field 1 did not solve (index index-5203-18.fits, field objects 1-10).
Field 1 did not solve (index index-5203-17.fits, field objects 1-10).
Field 1 did not solve (index index-5203-16.fits, field objects 1-10).
Field 1 did not solve (index index-5203-15.fits, field objects 1-10).
Field 1 did not solve (index index-5203-14.fits, field objects 1-10).
Field 1 did not solve (index index-5203-13.fits, field objects 1-10).
Field 1 did not solve (index index-5203-12.fits, field objects 1-10).
Field 1 did not solve (index index-5203-11.fits, field objects 1-10).
Field 1 did not solve (index index-5203-10.fits, field objects 1-10).
Field 1 did not solve (index index-5203-09.fits, field objects 1-10).
Field 1 did not solve (index index-5203-08.fits, field objects 1-10).
Field 1 did not solve (index index-5203-07.fits, field objects 1-10).
Field 1 did not solve (index index-5203-06.fits, field objects 1-10).
Field 1 did not solve (index index-5203-05.fits, field objects 1-10).
Field 1 did not solve (index index-5203-04.fits, field objects 1-10).
Field 1 did not solve (index index-5203-03.fits, field objects 1-10).
Field 1 did not solve (index index-5203-02.fits, field objects 1-10).
Field 1 did not solve (index index-5203-01.fits, field objects 1-10).
Field 1 did not solve (index index-5203-00.fits, field objects 1-10).
Field 1 did not solve (index index-5005-11.fits, field objects 1-10).
Field 1 did not solve (index index-5005-10.fits, field objects 1-10).
Field 1 did not solve (index index-5005-09.fits, field objects 1-10).
Field 1 did not solve (index index-5005-08.fits, field objects 1-10).
Field 1 did not solve (index index-5005-07.fits, field objects 1-10).
Field 1 did not solve (index index-5005-06.fits, field objects 1-10).
Field 1 did not solve (index index-5005-05.fits, field objects 1-10).
Field 1 did not solve (index index-5005-04.fits, field objects 1-10).
Field 1 did not solve (index index-5005-03.fits, field objects 1-10).
Field 1 did not solve (index index-5005-02.fits, field objects 1-10).
Field 1 did not solve (index index-5005-01.fits, field objects 1-10).
Field 1 did not solve (index index-5005-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-11.fits, field objects 1-10).
Field 1 did not solve (index index-4206-10.fits, field objects 1-10).
Field 1 did not solve (index index-4206-09.fits, field objects 1-10).
Field 1 did not solve (index index-4206-08.fits, field objects 1-10).
Field 1 did not solve (index index-4206-07.fits, field objects 1-10).
Field 1 did not solve (index index-4206-06.fits, field objects 1-10).
Field 1 did not solve (index index-4206-05.fits, field objects 1-10).
Field 1 did not solve (index index-4206-04.fits, field objects 1-10).
Field 1 did not solve (index index-4206-03.fits, field objects 1-10).
Field 1 did not solve (index index-4206-02.fits, field objects 1-10).
Field 1 did not solve (index index-4206-01.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-11.fits, field objects 1-10).
Field 1 did not solve (index index-4205-10.fits, field objects 1-10).
Field 1 did not solve (index index-4205-09.fits, field objects 1-10).
Field 1 did not solve (index index-4205-08.fits, field objects 1-10).
Field 1 did not solve (index index-4205-07.fits, field objects 1-10).
Field 1 did not solve (index index-4205-06.fits, field objects 1-10).
Field 1 did not solve (index index-4205-05.fits, field objects 1-10).
Field 1 did not solve (index index-4205-04.fits, field objects 1-10).
Field 1 did not solve (index index-4205-03.fits, field objects 1-10).
Field 1 did not solve (index index-4205-02.fits, field objects 1-10).
Field 1 did not solve (index index-4205-01.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
Field 1 did not solve (index index-4119.fits, field objects 1-10).
Field 1 did not solve (index index-4118.fits, field objects 1-10).
Field 1 did not solve (index index-4117.fits, field objects 1-10).
Field 1 did not solve (index index-4116.fits, field objects 1-10).
Field 1 did not solve (index index-4115.fits, field objects 1-10).
Field 1 did not solve (index index-4114.fits, field objects 1-10).
Field 1 did not solve (index index-4113.fits, field objects 1-10).
Field 1 did not solve (index index-4112.fits, field objects 1-10).
Field 1 did not solve (index index-4111.fits, field objects 1-10).
Field 1 did not solve (index index-4110.fits, field objects 1-10).
Field 1 did not solve (index index-4109.fits, field objects 1-10).
Field 1 did not solve (index index-4108.fits, field objects 1-10).
Field 1 did not solve (index index-4107.fits, field objects 1-10).
Field 1 did not solve (index index-204-11.fits, field objects 1-10).
Field 1 did not solve (index index-204-10.fits, field objects 1-10).
Field 1 did not solve (index index-204-09.fits, field objects 1-10).
Field 1 did not solve (index index-204-08.fits, field objects 1-10).
Field 1 did not solve (index index-204-07.fits, field objects 1-10).
Field 1 did not solve (index index-204-06.fits, field objects 1-10).
Field 1 did not solve (index index-204-05.fits, field objects 1-10).
Field 1 did not solve (index index-204-04.fits, field objects 1-10).
Field 1 did not solve (index index-204-03.fits, field objects 1-10).
Field 1 did not solve (index index-204-02.fits, field objects 1-10).
Field 1 did not solve (index index-204-01.fits, field objects 1-10).
Field 1 did not solve (index index-204-00.fits, field objects 1-10).
Field 1 did not solve (index index-5203-47.fits, field objects 11-20).
Field 1 did not solve (index index-5203-46.fits, field objects 11-20).
Field 1 did not solve (index index-5203-45.fits, field objects 11-20).
Field 1 did not solve (index index-5203-44.fits, field objects 11-20).
Field 1 did not solve (index index-5203-43.fits, field objects 11-20).
Field 1 did not solve (index index-5203-42.fits, field objects 11-20).
Field 1 did not solve (index index-5203-41.fits, field objects 11-20).
Field 1 did not solve (index index-5203-40.fits, field objects 11-20).
Field 1 did not solve (index index-5203-39.fits, field objects 11-20).
Field 1 did not solve (index index-5203-38.fits, field objects 11-20).
Field 1 did not solve (index index-5203-37.fits, field objects 11-20).
Field 1 did not solve (index index-5203-36.fits, field objects 11-20).
Field 1 did not solve (index index-5203-35.fits, field objects 11-20).
Field 1 did not solve (index index-5203-34.fits, field objects 11-20).
Field 1 did not solve (index index-5203-33.fits, field objects 11-20).
Field 1 did not solve (index index-5203-32.fits, field objects 11-20).
Field 1 did not solve (index index-5203-31.fits, field objects 11-20).
Field 1 did not solve (index index-5203-30.fits, field objects 11-20).
Field 1 did not solve (index index-5203-29.fits, field objects 11-20).
Field 1 did not solve (index index-5203-28.fits, field objects 11-20).
Field 1 did not solve (index index-5203-27.fits, field objects 11-20).
Field 1 did not solve (index index-5203-26.fits, field objects 11-20).
Field 1 did not solve (index index-5203-25.fits, field objects 11-20).
Field 1 did not solve (index index-5203-24.fits, field objects 11-20).
Field 1 did not solve (index index-5203-23.fits, field objects 11-20).
Field 1 did not solve (index index-5203-22.fits, field objects 11-20).
Field 1 did not solve (index index-5203-21.fits, field objects 11-20).
Field 1 did not solve (index index-5203-20.fits, field objects 11-20).
Field 1 did not solve (index index-5203-19.fits, field objects 11-20).
Field 1 did not solve (index index-5203-18.fits, field objects 11-20).
Field 1 did not solve (index index-5203-17.fits, field objects 11-20).
Field 1 did not solve (index index-5203-16.fits, field objects 11-20).
Field 1 did not solve (index index-5203-15.fits, field objects 11-20).
Field 1 did not solve (index index-5203-14.fits, field objects 11-20).
Field 1 did not solve (index index-5203-13.fits, field objects 11-20).
Field 1 did not solve (index index-5203-12.fits, field objects 11-20).
Field 1 did not solve (index index-5203-11.fits, field objects 11-20).
Field 1 did not solve (index index-5203-10.fits, field objects 11-20).
Field 1 did not solve (index index-5203-09.fits, field objects 11-20).
Field 1 did not solve (index index-5203-08.fits, field objects 11-20).
Field 1 did not solve (index index-5203-07.fits, field objects 11-20).
Field 1 did not solve (index index-5203-06.fits, field objects 11-20).
Field 1 did not solve (index index-5203-05.fits, field objects 11-20).
Field 1 did not solve (index index-5203-04.fits, field objects 11-20).
Field 1 did not solve (index index-5203-03.fits, field objects 11-20).
Field 1 did not solve (index index-5203-02.fits, field objects 11-20).
Field 1 did not solve (index index-5203-01.fits, field objects 11-20).
Field 1 did not solve (index index-5203-00.fits, field objects 11-20).
Field 1 did not solve (index index-5005-11.fits, field objects 11-20).
Field 1 did not solve (index index-5005-10.fits, field objects 11-20).
Field 1 did not solve (index index-5005-09.fits, field objects 11-20).
Field 1 did not solve (index index-5005-08.fits, field objects 11-20).
Field 1 did not solve (index index-5005-07.fits, field objects 11-20).
Field 1 did not solve (index index-5005-06.fits, field objects 11-20).
Field 1 did not solve (index index-5005-05.fits, field objects 11-20).
Field 1 did not solve (index index-5005-04.fits, field objects 11-20).
Field 1 did not solve (index index-5005-03.fits, field objects 11-20).
Field 1 did not solve (index index-5005-02.fits, field objects 11-20).
Field 1 did not solve (index index-5005-01.fits, field objects 11-20).
Field 1 did not solve (index index-5005-00.fits, field objects 11-20).
Field 1 did not solve (index index-4206-11.fits, field objects 11-20).
Field 1 did not solve (index index-4206-10.fits, field objects 11-20).
Field 1 did not solve (index index-4206-09.fits, field objects 11-20).
Field 1 did not solve (index index-4206-08.fits, field objects 11-20).
Field 1 did not solve (index index-4206-07.fits, field objects 11-20).
Field 1 did not solve (index index-4206-06.fits, field objects 11-20).
Field 1 did not solve (index index-4206-05.fits, field objects 11-20).
Field 1 did not solve (index index-4206-04.fits, field objects 11-20).
Field 1 did not solve (index index-4206-03.fits, field objects 11-20).
Field 1 did not solve (index index-4206-02.fits, field objects 11-20).
Field 1 did not solve (index index-4206-01.fits, field objects 11-20).
Field 1 did not solve (index index-4206-00.fits, field objects 11-20).
Field 1 did not solve (index index-4205-11.fits, field objects 11-20).
Field 1 did not solve (index index-4205-10.fits, field objects 11-20).
Field 1 did not solve (index index-4205-09.fits, field objects 11-20).
Field 1 did not solve (index index-4205-08.fits, field objects 11-20).
Field 1 did not solve (index index-4205-07.fits, field objects 11-20).
Field 1 did not solve (index index-4205-06.fits, field objects 11-20).
Field 1 did not solve (index index-4205-05.fits, field objects 11-20).
Field 1 did not solve (index index-4205-04.fits, field objects 11-20).
Field 1 did not solve (index index-4205-03.fits, field objects 11-20).
Field 1 did not solve (index index-4205-02.fits, field objects 11-20).
Field 1 did not solve (index index-4205-01.fits, field objects 11-20).
Field 1 did not solve (index index-4205-00.fits, field objects 11-20).
Field 1 did not solve (index index-4119.fits, field objects 11-20).
Field 1 did not solve (index index-4118.fits, field objects 11-20).
Field 1 did not solve (index index-4117.fits, field objects 11-20).
Field 1 did not solve (index index-4116.fits, field objects 11-20).
Field 1 did not solve (index index-4115.fits, field objects 11-20).
Field 1 did not solve (index index-4114.fits, field objects 11-20).
Field 1 did not solve (index index-4113.fits, field objects 11-20).
Field 1 did not solve (index index-4112.fits, field objects 11-20).
Field 1 did not solve (index index-4111.fits, field objects 11-20).
Field 1 did not solve (index index-4110.fits, field objects 11-20).
Field 1 did not solve (index index-4109.fits, field objects 11-20).
Field 1 did not solve (index index-4108.fits, field objects 11-20).
Field 1 did not solve (index index-4107.fits, field objects 11-20).
Field 1 did not solve (index index-204-11.fits, field objects 11-20).
Field 1 did not solve (index index-204-10.fits, field objects 11-20).
Field 1 did not solve (index index-204-09.fits, field objects 11-20).
Field 1 did not solve (index index-204-08.fits, field objects 11-20).
Field 1 did not solve (index index-204-07.fits, field objects 11-20).
Field 1 did not solve (index index-204-06.fits, field objects 11-20).
Field 1 did not solve (index index-204-05.fits, field objects 11-20).
Field 1 did not solve (index index-204-04.fits, field objects 11-20).
Field 1 did not solve (index index-204-03.fits, field objects 11-20).
Field 1 did not solve (index index-204-02.fits, field objects 11-20).
Field 1 did not solve (index index-204-01.fits, field objects 11-20).
Field 1 did not solve (index index-204-00.fits, field objects 11-20).
Field 1 did not solve (index index-5203-47.fits, field objects 21-30).
Field 1 did not solve (index index-5203-46.fits, field objects 21-30).
Field 1 did not solve (index index-5203-45.fits, field objects 21-30).
Field 1 did not solve (index index-5203-44.fits, field objects 21-30).
Field 1 did not solve (index index-5203-43.fits, field objects 21-30).
Field 1 did not solve (index index-5203-42.fits, field objects 21-30).
Field 1 did not solve (index index-5203-41.fits, field objects 21-30).
Field 1 did not solve (index index-5203-40.fits, field objects 21-30).
Field 1 did not solve (index index-5203-39.fits, field objects 21-30).
Field 1 did not solve (index index-5203-38.fits, field objects 21-30).
Field 1 did not solve (index index-5203-37.fits, field objects 21-30).
Field 1 did not solve (index index-5203-36.fits, field objects 21-30).
Field 1 did not solve (index index-5203-35.fits, field objects 21-30).
Field 1 did not solve (index index-5203-34.fits, field objects 21-30).
Field 1 did not solve (index index-5203-33.fits, field objects 21-30).
Field 1 did not solve (index index-5203-32.fits, field objects 21-30).
Field 1 did not solve (index index-5203-31.fits, field objects 21-30).
Field 1 did not solve (index index-5203-30.fits, field objects 21-30).
Field 1 did not solve (index index-5203-29.fits, field objects 21-30).
Field 1 did not solve (index index-5203-28.fits, field objects 21-30).
Field 1 did not solve (index index-5203-27.fits, field objects 21-30).
Field 1 did not solve (index index-5203-26.fits, field objects 21-30).
Field 1 did not solve (index index-5203-25.fits, field objects 21-30).
Field 1 did not solve (index index-5203-24.fits, field objects 21-30).
Field 1 did not solve (index index-5203-23.fits, field objects 21-30).
Field 1 did not solve (index index-5203-22.fits, field objects 21-30).
Field 1 did not solve (index index-5203-21.fits, field objects 21-30).
Field 1 did not solve (index index-5203-20.fits, field objects 21-30).
Field 1 did not solve (index index-5203-19.fits, field objects 21-30).
Field 1 did not solve (index index-5203-18.fits, field objects 21-30).
Field 1 did not solve (index index-5203-17.fits, field objects 21-30).
Field 1 did not solve (index index-5203-16.fits, field objects 21-30).
Field 1 did not solve (index index-5203-15.fits, field objects 21-30).
Field 1 did not solve (index index-5203-14.fits, field objects 21-30).
Field 1 did not solve (index index-5203-13.fits, field objects 21-30).
Field 1 did not solve (index index-5203-12.fits, field objects 21-30).
Field 1 did not solve (index index-5203-11.fits, field objects 21-30).
Field 1 did not solve (index index-5203-10.fits, field objects 21-30).
Field 1 did not solve (index index-5203-09.fits, field objects 21-30).
Field 1 did not solve (index index-5203-08.fits, field objects 21-30).
Field 1 did not solve (index index-5203-07.fits, field objects 21-30).
Field 1 did not solve (index index-5203-06.fits, field objects 21-30).
Field 1 did not solve (index index-5203-05.fits, field objects 21-30).
Field 1 did not solve (index index-5203-04.fits, field objects 21-30).
Field 1 did not solve (index index-5203-03.fits, field objects 21-30).
Field 1 did not solve (index index-5203-02.fits, field objects 21-30).
Field 1 did not solve (index index-5203-01.fits, field objects 21-30).
Field 1 did not solve (index index-5203-00.fits, field objects 21-30).
Field 1 did not solve (index index-5005-11.fits, field objects 21-30).
Field 1 did not solve (index index-5005-10.fits, field objects 21-30).
Field 1 did not solve (index index-5005-09.fits, field objects 21-30).
Field 1 did not solve (index index-5005-08.fits, field objects 21-30).
Field 1 did not solve (index index-5005-07.fits, field objects 21-30).
Field 1 did not solve (index index-5005-06.fits, field objects 21-30).
Field 1 did not solve (index index-5005-05.fits, field objects 21-30).
Field 1 did not solve (index index-5005-04.fits, field objects 21-30).
Field 1 did not solve (index index-5005-03.fits, field objects 21-30).
Field 1 did not solve (index index-5005-02.fits, field objects 21-30).
Field 1 did not solve (index index-5005-01.fits, field objects 21-30).
Field 1 did not solve (index index-5005-00.fits, field objects 21-30).
Field 1 did not solve (index index-4206-11.fits, field objects 21-30).
Field 1 did not solve (index index-4206-10.fits, field objects 21-30).
Field 1 did not solve (index index-4206-09.fits, field objects 21-30).
Field 1 did not solve (index index-4206-08.fits, field objects 21-30).
Field 1 did not solve (index index-4206-07.fits, field objects 21-30).
Field 1 did not solve (index index-4206-06.fits, field objects 21-30).
Field 1 did not solve (index index-4206-05.fits, field objects 21-30).
Field 1 did not solve (index index-4206-04.fits, field objects 21-30).
Field 1 did not solve (index index-4206-03.fits, field objects 21-30).
Field 1 did not solve (index index-4206-02.fits, field objects 21-30).
Field 1 did not solve (index index-4206-01.fits, field objects 21-30).
Field 1 did not solve (index index-4206-00.fits, field objects 21-30).
Field 1 did not solve (index index-4205-11.fits, field objects 21-30).
Field 1 did not solve (index index-4205-10.fits, field objects 21-30).
Field 1 did not solve (index index-4205-09.fits, field objects 21-30).
Field 1 did not solve (index index-4205-08.fits, field objects 21-30).
Field 1 did not solve (index index-4205-07.fits, field objects 21-30).
Field 1 did not solve (index index-4205-06.fits, field objects 21-30).
Field 1 did not solve (index index-4205-05.fits, field objects 21-30).
Field 1 did not solve (index index-4205-04.fits, field objects 21-30).
Field 1 did not solve (index index-4205-03.fits, field objects 21-30).
Field 1 did not solve (index index-4205-02.fits, field objects 21-30).
Field 1 did not solve (index index-4205-01.fits, field objects 21-30).
Field 1 did not solve (index index-4205-00.fits, field objects 21-30).
Field 1 did not solve (index index-4119.fits, field objects 21-30).
Field 1 did not solve (index index-4118.fits, field objects 21-30).
Field 1 did not solve (index index-4117.fits, field objects 21-30).
Field 1 did not solve (index index-4116.fits, field objects 21-30).
Field 1 did not solve (index index-4115.fits, field objects 21-30).
Field 1 did not solve (index index-4114.fits, field objects 21-30).
Total CPU time limit reached!
Field 1 did not solve (index index-4113.fits, field objects 21-30).
Field: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
Did not solve (or no WCS file was written).
Checking if the catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits alredy exist and is non-empty...
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits was not found.
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
Generating wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat from image00004.cat
Catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat corresponding to the image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits created.
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
verification OK: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
Image size: 926.8'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:56.842 +54:01:36.38 J2000 4789.000 3195.000
### Converting SExtractor-derived pixel positions to celestial coordinates using xy2sky from WCSTools ###
### Converted positions of 25903 stars ###
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat' -> 'vast_debug_catalog_before_xy2sky_correction.cat.log'
'/data_ssd/NMW-TexasTech/workdir/vast_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/correct_sextractor_wcs_catalog_usingxy2sky2717086.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-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
WCS catalog name: wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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=2095, bad_region=4810, passed=25903
Got 25903 stars (including 19387 good ones) from the SExtractor catalog wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat
util/solve_plate_with_UCAC5 got 25903 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 926.8'
Seting catalog search parameters based on the expected field of view 926.8 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012872 (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.010298 (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 344.9607 through 0 to 14.8806, gap 14.8806 to 344.9607
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 322 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 232 matched stars entering correct_measured_positions(), 165 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.57"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 223 matched stars entering correct_measured_positions(), 5460 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.78"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
RA wraps around 0/360 boundary: field RA 344.9497 through 0 to 14.9062, gap 14.9062 to 344.9497
Reading UCAC5 zone files...
Searching UCAC5 zones 691 to 748 (Dec 48.2 to 59.3)
Done reading UCAC5 zone files...
Matched 408 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 338 matched stars entering correct_measured_positions(), 5522 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.58"
Accuracy estimation diagnostic: 331 matched stars entering correct_measured_positions(), 7532 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.85"
Excluding outliers - 331 stars left (next iteration limit 245)
WCS_QUALITY_DIAG: file=fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits N_match=331 sigma_overall_arcsec=11.179 sigma_q1_arcsec=27.334 sigma_q2_arcsec=30.999 sigma_q3_arcsec=7.898 sigma_q4_arcsec=11.009 n_q1=35 n_q2=15 n_q3=123 n_q4=158 worst_quadrant_to_overall_ratio=2.773
The image catalog is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits -region wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits): sigma 11.179->11.179, ratio 2.773->2.773; reverting to order 3
WARNING: 1st new image has sigma_overall_arcsec=10.982 -- 22.19x the reference average (0.495); plate solution may be of low accuracy
WARNING: 2nd new image has sigma_overall_arcsec=11.179 -- 22.58x the reference average (0.495); plate solution may be of low accuracy
WARNING: 1st new image has worst_quadrant_to_overall_ratio=2.917 -- 2.60x the reference average (1.122); plate solution may be of low accuracy
WARNING: 2nd new image has worst_quadrant_to_overall_ratio=2.773 -- 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-24_02-56-26_20.00sec_5.00C_LIGHT_0096_astrometric_residuals.png (334 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 3.81 arcsec)
plot_astrometric_residuals_xy.py: wrote wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097_astrometric_residuals.png (331 matched stars from wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits.wcscat.astrometric_residuals, image 9576x6388, median residual 3.69 arcsec)
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-56-26_20.00sec_5.00C_LIGHT_0096.fits'
Saving fully-calibrated image wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-06-24_CI_Cas-04-Q2b1x1_030443_TTUQ2b1x1_56346_y4p3BX8a/wcs_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097.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:14:54.68 +53:15:41.5: 12.87 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:59:49.92 +54:00:28.1: 11.78 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:16.16 +56:39:36.4: 11.71 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:46.35 +50:11:43.8: 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:59:40.13 +56:24:06.7: 12.30 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:17:35.62 +51:28:57.1: 15.60 +/- 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:02:20.04 +54:07:53.8: 12.49 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:05:16.16 +56:39:36.4: 11.71 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:14:54.68 +53:15:41.5: 12.88 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:46.35 +50:11:43.8: 15.62 +/- 99.00 upperlimit
Forced photometry reference-image weighted average: 12.87 +/- 0.02
Forced photometry reference-image weighted average: 11.71 +/- 0.01
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:59:49.92 +54:00:28.1: 11.76 +/- 0.01 detection
Forced photometry filter REJECTED candidate at 00:05:16.16 +56:39:36.4: ref_mag=11.71 +/- 0.01 new_mean_mag=11.7117 delta=-0.00 (need > 0.90)
Forced photometry filter KEPT candidate at 00:14:54.68 +53:15:41.5: ref_mag=12.87 +/- 0.02 new_mean_mag=11.5476 delta=1.33 (need > 0.90)
Forced photometry reference-image weighted average: 11.77 +/- 0.01
Forced photometry filter REJECTED candidate at 23:59:49.92 +54:00:28.1: ref_mag=11.77 +/- 0.01 new_mean_mag=11.8657 delta=-0.09 (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:59:40.13 +56:24:06.7: 12.23 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.26 +/- 0.01
Forced photometry filter REJECTED candidate at 23:59:40.13 +56:24:06.7: ref_mag=12.26 +/- 0.01 new_mean_mag=11.7017 delta=0.56 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:20.04 +54:07:53.8: 12.45 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:17:35.62 +51:28:57.1: 15.13 +/- 0.24 detection
Forced photometry reference-image weighted average: 12.47 +/- 0.01
Forced photometry filter REJECTED candidate at 00:02:20.04 +54:07:53.8: ref_mag=12.47 +/- 0.01 new_mean_mag=11.7105 delta=0.76 (need > 0.90)
Forced photometry reference-image weighted average: 15.13 +/- 0.24
Forced photometry filter KEPT candidate at 00:17:35.62 +51:28:57.1: ref_mag=15.13 +/- 0.24 new_mean_mag=11.7890 delta=3.34 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:57.95 +54:07:59.6: 13.19 +/- 0.04 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:16:04.92 +58:08:25.9: 12.04 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:47:41.31 +57:49:58.0: 11.99 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:57.95 +54:07:59.6: 13.07 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.13 +/- 0.03
Forced photometry filter KEPT candidate at 00:03:57.95 +54:07:59.6: ref_mag=13.13 +/- 0.03 new_mean_mag=11.9956 delta=1.13 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:16:04.92 +58:08:25.9: 12.04 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.04 +/- 0.01
Forced photometry filter REJECTED candidate at 00:16:04.92 +58:08:25.9: ref_mag=12.04 +/- 0.01 new_mean_mag=11.9860 delta=0.05 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:46:43.93 +51:45:27.9: 15.72 +/- 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:02:38.42 +53:39:39.6: 15.77 +/- 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:44:59.47 +57:58:35.5: 12.13 +/- 0.02 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:47:41.31 +57:49:58.0: 11.99 +/- 0.01 detection
Forced photometry reference-image weighted average: 11.99 +/- 0.01
Forced photometry filter REJECTED candidate at 23:47:41.31 +57:49:58.0: ref_mag=11.99 +/- 0.01 new_mean_mag=12.0426 delta=-0.05 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:08:00.55 +52:54:45.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:46:43.93 +51:45:27.9: 15.69 +/- 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:02:38.42 +53:39:39.6: 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 23:44:59.47 +57:58:35.5: 12.11 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.12 +/- 0.01
Forced photometry filter REJECTED candidate at 23:44:59.47 +57:58:35.5: ref_mag=12.12 +/- 0.01 new_mean_mag=12.1030 delta=0.02 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:08:00.55 +52:54:45.0: 15.84 +/- 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:52:57.20 +55:11:43.6: 12.15 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:56:10.80 +50:38:48.7: 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 00:00:59.75 +53:46:33.9: 15.71 +/- 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:57.20 +55:11:43.6: 12.13 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.14 +/- 0.01
Forced photometry filter REJECTED candidate at 23:52:57.20 +55:11:43.6: ref_mag=12.14 +/- 0.01 new_mean_mag=12.1073 delta=0.03 (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:56:10.80 +50:38:48.7: 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:00:59.75 +53:46:33.9: 15.69 +/- 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:58:53.45 +57:22:02.0: 12.17 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:53.45 +57:22:02.0: 12.18 +/- 0.02 detection
Forced photometry reference-image weighted average: 12.18 +/- 0.01
Forced photometry filter REJECTED candidate at 23:58:53.45 +57:22:02.0: ref_mag=12.18 +/- 0.01 new_mean_mag=12.1182 delta=0.06 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:04:10.26 +55:53:01.2: 12.15 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:04:10.26 +55:53:01.2: 12.15 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.15 +/- 0.01
Forced photometry filter REJECTED candidate at 00:04:10.26 +55:53:01.2: ref_mag=12.15 +/- 0.01 new_mean_mag=12.1165 delta=0.03 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:01:21.47 +55:06:38.8: 12.14 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:01:21.47 +55:06:38.8: 12.16 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.15 +/- 0.01
Forced photometry filter REJECTED candidate at 00:01:21.47 +55:06:38.8: ref_mag=12.15 +/- 0.01 new_mean_mag=12.1043 delta=0.04 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:12:20.42 +55:46:13.9: 12.17 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:12:20.42 +55:46:13.9: 12.16 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.16 +/- 0.01
Forced photometry filter REJECTED candidate at 00:12:20.42 +55:46:13.9: ref_mag=12.16 +/- 0.01 new_mean_mag=12.0979 delta=0.07 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:43:37.78 +52:09:44.1: 15.72 +/- 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:37.78 +52:09:44.1: 15.69 +/- 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:02:33.07 +54:00:25.4: 14.02 +/- 0.07 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:33.07 +54:00:25.4: 13.92 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.97 +/- 0.04
Forced photometry filter KEPT candidate at 00:02:33.07 +54:00:25.4: ref_mag=13.97 +/- 0.04 new_mean_mag=12.1090 delta=1.86 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:20:45.93 +55:40:43.8: 12.88 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:20:45.93 +55:40:43.8: 12.82 +/- 0.03 detection
Forced photometry reference-image weighted average: 12.85 +/- 0.02
Forced photometry filter REJECTED candidate at 00:20:45.93 +55:40:43.8: ref_mag=12.85 +/- 0.02 new_mean_mag=12.1009 delta=0.75 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:35.22 +56:48:24.2: 12.13 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:55:40.48 +52:35:18.8: 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:55:35.22 +56:48:24.2: 12.09 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.11 +/- 0.01
Forced photometry filter REJECTED candidate at 23:55:35.22 +56:48:24.2: ref_mag=12.11 +/- 0.01 new_mean_mag=12.1666 delta=-0.06 (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:55:40.48 +52:35:18.8: 15.70 +/- 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:51:16.81 +52:09:16.1: 15.82 +/- 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:20:14.58 +50:44:30.1: 13.20 +/- 0.03 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:03:43.54 +55:00:55.5: 12.08 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:51:16.81 +52:09:16.1: 15.79 +/- 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:02:02.38 +53:59:18.7: 13.92 +/- 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:20:14.58 +50:44:30.1: 13.31 +/- 0.04 detection
Forced photometry reference-image weighted average: 13.25 +/- 0.03
Forced photometry filter KEPT candidate at 00:20:14.58 +50:44:30.1: ref_mag=13.25 +/- 0.03 new_mean_mag=12.0757 delta=1.17 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:03:43.54 +55:00:55.5: 12.10 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.09 +/- 0.01
Forced photometry filter REJECTED candidate at 00:03:43.54 +55:00:55.5: ref_mag=12.09 +/- 0.01 new_mean_mag=12.0939 delta=-0.01 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:02:02.38 +53:59:18.7: 13.87 +/- 0.06 detection
Forced photometry reference-image weighted average: 13.89 +/- 0.04
Forced photometry filter KEPT candidate at 00:02:02.38 +53:59:18.7: ref_mag=13.89 +/- 0.04 new_mean_mag=12.1193 delta=1.77 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 00:05:25.23 +54:33:36.0: 12.19 +/- 0.01 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:52:20.14 +50:08:57.9: 15.58 +/- 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:25.23 +54:33:36.0: 12.15 +/- 0.01 detection
Forced photometry reference-image weighted average: 12.17 +/- 0.01
Forced photometry filter REJECTED candidate at 00:05:25.23 +54:33:36.0: ref_mag=12.17 +/- 0.01 new_mean_mag=12.1032 delta=0.06 (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:52:20.14 +50:08:57.9: 15.61 +/- 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:04:14.31 +50:01:22.7: 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 00:04:14.31 +50:01:22.7: 15.58 +/- 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:58:27.05 +51:26:14.3: 15.62 +/- 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:23:11.74 +55:47:35.3: 9.18 +/- 0.00 detection
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 23:58:27.05 +51:26:14.3: 15.47 +/- 0.33 detection
Forced photometry reference-image weighted average: 15.47 +/- 0.33
Forced photometry filter KEPT candidate at 23:58:27.05 +51:26:14.3: ref_mag=15.47 +/- 0.33 new_mean_mag=7.6007 delta=7.87 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-21-47_20.00sec_-15.00C_LIGHT_0007.fits at 00:23:11.74 +55:47:35.3: 9.22 +/- 0.00 detection
Forced photometry reference-image weighted average: 9.20 +/- 0.00
Forced photometry filter KEPT candidate at 00:23:11.74 +55:47:35.3: ref_mag=9.20 +/- 0.00 new_mean_mag=7.5243 delta=1.67 (need > 0.90)
Forced photometry on wcs_Cas-04-Q2b1x1_2026-02-10_20-20-38_20.00sec_-14.90C_LIGHT_0006.fits at 23:38:16.00 +56:01:54.0: 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 23:38:16.00 +56:01:54.0: 15.58 +/- 99.00 upperlimit
Adding exclusion_list_local.txt__out08367.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out09534.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21888.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out33336.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out34590.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out35494.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36082.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36158.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36301.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36438.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36534.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36546.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36641.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36646.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36676.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36684.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36686.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36702.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36751.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out36779.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 37s
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: 14s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 31480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31481_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 31481_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31482_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 31482_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32276_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 32276_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:04:40.85 +55:32:14.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 32380_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 32380_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (12.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33004_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 33004_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:06:02.61 +55:11:58.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33021_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 33021_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:44:31.87 +56:34:50.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33336_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 33336_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 33928_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 33928_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (25.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34590_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 34590_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34926_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 34926_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34990_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 34990_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:52:38.40 +56:44:35.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 34996_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 34996_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35494_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 35494_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35516_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 35516_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35563_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 35563_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (18.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35672_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 35672_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35896_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 35896_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:58:58.83 +54:51:09.2 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 35988_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 35988_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36018_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36018_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:01:49.05 +53:05:05.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36082_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36082_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36116_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36116_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36142_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36142_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36158_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36158_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36301_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36301_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36404_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36404_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36426_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36426_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36438_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36438_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36481_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36481_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36494_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36494_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36534_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36534_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36535_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36535_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36546_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36546_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36572_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36572_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36596_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36596_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36599_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36599_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36619_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36619_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36628_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36628_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36633_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36633_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36641_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36641_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36646_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36646_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36656_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36656_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36663_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36663_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36670_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36670_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36676_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36676_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36684_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36684_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36686_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36686_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36692_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36692_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36697_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36697_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36701_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36701_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36702_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36702_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36707_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36707_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36723_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36723_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36751_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36751_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36756_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36756_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36779_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 36779_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36879_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36879_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36929_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36929_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (13.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 36935_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 36935_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243704_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243704_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243718_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243718_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243736_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243736_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243738_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243738_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243739_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243739_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243745_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243745_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (25.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243747_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243747_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243749_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243749_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243750_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243750_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243753_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243753_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243777_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243777_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (20.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243783_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243783_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243785_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243785_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243789_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243789_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243793_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243793_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243794_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243794_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243797_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243797_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243799_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243799_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243801_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243801_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243805_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243805_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (35.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243807_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243807_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243811_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243811_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243813_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243813_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243815_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243815_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243820_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243820_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243829_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243829_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243831_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243831_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243833_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243833_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243835_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243835_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243836_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243836_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243839_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243839_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243840_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243840_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243841_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243841_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243842_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243842_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243844_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243844_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243847_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243847_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243849_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243849_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243852_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243852_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243854_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243854_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243855_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243855_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243859_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243859_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243860_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243860_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243863_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243863_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243866_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243866_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243868_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243868_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243873_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243873_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243874_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243874_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243875_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243875_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243876_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243876_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243884_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243884_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243886_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243886_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:45:59.31 +56:53:27.9 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243888_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243888_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243889_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243889_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243895_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243895_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243896_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243896_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243897_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243897_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243901_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 243901_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:59:16.63 +55:57:39.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 243902_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 243902_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 244861_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 244861_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245181_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 245181_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (21.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245580_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 245580_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:06:03.56 +55:11:55.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 245868_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 245868_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (25.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 246291_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 246291_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (18.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247169_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 247169_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247585_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 247585_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 247839_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 247839_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 248172_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 248172_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (31.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 249672_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 249672_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250488_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 250488_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 250746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 250746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:44:12.16 +56:38:09.5 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 251890_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 251890_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252346_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 252346_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:22:44.99 +57:06:32.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 252625_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 252625_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253026_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 253026_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253227_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 253227_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 253738_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 253738_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254192_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 254192_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 254860_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 254860_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255325_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 255325_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255755_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 255755_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 255769_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 255769_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 256331_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 256331_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 257775_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 257775_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259064_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 259064_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259305_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 259305_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259609_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 259609_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:38:56.42 +57:50:09.3 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259640_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 259640_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259671_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 259671_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259769_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 259769_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 259887_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 259887_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260273_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 260273_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260387_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 260387_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 260642_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 260642_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 261063_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 261063_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262086_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 262086_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262095_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 262095_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262472_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 262472_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 262512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262822_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 262822_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (18.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262920_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 262920_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (22.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 262982_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 262982_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263047_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 263047_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263183_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 263183_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:41:22.45 +57:32:51.6 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263334_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 263334_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263477_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 263477_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 263564_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 263564_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264371_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 264371_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264470_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 264470_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:12:36.98 +57:12:38.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264604_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 264604_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264823_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 264823_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264875_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 264875_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 264877_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 264877_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265137_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265137_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (32.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265405_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265405_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265438_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 265438_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265466_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 265466_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265483_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265483_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265489_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 265489_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265662_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265662_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265898_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265898_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (22.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 265986_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 265986_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266055_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 266055_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 266083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (21.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266105_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 266105_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266447_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 266447_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266670_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 266670_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266754_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 266754_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266934_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 266934_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:24:21.20 +53:13:46.2 in the exclusion list exclusion_list_tycho2.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 266974_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 266974_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267101_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267101_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267251_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267251_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267443_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267443_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267505_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267505_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267530_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267530_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267532_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267532_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267661_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 267661_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 267679_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 267679_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:20:28.33 +57:50:30.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268124_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 268124_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268293_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268293_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268346_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268346_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268372_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268372_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268381_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268381_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268704_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268704_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268858_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268858_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 268973_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 268973_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269028_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 269028_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269093_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 269093_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269184_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 269184_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269214_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 269214_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269314_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 269314_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269611_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 269611_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269658_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 269658_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269692_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 269692_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 269828_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 269828_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270591_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 270591_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270606_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 270606_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:55:43.19 +57:23:31.4 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270717_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 270717_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270804_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 270804_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270880_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 270880_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (33.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 270939_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 270939_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271003_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 271003_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271139_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 271139_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271169_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 271169_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271248_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 271248_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271262_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 271262_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271449_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 271449_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271470_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 271470_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 271520_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 271520_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272071_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 272071_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272134_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 272134_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272602_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 272602_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272727_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 272727_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272789_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 272789_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272962_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 272962_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 272997_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 272997_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273006_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273006_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273142_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273142_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273175_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 273175_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273274_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 273274_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273388_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273388_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273511_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 273511_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273612_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 273612_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273620_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273620_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273622_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273622_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273688_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 273688_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 273864_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 273864_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274082_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 274082_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274162_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 274162_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274207_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 274207_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274506_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 274506_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274538_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 274538_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 274978_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 274978_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (22.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275076_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 275076_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275261_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 275261_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275413_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 275413_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275418_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 275418_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275544_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 275544_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (13.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275554_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 275554_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 275929_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 275929_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (56.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276220_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 276220_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276342_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 276342_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 276778_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 276778_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277118_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 277118_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277170_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 277170_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277344_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 277344_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 277512_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (15.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277538_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 277538_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277786_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 277786_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 277812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 277911_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 277911_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 278083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (34.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278227_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 278227_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278442_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 278442_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 278933_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 278933_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279345_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 279345_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279716_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 279716_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 279898_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 279898_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280022_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 280022_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280044_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 280044_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280343_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 280343_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (35.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280473_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 280473_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280539_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 280539_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280578_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 280578_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 280791_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 280791_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 281083_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281095_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 281095_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 281480_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281936_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 281936_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281949_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 281949_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (30.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 281956_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 281956_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282002_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 282002_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282015_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282015_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282090_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 282090_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282264_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282264_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282353_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282353_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282429_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282429_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282757_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282757_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 282909_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 282909_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283042_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283042_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (11.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283124_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 283124_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283178_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283178_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283249_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283249_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283277_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283277_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283318_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283318_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283360_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283360_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283374_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283374_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283447_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 283447_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283548_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 283548_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283728_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 283728_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283796_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 283796_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 283971_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 283971_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284190_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284190_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284217_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284217_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284228_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284228_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284288_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284288_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284304_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284304_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284331_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284331_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284349_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284349_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (28.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284383_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284383_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284396_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284396_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284442_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284442_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284681_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284681_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284689_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284689_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284733_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284733_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284755_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284755_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284815_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284815_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (25.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284859_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284859_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284913_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284913_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284922_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 284922_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 284994_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 284994_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285022_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285022_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285032_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285032_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285043_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285043_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285044_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285044_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285073_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285073_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285187_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285187_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285252_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285252_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285267_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285267_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (13.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285318_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285318_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (23.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285340_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285340_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285343_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285343_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285386_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285386_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285448_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285448_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (23.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285499_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285499_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285526_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285526_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285536_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285536_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285572_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285572_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (17.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285658_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285658_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285732_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285742_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285742_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285746_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285750_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285750_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 285812_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285878_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285878_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (15.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285888_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285888_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285892_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285892_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 285998_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 285998_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286088_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 286088_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286090_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 286090_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286102_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 286102_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286157_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 286157_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286370_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 286370_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 286503_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 286503_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 287067_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 287067_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 287337_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 287337_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69970_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 69970_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 174810_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 174810_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 130430_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 130430_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (26.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 117774_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 117774_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:02:02.89 +53:59:15.3 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 177194_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 177194_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 58579_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 58579_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:44:32.42 +56:34:50.8 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 79234_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 79234_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 160198_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 160198_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 179137_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 179137_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 00:20:46.50 +50:11:46.6 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 98268_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 98268_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 105557_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 105557_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (19.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 171436_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 171436_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (20.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 125040_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 125040_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
Rejecting candidate due to large distance (16.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 53473_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 53473_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:52:39.22 +56:44:33.4 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 119320_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 119320_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 71796_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
The candidate 71796_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097 did not pass the final checks
**** FOUND 23:38:16.45 +56:01:56.7 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143637_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
Preparing report for the candidate 143637_fd_Cas-04-Q2b1x1_2026-06-24_02-57-07_20.00sec_5.00C_LIGHT_0097
make_report_in_HTML.sh Phase 2 (HTML assembly): 25s
make_report_in_HTML.sh TOTAL: 560s
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 ####
00:23:11.74 +55:47:35.3
23:38:16.00 +56:01:54.0
23:58:27.05 +51:26:14.3
00:20:46.35 +50:11:43.8
00:14:54.68 +53:15:41.5
00:17:35.62 +51:28:57.1
00:03:57.95 +54:07:59.6
00:02:38.42 +53:39:39.6
23:46:43.93 +51:45:27.9
00:08:00.55 +52:54:45.0
23:56:10.80 +50:38:48.7
00:00:59.75 +53:46:33.9
23:43:37.78 +52:09:44.1
00:02:33.07 +54:00:25.4
23:55:40.48 +52:35:18.8
23:51:16.81 +52:09:16.1
00:20:14.58 +50:44:30.1
00:02:02.38 +53:59:18.7
23:52:20.14 +50:08:57.9
00:04:14.31 +50:01:22.7
00:18:30.00 +53:39:27.2
00:13:25.75 +52:37:42.8
23:57:27.85 +52:04:36.7
23:58:25.86 +51:26:15.9
23:34:59.80 +50:35:49.8
00:01:08.45 +56:27:05.4
23:42:06.30 +55:02:24.9
00:08:07.20 +54:56:34.4
23:43:07.09 +53:23:28.1
00:02:59.15 +51:30:26.5
23:31:33.68 +56:51:42.4
23:42:27.86 +53:37:18.0
23:30:46.10 +56:37:26.0
23:32:21.78 +54:31:58.0
23:30:43.51 +51:31:34.5
00:00:11.35 +53:25:56.9
23:36:59.90 +53:05:01.7
23:30:35.20 +53:35:49.8
23:36:31.48 +54:23:09.4
23:42:55.34 +53:06:04.8
23:35:18.02 +54:24:57.3
00:08:06.73 +54:49:22.0
23:38:58.59 +51:32:10.6
23:44:02.93 +52:45:35.2
00:08:49.88 +50:55:59.7
23:31:18.09 +55:42:25.5
23:35:59.94 +56:49:21.3
23:30:04.32 +55:55:29.3
23:36:59.39 +56:58:25.7
23:55:25.83 +51:47:36.6
00:01:49.28 +50:18:52.1
23:31:53.16 +51:39:04.1
23:29:17.10 +55:18:52.3
00:22:29.68 +50:18:56.0
23:37:54.53 +52:05:24.9
23:39:01.86 +52:18:14.9
00:14:55.44 +53:15:47.3
23:31:40.28 +57:27:22.9
23:31:59.91 +55:07:36.7
23:41:55.17 +52:45:28.4
00:07:39.42 +53:34:06.0
23:47:36.08 +52:37:54.3
23:43:07.15 +52:00:53.7
23:39:32.32 +52:05:01.1
23:38:55.92 +51:35:18.2
23:30:03.60 +54:40:05.4
23:33:33.56 +50:54:49.4
23:41:05.57 +52:46:43.3
00:04:16.40 +50:02:31.6
00:05:01.55 +51:13:22.9
23:34:21.05 +54:04:08.8
00:19:42.93 +50:48:25.6
23:51:10.27 +51:26:07.1
23:33:32.02 +56:43:57.2
23:36:57.43 +55:34:22.6
00:12:16.02 +57:18:54.5
00:27:54.16 +52:58:19.3
23:35:04.15 +50:23:35.1
23:43:27.65 +51:45:09.0
23:43:10.12 +52:00:37.3
23:42:02.11 +57:24:41.8
00:18:12.84 +54:09:31.4
23:30:29.03 +55:42:38.3
23:57:06.91 +52:12:21.2
00:19:48.27 +51:04:46.8
23:51:59.45 +56:02:30.5
23:32:13.49 +55:32:49.6
23:44:10.52 +53:03:33.5
23:51:33.93 +51:33:35.4
23:35:17.66 +55:37:21.9
23:38:10.32 +52:43:48.9
23:29:09.11 +56:37:33.8
00:18:52.21 +57:49:38.8
00:06:22.19 +52:40:37.3
00:10:00.85 +50:50:02.0
23:43:06.18 +52:46:20.8
23:41:29.16 +52:56:27.7
00:01:19.68 +51:15:18.6
23:42:24.87 +53:39:49.0
23:38:25.92 +55:22:20.3
23:40:11.86 +51:49:34.2
23:34:16.39 +54:04:44.7
23:46:45.93 +52:24:14.0
00:08:30.90 +51:27:29.8
23:56:55.59 +56:39:55.6
23:32:28.28 +53:27:00.9
23:41:22.00 +55:49:29.6
00:07:47.70 +50:06:41.9
23:40:54.60 +53:47:05.5
23:33:36.56 +53:30:57.9
23:34:16.76 +54:25:03.6
23:32:09.20 +53:57:19.8
23:28:36.21 +57:27:57.2
23:29:51.09 +56:53:56.4
23:35:21.51 +56:13:47.8
23:31:44.84 +51:29:36.6
23:47:57.58 +54:15:32.2
23:36:56.22 +52:44:46.2
23:52:16.62 +51:29:29.7
23:29:19.98 +54:59:47.1
23:31:23.21 +54:32:01.3
23:29:30.64 +56:07:01.5
23:37:58.17 +52:39:44.2
23:36:32.87 +53:13:26.0
23:33:53.40 +54:37:16.9
23:30:47.25 +56:59:47.3
23:31:09.91 +50:06:30.9
23:31:39.19 +51:36:24.3
23:36:30.85 +57:01:15.2
23:32:59.53 +56:40:19.7
23:30:06.40 +53:32:17.7
23:31:51.43 +51:36:18.3
23:29:41.77 +57:15:16.9
23:31:53.48 +56:22:32.9
23:40:41.80 +51:33:51.3
23:30:23.05 +54:28:32.9
23:32:01.34 +57:16:57.3
23:32:04.03 +55:15:39.7
23:40:24.51 +54:53:56.5
23:42:10.97 +56:45:18.7
23:31:21.75 +54:44:10.3
23:41:49.94 +53:59:51.3
23:42:24.06 +55:49:09.1
23:31:20.85 +50:23:20.5
23:39:52.36 +52:19:51.6
23:31:13.06 +51:41:37.4
23:50:58.60 +50:27:24.9
23:41:49.20 +52:55:47.4
00:13:10.02 +50:37:08.4
00:06:32.77 +52:20:36.8
00:06:57.77 +51:44:16.0
00:23:10.55 +55:47:26.4
00:04:41.20 +55:32:15.1
23:58:59.85 +54:51:05.1
########### 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 ####
00:20:46.35 +50:11:43.8
00:14:54.68 +53:15:41.5
00:17:35.62 +51:28:57.1
00:03:57.95 +54:07:59.6
00:02:38.42 +53:39:39.6
23:46:43.93 +51:45:27.9
00:08:00.55 +52:54:45.0
23:56:10.80 +50:38:48.7
00:00:59.75 +53:46:33.9
23:43:37.78 +52:09:44.1
00:02:33.07 +54:00:25.4
23:55:40.48 +52:35:18.8
23:51:16.81 +52:09:16.1
00:20:14.58 +50:44:30.1
00:02:02.38 +53:59:18.7
23:52:20.14 +50:08:57.9
00:04:14.31 +50:01:22.7
23:58:27.05 +51:26:14.3
00:23:11.74 +55:47:35.3
23:38:16.00 +56:01:54.0
00:01:08.45 +56:27:05.4
23:42:06.30 +55:02:24.9
00:08:07.20 +54:56:34.4
23:43:07.09 +53:23:28.1
00:02:59.15 +51:30:26.5
23:31:33.68 +56:51:42.4
23:42:27.86 +53:37:18.0
23:30:46.10 +56:37:26.0
23:32:21.78 +54:31:58.0
23:30:43.51 +51:31:34.5
00:00:11.35 +53:25:56.9
23:36:59.90 +53:05:01.7
23:30:35.20 +53:35:49.8
23:36:31.48 +54:23:09.4
23:42:55.34 +53:06:04.8
23:35:18.02 +54:24:57.3
00:08:06.73 +54:49:22.0
23:38:58.59 +51:32:10.6
23:44:02.93 +52:45:35.2
00:08:49.88 +50:55:59.7
23:31:18.09 +55:42:25.5
23:35:59.94 +56:49:21.3
23:30:04.32 +55:55:29.3
23:36:59.39 +56:58:25.7
23:55:25.83 +51:47:36.6
00:01:49.28 +50:18:52.1
23:31:53.16 +51:39:04.1
23:29:17.10 +55:18:52.3
00:22:29.68 +50:18:56.0
23:37:54.53 +52:05:24.9
23:39:01.86 +52:18:14.9
00:14:55.44 +53:15:47.3
23:31:40.28 +57:27:22.9
23:31:59.91 +55:07:36.7
23:41:55.17 +52:45:28.4
00:07:39.42 +53:34:06.0
23:47:36.08 +52:37:54.3
23:43:07.15 +52:00:53.7
23:39:32.32 +52:05:01.1
23:38:55.92 +51:35:18.2
23:30:03.60 +54:40:05.4
23:33:33.56 +50:54:49.4
23:41:05.57 +52:46:43.3
00:04:16.40 +50:02:31.6
00:05:01.55 +51:13:22.9
23:34:21.05 +54:04:08.8
00:19:42.93 +50:48:25.6
23:51:10.27 +51:26:07.1
23:33:32.02 +56:43:57.2
23:36:57.43 +55:34:22.6
00:12:16.02 +57:18:54.5
00:27:54.16 +52:58:19.3
23:35:04.15 +50:23:35.1
23:43:27.65 +51:45:09.0
23:43:10.12 +52:00:37.3
23:42:02.11 +57:24:41.8
00:18:12.84 +54:09:31.4
23:30:29.03 +55:42:38.3
23:57:06.91 +52:12:21.2
00:19:48.27 +51:04:46.8
23:51:59.45 +56:02:30.5
23:32:13.49 +55:32:49.6
23:44:10.52 +53:03:33.5
23:51:33.93 +51:33:35.4
23:35:17.66 +55:37:21.9
23:38:10.32 +52:43:48.9
23:29:09.11 +56:37:33.8
00:18:52.21 +57:49:38.8
00:06:22.19 +52:40:37.3
00:10:00.85 +50:50:02.0
23:43:06.18 +52:46:20.8
23:41:29.16 +52:56:27.7
00:01:19.68 +51:15:18.6
23:42:24.87 +53:39:49.0
23:38:25.92 +55:22:20.3
23:40:11.86 +51:49:34.2
23:34:16.39 +54:04:44.7
23:46:45.93 +52:24:14.0
00:08:30.90 +51:27:29.8
23:56:55.59 +56:39:55.6
23:32:28.28 +53:27:00.9
23:41:22.00 +55:49:29.6
00:07:47.70 +50:06:41.9
23:40:54.60 +53:47:05.5
23:33:36.56 +53:30:57.9
23:34:16.76 +54:25:03.6
23:32:09.20 +53:57:19.8
23:28:36.21 +57:27:57.2
23:29:51.09 +56:53:56.4
23:35:21.51 +56:13:47.8
23:31:44.84 +51:29:36.6
23:47:57.58 +54:15:32.2
23:36:56.22 +52:44:46.2
23:52:16.62 +51:29:29.7
23:29:19.98 +54:59:47.1
23:31:23.21 +54:32:01.3
23:29:30.64 +56:07:01.5
23:37:58.17 +52:39:44.2
23:36:32.87 +53:13:26.0
23:33:53.40 +54:37:16.9
23:30:47.25 +56:59:47.3
23:31:09.91 +50:06:30.9
23:31:39.19 +51:36:24.3
23:36:30.85 +57:01:15.2
23:32:59.53 +56:40:19.7
23:30:06.40 +53:32:17.7
23:31:51.43 +51:36:18.3
23:29:41.77 +57:15:16.9
23:31:53.48 +56:22:32.9
23:40:41.80 +51:33:51.3
23:30:23.05 +54:28:32.9
23:32:01.34 +57:16:57.3
23:32:04.03 +55:15:39.7
23:40:24.51 +54:53:56.5
23:42:10.97 +56:45:18.7
23:31:21.75 +54:44:10.3
23:41:49.94 +53:59:51.3
23:42:24.06 +55:49:09.1
23:31:20.85 +50:23:20.5
23:39:52.36 +52:19:51.6
23:31:13.06 +51:41:37.4
23:50:58.60 +50:27:24.9
23:41:49.20 +52:55:47.4
00:13:10.02 +50:37:08.4
00:06:32.77 +52:20:36.8
00:06:57.77 +51:44:16.0
00:23:10.55 +55:47:26.4
23:58:25.86 +51:26:15.9
23:34:59.80 +50:35:49.8
00:04:41.20 +55:32:15.1
23:57:27.85 +52:04:36.7
23:58:59.85 +54:51:05.1
00:18:30.00 +53:39:27.2
00:13:25.75 +52:37:42.8
###################################################################################
00:20:46.35 +50:11:43.8 -- not an asteroid (will add it to exclusion list)
00:14:54.68 +53:15:41.5 -- not an asteroid (will add it to exclusion list)
00:17:35.62 +51:28:57.1 -- not an asteroid (will add it to exclusion list)
00:03:57.95 +54:07:59.6 -- not an asteroid (will add it to exclusion list)
00:02:38.42 +53:39:39.6 -- not an asteroid (will add it to exclusion list)
23:46:43.93 +51:45:27.9 -- not an asteroid (will add it to exclusion list)
00:08:00.55 +52:54:45.0 -- not an asteroid (will add it to exclusion list)
23:56:10.80 +50:38:48.7 -- not an asteroid (will add it to exclusion list)
00:00:59.75 +53:46:33.9 -- not an asteroid (will add it to exclusion list)
23:43:37.78 +52:09:44.1 -- not an asteroid (will add it to exclusion list)
00:02:33.07 +54:00:25.4 -- not an asteroid (will add it to exclusion list)
23:55:40.48 +52:35:18.8 -- not an asteroid (will add it to exclusion list)
23:51:16.81 +52:09:16.1 -- not an asteroid (will add it to exclusion list)
00:20:14.58 +50:44:30.1 -- not an asteroid (will add it to exclusion list)
00:02:02.38 +53:59:18.7 -- not an asteroid (will add it to exclusion list)
23:52:20.14 +50:08:57.9 -- not an asteroid (will add it to exclusion list)
00:04:14.31 +50:01:22.7 -- not an asteroid (will add it to exclusion list)
23:58:27.05 +51:26:14.3 -- not an asteroid (will add it to exclusion list)
00:23:11.74 +55:47:35.3 -- not an asteroid (will add it to exclusion list)
23:38:16.00 +56:01:54.0 -- not an asteroid (will add it to exclusion list)
00:01:08.45 +56:27:05.4 -- not an asteroid (will add it to exclusion list)
23:42:06.30 +55:02:24.9 -- not an asteroid (will add it to exclusion list)
00:08:07.20 +54:56:34.4 -- not an asteroid (will add it to exclusion list)
23:43:07.09 +53:23:28.1 -- not an asteroid (will add it to exclusion list)
00:02:59.15 +51:30:26.5 -- not an asteroid (will add it to exclusion list)
23:31:33.68 +56:51:42.4 -- not an asteroid (will add it to exclusion list)
23:42:27.86 +53:37:18.0 -- not an asteroid (will add it to exclusion list)
23:30:46.10 +56:37:26.0 -- not an asteroid (will add it to exclusion list)
23:32:21.78 +54:31:58.0 -- not an asteroid (will add it to exclusion list)
23:30:43.51 +51:31:34.5 -- not an asteroid (will add it to exclusion list)
00:00:11.35 +53:25:56.9 -- not an asteroid (will add it to exclusion list)
23:36:59.90 +53:05:01.7 -- not an asteroid (will add it to exclusion list)
23:30:35.20 +53:35:49.8 -- not an asteroid (will add it to exclusion list)
23:36:31.48 +54:23:09.4 -- not an asteroid (will add it to exclusion list)
23:42:55.34 +53:06:04.8 -- not an asteroid (will add it to exclusion list)
23:35:18.02 +54:24:57.3 -- not an asteroid (will add it to exclusion list)
00:08:06.73 +54:49:22.0 -- not an asteroid (will add it to exclusion list)
23:38:58.59 +51:32:10.6 -- not an asteroid (will add it to exclusion list)
23:44:02.93 +52:45:35.2 -- not an asteroid (will add it to exclusion list)
00:08:49.88 +50:55:59.7 -- not an asteroid (will add it to exclusion list)
23:31:18.09 +55:42:25.5 -- not an asteroid (will add it to exclusion list)
23:35:59.94 +56:49:21.3 -- not an asteroid (will add it to exclusion list)
23:30:04.32 +55:55:29.3 -- not an asteroid (will add it to exclusion list)
23:36:59.39 +56:58:25.7 -- not an asteroid (will add it to exclusion list)
23:55:25.83 +51:47:36.6 -- not an asteroid (will add it to exclusion list)
00:01:49.28 +50:18:52.1 -- not an asteroid (will add it to exclusion list)
23:31:53.16 +51:39:04.1 -- not an asteroid (will add it to exclusion list)
23:29:17.10 +55:18:52.3 -- not an asteroid (will add it to exclusion list)
00:22:29.68 +50:18:56.0 -- not an asteroid (will add it to exclusion list)
23:37:54.53 +52:05:24.9 -- not an asteroid (will add it to exclusion list)
23:39:01.86 +52:18:14.9 -- not an asteroid (will add it to exclusion list)
00:14:55.44 +53:15:47.3 -- not an asteroid (will add it to exclusion list)
23:31:40.28 +57:27:22.9 -- not an asteroid (will add it to exclusion list)
23:31:59.91 +55:07:36.7 -- not an asteroid (will add it to exclusion list)
23:41:55.17 +52:45:28.4 -- not an asteroid (will add it to exclusion list)
00:07:39.42 +53:34:06.0 -- not an asteroid (will add it to exclusion list)
23:47:36.08 +52:37:54.3 -- not an asteroid (will add it to exclusion list)
23:43:07.15 +52:00:53.7 -- not an asteroid (will add it to exclusion list)
23:39:32.32 +52:05:01.1 -- not an asteroid (will add it to exclusion list)
23:38:55.92 +51:35:18.2 -- not an asteroid (will add it to exclusion list)
23:30:03.60 +54:40:05.4 -- not an asteroid (will add it to exclusion list)
23:33:33.56 +50:54:49.4 -- not an asteroid (will add it to exclusion list)
23:41:05.57 +52:46:43.3 -- not an asteroid (will add it to exclusion list)
00:04:16.40 +50:02:31.6 -- not an asteroid (will add it to exclusion list)
00:05:01.55 +51:13:22.9 -- not an asteroid (will add it to exclusion list)
23:34:21.05 +54:04:08.8 -- not an asteroid (will add it to exclusion list)
00:19:42.93 +50:48:25.6 -- not an asteroid (will add it to exclusion list)
23:51:10.27 +51:26:07.1 -- not an asteroid (will add it to exclusion list)
23:33:32.02 +56:43:57.2 -- not an asteroid (will add it to exclusion list)
23:36:57.43 +55:34:22.6 -- not an asteroid (will add it to exclusion list)
00:12:16.02 +57:18:54.5 -- not an asteroid (will add it to exclusion list)
00:27:54.16 +52:58:19.3 -- not an asteroid (will add it to exclusion list)
23:35:04.15 +50:23:35.1 -- not an asteroid (will add it to exclusion list)
23:43:27.65 +51:45:09.0 -- not an asteroid (will add it to exclusion list)
23:43:10.12 +52:00:37.3 -- not an asteroid (will add it to exclusion list)
23:42:02.11 +57:24:41.8 -- not an asteroid (will add it to exclusion list)
00:18:12.84 +54:09:31.4 -- not an asteroid (will add it to exclusion list)
23:30:29.03 +55:42:38.3 -- not an asteroid (will add it to exclusion list)
23:57:06.91 +52:12:21.2 -- not an asteroid (will add it to exclusion list)
00:19:48.27 +51:04:46.8 -- not an asteroid (will add it to exclusion list)
23:51:59.45 +56:02:30.5 -- not an asteroid (will add it to exclusion list)
23:32:13.49 +55:32:49.6 -- not an asteroid (will add it to exclusion list)
23:44:10.52 +53:03:33.5 -- not an asteroid (will add it to exclusion list)
23:51:33.93 +51:33:35.4 -- not an asteroid (will add it to exclusion list)
23:35:17.66 +55:37:21.9 -- not an asteroid (will add it to exclusion list)
23:38:10.32 +52:43:48.9 -- not an asteroid (will add it to exclusion list)
23:29:09.11 +56:37:33.8 -- not an asteroid (will add it to exclusion list)
00:18:52.21 +57:49:38.8 -- not an asteroid (will add it to exclusion list)
00:06:22.19 +52:40:37.3 -- not an asteroid (will add it to exclusion list)
00:10:00.85 +50:50:02.0 -- not an asteroid (will add it to exclusion list)
23:43:06.18 +52:46:20.8 -- not an asteroid (will add it to exclusion list)
23:41:29.16 +52:56:27.7 -- not an asteroid (will add it to exclusion list)
00:01:19.68 +51:15:18.6 -- not an asteroid (will add it to exclusion list)
23:42:24.87 +53:39:49.0 -- not an asteroid (will add it to exclusion list)
23:38:25.92 +55:22:20.3 -- not an asteroid (will add it to exclusion list)
23:40:11.86 +51:49:34.2 -- not an asteroid (will add it to exclusion list)
23:34:16.39 +54:04:44.7 -- not an asteroid (will add it to exclusion list)
23:46:45.93 +52:24:14.0 -- not an asteroid (will add it to exclusion list)
00:08:30.90 +51:27:29.8 -- not an asteroid (will add it to exclusion list)
23:56:55.59 +56:39:55.6 -- not an asteroid (will add it to exclusion list)
23:32:28.28 +53:27:00.9 -- not an asteroid (will add it to exclusion list)
23:41:22.00 +55:49:29.6 -- not an asteroid (will add it to exclusion list)
00:07:47.70 +50:06:41.9 -- not an asteroid (will add it to exclusion list)
23:40:54.60 +53:47:05.5 -- not an asteroid (will add it to exclusion list)
23:33:36.56 +53:30:57.9 -- not an asteroid (will add it to exclusion list)
23:34:16.76 +54:25:03.6 -- not an asteroid (will add it to exclusion list)
23:32:09.20 +53:57:19.8 -- not an asteroid (will add it to exclusion list)
23:28:36.21 +57:27:57.2 -- not an asteroid (will add it to exclusion list)
23:29:51.09 +56:53:56.4 -- not an asteroid (will add it to exclusion list)
23:35:21.51 +56:13:47.8 -- not an asteroid (will add it to exclusion list)
23:31:44.84 +51:29:36.6 -- not an asteroid (will add it to exclusion list)
23:47:57.58 +54:15:32.2 -- not an asteroid (will add it to exclusion list)
23:36:56.22 +52:44:46.2 -- not an asteroid (will add it to exclusion list)
23:52:16.62 +51:29:29.7 -- not an asteroid (will add it to exclusion list)
23:29:19.98 +54:59:47.1 -- not an asteroid (will add it to exclusion list)
23:31:23.21 +54:32:01.3 -- not an asteroid (will add it to exclusion list)
23:29:30.64 +56:07:01.5 -- not an asteroid (will add it to exclusion list)
23:37:58.17 +52:39:44.2 -- not an asteroid (will add it to exclusion list)
23:36:32.87 +53:13:26.0 -- not an asteroid (will add it to exclusion list)
23:33:53.40 +54:37:16.9 -- not an asteroid (will add it to exclusion list)
23:30:47.25 +56:59:47.3 -- not an asteroid (will add it to exclusion list)
23:31:09.91 +50:06:30.9 -- not an asteroid (will add it to exclusion list)
23:31:39.19 +51:36:24.3 -- not an asteroid (will add it to exclusion list)
23:36:30.85 +57:01:15.2 -- not an asteroid (will add it to exclusion list)
23:32:59.53 +56:40:19.7 -- not an asteroid (will add it to exclusion list)
23:30:06.40 +53:32:17.7 -- not an asteroid (will add it to exclusion list)
23:31:51.43 +51:36:18.3 -- not an asteroid (will add it to exclusion list)
23:29:41.77 +57:15:16.9 -- not an asteroid (will add it to exclusion list)
23:31:53.48 +56:22:32.9 -- not an asteroid (will add it to exclusion list)
23:40:41.80 +51:33:51.3 -- not an asteroid (will add it to exclusion list)
23:30:23.05 +54:28:32.9 -- not an asteroid (will add it to exclusion list)
23:32:01.34 +57:16:57.3 -- not an asteroid (will add it to exclusion list)
23:32:04.03 +55:15:39.7 -- not an asteroid (will add it to exclusion list)
23:40:24.51 +54:53:56.5 -- not an asteroid (will add it to exclusion list)
23:42:10.97 +56:45:18.7 -- not an asteroid (will add it to exclusion list)
23:31:21.75 +54:44:10.3 -- not an asteroid (will add it to exclusion list)
23:41:49.94 +53:59:51.3 -- not an asteroid (will add it to exclusion list)
23:42:24.06 +55:49:09.1 -- not an asteroid (will add it to exclusion list)
23:31:20.85 +50:23:20.5 -- not an asteroid (will add it to exclusion list)
23:39:52.36 +52:19:51.6 -- not an asteroid (will add it to exclusion list)
23:31:13.06 +51:41:37.4 -- not an asteroid (will add it to exclusion list)
23:50:58.60 +50:27:24.9 -- not an asteroid (will add it to exclusion list)
23:41:49.20 +52:55:47.4 -- not an asteroid (will add it to exclusion list)
00:13:10.02 +50:37:08.4 -- not an asteroid (will add it to exclusion list)
00:06:32.77 +52:20:36.8 -- not an asteroid (will add it to exclusion list)
00:06:57.77 +51:44:16.0 -- not an asteroid (will add it to exclusion list)
00:23:10.55 +55:47:26.4 -- not an asteroid (will add it to exclusion list)
23:58:25.86 +51:26:15.9 -- not an asteroid (will add it to exclusion list)
23:34:59.80 +50:35:49.8 -- not an asteroid (will add it to exclusion list)
00:04:41.20 +55:32:15.1 -- not an asteroid (will add it to exclusion list)
23:57:27.85 +52:04:36.7 -- not an asteroid (will add it to exclusion list)
23:58:59.85 +54:51:05.1 -- not an asteroid (will add it to exclusion list)
00:18:30.00 +53:39:27.2 -- not an asteroid (will add it to exclusion list)
00:13:25.75 +52:37:42.8 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
00:00:11.35 +53:25:56.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:00:59.75 +53:46:33.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:08.45 +56:27:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:19.68 +51:15:18.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:01:49.28 +50:18:52.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:02.38 +53:59:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:33.07 +54:00:25.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:38.42 +53:39:39.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:02:59.15 +51:30:26.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:03:57.95 +54:07:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:14.31 +50:01:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:16.40 +50:02:31.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:04:41.20 +55:32:15.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:05:01.55 +51:13:22.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:22.19 +52:40:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:32.77 +52:20:36.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:06:57.77 +51:44:16.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:39.42 +53:34:06.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:07:47.70 +50:06:41.9 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:00.55 +52:54:45.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:06.73 +54:49:22.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:07.20 +54:56:34.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:30.90 +51:27:29.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:08:49.88 +50:55:59.7 -- does not seem to be a hot pixel (will add it to exclusion list)
00:10:00.85 +50:50:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:12:16.02 +57:18:54.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:10.02 +50:37:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:13:25.75 +52:37:42.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:54.68 +53:15:41.5 -- does not seem to be a hot pixel (will add it to exclusion list)
00:14:55.44 +53:15:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:17:35.62 +51:28:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:12.84 +54:09:31.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:30.00 +53:39:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
00:18:52.21 +57:49:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:42.93 +50:48:25.6 -- does not seem to be a hot pixel (will add it to exclusion list)
00:19:48.27 +51:04:46.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:14.58 +50:44:30.1 -- does not seem to be a hot pixel (will add it to exclusion list)
00:20:46.35 +50:11:43.8 -- does not seem to be a hot pixel (will add it to exclusion list)
00:22:29.68 +50:18:56.0 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:10.55 +55:47:26.4 -- does not seem to be a hot pixel (will add it to exclusion list)
00:23:11.74 +55:47:35.3 -- does not seem to be a hot pixel (will add it to exclusion list)
00:27:54.16 +52:58:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:28:36.21 +57:27:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:09.11 +56:37:33.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:17.10 +55:18:52.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:19.98 +54:59:47.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:30.64 +56:07:01.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:41.77 +57:15:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:29:51.09 +56:53:56.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:03.60 +54:40:05.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:04.32 +55:55:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:06.40 +53:32:17.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:23.05 +54:28:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:29.03 +55:42:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:35.20 +53:35:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:43.51 +51:31:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:46.10 +56:37:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:30:47.25 +56:59:47.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:09.91 +50:06:30.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:13.06 +51:41:37.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:18.09 +55:42:25.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:20.85 +50:23:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:21.75 +54:44:10.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:23.21 +54:32:01.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:33.68 +56:51:42.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:39.19 +51:36:24.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:40.28 +57:27:22.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:44.84 +51:29:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:51.43 +51:36:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:53.16 +51:39:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:53.48 +56:22:32.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:31:59.91 +55:07:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:01.34 +57:16:57.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:04.03 +55:15:39.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:09.20 +53:57:19.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:13.49 +55:32:49.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:21.78 +54:31:58.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:28.28 +53:27:00.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:32:59.53 +56:40:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:32.02 +56:43:57.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:33.56 +50:54:49.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:36.56 +53:30:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:33:53.40 +54:37:16.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:16.39 +54:04:44.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:16.76 +54:25:03.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:21.05 +54:04:08.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:34:59.80 +50:35:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:04.15 +50:23:35.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:17.66 +55:37:21.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:18.02 +54:24:57.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:21.51 +56:13:47.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:35:59.94 +56:49:21.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:30.85 +57:01:15.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:31.48 +54:23:09.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:32.87 +53:13:26.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:56.22 +52:44:46.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:57.43 +55:34:22.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:59.39 +56:58:25.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:36:59.90 +53:05:01.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:54.53 +52:05:24.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:37:58.17 +52:39:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:10.32 +52:43:48.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:16.00 +56:01:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:25.92 +55:22:20.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:55.92 +51:35:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:38:58.59 +51:32:10.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:01.86 +52:18:14.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:32.32 +52:05:01.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:39:52.36 +52:19:51.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:11.86 +51:49:34.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:24.51 +54:53:56.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:41.80 +51:33:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:40:54.60 +53:47:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:05.57 +52:46:43.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:22.00 +55:49:29.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:29.16 +52:56:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:49.20 +52:55:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:49.94 +53:59:51.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:41:55.17 +52:45:28.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:02.11 +57:24:41.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:06.30 +55:02:24.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:10.97 +56:45:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:24.06 +55:49:09.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:24.87 +53:39:49.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:27.86 +53:37:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:42:55.34 +53:06:04.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:06.18 +52:46:20.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:07.09 +53:23:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:07.15 +52:00:53.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:10.12 +52:00:37.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:27.65 +51:45:09.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:43:37.78 +52:09:44.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:02.93 +52:45:35.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:44:10.52 +53:03:33.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:43.93 +51:45:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:46:45.93 +52:24:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:36.08 +52:37:54.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:47:57.58 +54:15:32.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:50:58.60 +50:27:24.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:10.27 +51:26:07.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:16.81 +52:09:16.1 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:33.93 +51:33:35.4 -- does not seem to be a hot pixel (will add it to exclusion list)
23:51:59.45 +56:02:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:16.62 +51:29:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:52:20.14 +50:08:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:25.83 +51:47:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:55:40.48 +52:35:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:10.80 +50:38:48.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:56:55.59 +56:39:55.6 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:06.91 +52:12:21.2 -- does not seem to be a hot pixel (will add it to exclusion list)
23:57:27.85 +52:04:36.7 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:25.86 +51:26:15.9 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:27.05 +51:26:14.3 -- does not seem to be a hot pixel (will add it to exclusion list)
23:58:59.85 +54:51:05.1 -- 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:11.35 +53:25:56.9 -- not a known variable star
00:00:59.75 +53:46:33.9 -- not a known variable star
00:01:08.45 +56:27:05.4 -- not a known variable star
00:01:19.68 +51:15:18.6 -- not a known variable star
00:01:49.28 +50:18:52.1 -- not a known variable star
00:02:02.38 +53:59:18.7 -- a known variable star
00:02:33.07 +54:00:25.4 -- not a known variable star
00:02:38.42 +53:39:39.6 -- not a known variable star
00:02:59.15 +51:30:26.5 -- not a known variable star
00:03:57.95 +54:07:59.6 -- not a known variable star
00:04:14.31 +50:01:22.7 -- not a known variable star
00:04:16.40 +50:02:31.6 -- not a known variable star
00:04:41.20 +55:32:15.1 -- a known variable star
00:05:01.55 +51:13:22.9 -- not a known variable star
00:06:22.19 +52:40:37.3 -- not a known variable star
00:06:32.77 +52:20:36.8 -- not a known variable star
00:06:57.77 +51:44:16.0 -- not a known variable star
00:07:39.42 +53:34:06.0 -- not a known variable star
00:07:47.70 +50:06:41.9 -- not a known variable star
00:08:00.55 +52:54:45.0 -- not a known variable star
00:08:06.73 +54:49:22.0 -- a known variable star
00:08:07.20 +54:56:34.4 -- not a known variable star
00:08:30.90 +51:27:29.8 -- not a known variable star
00:08:49.88 +50:55:59.7 -- not a known variable star
00:10:00.85 +50:50:02.0 -- not a known variable star
00:12:16.02 +57:18:54.5 -- a known variable star
00:13:10.02 +50:37:08.4 -- not a known variable star
00:13:25.75 +52:37:42.8 -- not a known variable star
00:14:54.68 +53:15:41.5 -- not a known variable star
00:14:55.44 +53:15:47.3 -- not a known variable star
00:17:35.62 +51:28:57.1 -- not a known variable star
00:18:12.84 +54:09:31.4 -- not a known variable star
00:18:30.00 +53:39:27.2 -- not a known variable star
00:18:52.21 +57:49:38.8 -- a known variable star
00:19:42.93 +50:48:25.6 -- not a known variable star
00:19:48.27 +51:04:46.8 -- not a known variable star
00:20:14.58 +50:44:30.1 -- not a known variable star
00:20:46.35 +50:11:43.8 -- not a known variable star
00:22:29.68 +50:18:56.0 -- not a known variable star
00:23:10.55 +55:47:26.4 -- not a known variable star
00:23:11.74 +55:47:35.3 -- a known variable star
00:27:54.16 +52:58:19.3 -- not a known variable star
23:28:36.21 +57:27:57.2 -- not a known variable star
23:29:09.11 +56:37:33.8 -- not a known variable star
23:29:17.10 +55:18:52.3 -- not a known variable star
23:29:19.98 +54:59:47.1 -- not a known variable star
23:29:30.64 +56:07:01.5 -- not a known variable star
23:29:41.77 +57:15:16.9 -- not a known variable star
23:29:51.09 +56:53:56.4 -- not a known variable star
23:30:03.60 +54:40:05.4 -- not a known variable star
23:30:04.32 +55:55:29.3 -- not a known variable star
23:30:06.40 +53:32:17.7 -- a known variable star
23:30:23.05 +54:28:32.9 -- not a known variable star
23:30:29.03 +55:42:38.3 -- not a known variable star
23:30:35.20 +53:35:49.8 -- not a known variable star
23:30:43.51 +51:31:34.5 -- not a known variable star
23:30:46.10 +56:37:26.0 -- a known variable star
23:30:47.25 +56:59:47.3 -- not a known variable star
23:31:09.91 +50:06:30.9 -- not a known variable star
23:31:13.06 +51:41:37.4 -- not a known variable star
23:31:18.09 +55:42:25.5 -- not a known variable star
23:31:20.85 +50:23:20.5 -- not a known variable star
23:31:21.75 +54:44:10.3 -- not a known variable star
23:31:23.21 +54:32:01.3 -- not a known variable star
23:31:33.68 +56:51:42.4 -- a known variable star
23:31:39.19 +51:36:24.3 -- not a known variable star
23:31:40.28 +57:27:22.9 -- not a known variable star
23:31:44.84 +51:29:36.6 -- not a known variable star
23:31:51.43 +51:36:18.3 -- not a known variable star
23:31:53.16 +51:39:04.1 -- not a known variable star
23:31:53.48 +56:22:32.9 -- not a known variable star
23:31:59.91 +55:07:36.7 -- not a known variable star
23:32:01.34 +57:16:57.3 -- not a known variable star
23:32:04.03 +55:15:39.7 -- not a known variable star
23:32:09.20 +53:57:19.8 -- not a known variable star
23:32:13.49 +55:32:49.6 -- not a known variable star
23:32:21.78 +54:31:58.0 -- not a known variable star
23:32:28.28 +53:27:00.9 -- not a known variable star
23:32:59.53 +56:40:19.7 -- a known variable star
23:33:32.02 +56:43:57.2 -- not a known variable star
23:33:33.56 +50:54:49.4 -- not a known variable star
23:33:36.56 +53:30:57.9 -- not a known variable star
23:33:53.40 +54:37:16.9 -- not a known variable star
23:34:16.39 +54:04:44.7 -- not a known variable star
23:34:16.76 +54:25:03.6 -- not a known variable star
23:34:21.05 +54:04:08.8 -- not a known variable star
23:34:59.80 +50:35:49.8 -- not a known variable star
23:35:04.15 +50:23:35.1 -- not a known variable star
23:35:17.66 +55:37:21.9 -- not a known variable star
23:35:18.02 +54:24:57.3 -- not a known variable star
23:35:21.51 +56:13:47.8 -- not a known variable star
23:35:59.94 +56:49:21.3 -- not a known variable star
23:36:30.85 +57:01:15.2 -- not a known variable star
23:36:31.48 +54:23:09.4 -- not a known variable star
23:36:32.87 +53:13:26.0 -- not a known variable star
23:36:56.22 +52:44:46.2 -- not a known variable star
23:36:57.43 +55:34:22.6 -- not a known variable star
23:36:59.39 +56:58:25.7 -- not a known variable star
23:36:59.90 +53:05:01.7 -- not a known variable star
23:37:54.53 +52:05:24.9 -- a known variable star
23:37:58.17 +52:39:44.2 -- not a known variable star
23:38:10.32 +52:43:48.9 -- not a known variable star
23:38:16.00 +56:01:54.0 -- not a known variable star
23:38:25.92 +55:22:20.3 -- not a known variable star
23:38:55.92 +51:35:18.2 -- not a known variable star
23:38:58.59 +51:32:10.6 -- not a known variable star
23:39:01.86 +52:18:14.9 -- not a known variable star
23:39:32.32 +52:05:01.1 -- not a known variable star
23:39:52.36 +52:19:51.6 -- not a known variable star
23:40:11.86 +51:49:34.2 -- not a known variable star
23:40:24.51 +54:53:56.5 -- not a known variable star
23:40:41.80 +51:33:51.3 -- not a known variable star
23:40:54.60 +53:47:05.5 -- not a known variable star
23:41:05.57 +52:46:43.3 -- not a known variable star
23:41:22.00 +55:49:29.6 -- not a known variable star
23:41:29.16 +52:56:27.7 -- a known variable star
23:41:49.20 +52:55:47.4 -- not a known variable star
23:41:49.94 +53:59:51.3 -- not a known variable star
23:41:55.17 +52:45:28.4 -- not a known variable star
23:42:02.11 +57:24:41.8 -- not a known variable star
23:42:06.30 +55:02:24.9 -- not a known variable star
23:42:10.97 +56:45:18.7 -- not a known variable star
23:42:24.06 +55:49:09.1 -- not a known variable star
23:42:24.87 +53:39:49.0 -- not a known variable star
23:42:27.86 +53:37:18.0 -- not a known variable star
23:42:55.34 +53:06:04.8 -- a known variable star
23:43:06.18 +52:46:20.8 -- not a known variable star
23:43:07.09 +53:23:28.1 -- not a known variable star
23:43:07.15 +52:00:53.7 -- not a known variable star
23:43:10.12 +52:00:37.3 -- not a known variable star
23:43:27.65 +51:45:09.0 -- a known variable star
23:43:37.78 +52:09:44.1 -- not a known variable star
23:44:02.93 +52:45:35.2 -- not a known variable star
23:44:10.52 +53:03:33.5 -- not a known variable star
23:46:43.93 +51:45:27.9 -- not a known variable star
23:46:45.93 +52:24:14.0 -- not a known variable star
23:47:36.08 +52:37:54.3 -- not a known variable star
23:47:57.58 +54:15:32.2 -- not a known variable star
23:50:58.60 +50:27:24.9 -- not a known variable star
23:51:10.27 +51:26:07.1 -- not a known variable star
23:51:16.81 +52:09:16.1 -- not a known variable star
23:51:33.93 +51:33:35.4 -- not a known variable star
23:51:59.45 +56:02:30.5 -- a known variable star
23:52:16.62 +51:29:29.7 -- not a known variable star
23:52:20.14 +50:08:57.9 -- not a known variable star
23:55:25.83 +51:47:36.6 -- not a known variable star
23:55:40.48 +52:35:18.8 -- not a known variable star
23:56:10.80 +50:38:48.7 -- not a known variable star
23:56:55.59 +56:39:55.6 -- not a known variable star
23:57:06.91 +52:12:21.2 -- not a known variable star
23:57:27.85 +52:04:36.7 -- not a known variable star
23:58:25.86 +51:26:15.9 -- not a known variable star
23:58:27.05 +51:26:14.3 -- not a known variable star
23:58:59.85 +54:51:05.1 -- a known variable star
Found 138 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
154 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 154 (excluding asteroids and hot pixels, 138 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)2461215.83097344 -observatory V36
07:46:12.24 +20:24:27.4 Mercury (1.2mag)
09:00:59.48 +18:59:25.2 Venus (-4.0mag)
03:36:49.32 +18:58:56.5 Mars (1.3mag)
08:02:18.55 +20:54:24.9 Jupiter (-1.8mag)
00:53:19.69 +03:09:19.7 Saturn (0.8mag)
04:03:55.23 +20:35:58.1 Uranus (5.8mag)
00:16:50.42 +00:20:25.0 Neptune (7.8mag)
20:32:16.71 -23:11:02.2 Pluto (14.5mag)
13:43:05.70 -16:07:47.1 Moon (-11.1mag)
-rw-r--r-- 1 apache apache 362 Jun 24 03:57 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461215.83097344:
08:02:24.09 +20:54:08.3 Io (6.2mag)
08:02:18.17 +20:54:25.3 Europa (6.3mag)
08:02:17.93 +20:54:32.2 Ganymede (5.6mag)
08:02:42.43 +20:53:03.0 Callisto (6.9mag)
08:01:39.46 +20:33:15.8 Himalia (15.6mag)
08:02:22.70 +20:54:11.1 Thebe (16.6mag)
08:01:13.67 +20:42:18.1 Elara (17.6mag)
08:05:15.05 +20:57:17.1 Pasiphae (17.8mag)
08:08:07.97 +20:57:32.8 Carme (18.9mag)
00:53:10.03 +03:09:13.9 Titan (8.6mag)
00:53:24.80 +03:09:13.3 Rhea (9.9mag)
00:53:23.99 +03:11:20.3 Iapetus (11.3mag)
00:53:08.24 +03:09:38.8 Hyperion (14.6mag)
00:53:41.56 +03:08:54.9 Phoebe (16.6mag)
-rw-r--r-- 1 apache apache 568 Jun 24 03:57 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461215.83097344:
17:30:37.80 -35:17:42.9 JWST
15:48:31.09 +51:39:12.1 Chandra
22:31:09.10 +57:21:06.7 XMM-Newton
-rw-r--r-- 1 apache apache 96 Jun 24 03:57 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461215.83097344 -observatory V36
18:31:02.55 -33:41:40.9 13.7mag P/2010 H2 (Vales)
06:09:33.76 -67:59:53.5 17.3mag C/2014 UN271 (Bernardinelli-Bernstein)
05:55:01.93 +32:11:34.4 17.6mag C/2017 K2 (PANSTARRS)
17:08:25.65 +15:55:33.5 17.9mag C/2021 G2 (ATLAS)
23:51:19.23 -27:54:46.8 15.6mag P/2021 N1 (ZTF)
23:07:34.24 +32:05:45.2 17.2mag C/2022 E2 (ATLAS)
05:53:37.43 +27:00:33.2 16.6mag C/2022 N2 (PANSTARRS)
09:42:04.09 +30:28:05.2 16.7mag C/2022 QE78 (ATLAS)
08:59:44.56 +04:34:53.4 17.8mag C/2022 R6 (PANSTARRS)
18:17:31.17 +21:40:38.1 17.8mag C/2023 A3 (Tsuchinshan-ATLAS)
15:14:25.79 -11:06:49.6 17.6mag P/2023 B1 (PANSTARRS)
22:05:20.51 +67:20:29.6 17.8mag C/2023 H5 (Lemmon)
17:06:27.53 -08:21:52.7 13.7mag C/2023 R1 (PANSTARRS)
13:19:13.76 +79:10:15.9 18.0mag C/2023 X2 (Lemmon)
07:34:16.43 +64:55:54.9 17.8mag C/2024 A1 (ATLAS)
07:10:56.91 +29:04:33.8 14.2mag C/2024 E1 (Wierzchos)
15:25:33.74 +14:40:31.6 17.5mag C/2024 G6 (ATLAS)
19:59:36.62 +35:40:58.7 13.9mag C/2024 J3 (ATLAS)
22:01:17.23 +43:20:14.0 18.0mag C/2024 R4 (PANSTARRS)
04:34:07.03 -14:42:07.3 15.9mag C/2024 T5 (ATLAS)
06:20:42.32 +31:44:29.8 17.9mag C/2025 J1 (Borisov)
11:32:17.49 +51:45:20.9 18.0mag C/2025 L1 (ATLAS)
07:01:38.30 -11:42:21.4 15.4mag C/2025 R3 (PANSTARRS)
09:38:50.32 +23:00:13.5 17.8mag C/2025 V2 (Rankin)
12:40:44.56 +04:28:09.3 17.1mag C/2025 Y1 (ATLAS)
17:38:09.72 +77:55:51.7 17.6mag C/2026 A2 (Bok)
02:26:12.95 +44:26:26.3 16.4mag C/2026 B2 (Sun-Gao)
11:16:44.24 +01:06:47.8 16.7mag A/2026 E1
20:52:20.18 -10:40:35.6 7.9mag 10P/Tempel
11:06:49.25 -01:18:58.9 16.1mag 29P/Schwassmann-Wachmann
03:36:26.60 +27:42:22.1 17.8mag 47P/Ashbrook-Jackson
09:34:20.13 +19:00:16.3 17.0mag 63P/Wild
00:39:20.98 -05:31:11.8 15.6mag 65P/Gunn
07:35:51.76 +34:25:18.9 17.4mag 76P/West-Kohoutek-Ikemura
03:48:24.22 +19:00:09.6 13.8mag 78P/Gehrels
01:53:49.36 +08:03:14.7 15.9mag 88P/Howell
05:46:13.36 +30:57:16.1 15.4mag 93P/Lovas
03:30:27.83 +29:50:45.9 17.2mag 114P/Wiseman-Skiff
07:29:31.28 +32:09:48.8 15.4mag 123P/West-Hartley
10:18:46.64 +07:48:14.6 16.7mag 124P/Mrkos
04:25:38.31 +20:11:06.9 16.3mag 128P/Shoemaker-Holt
05:05:25.20 +19:36:45.2 17.8mag 131P/Mueller
07:02:07.36 +16:15:51.2 16.7mag 141P/Machholz
07:06:08.73 +17:45:59.3 16.6mag 141P-A/Machholz
06:11:01.92 +17:25:26.3 13.5mag 141P-D/Machholz
03:08:22.18 -22:40:43.9 16.2mag 161P/Hartley-IRAS
04:36:11.88 +29:38:04.2 15.1mag 162P/SidingSpring
19:29:32.08 +07:14:48.6 15.9mag 169P/NEAT
01:00:59.82 +05:22:11.4 17.7mag 220P/McNaught
16:41:28.46 -08:04:27.4 16.7mag 235P/LINEAR
08:10:42.31 +34:35:31.7 17.7mag 240P/NEAT
20:43:17.31 -45:29:46.7 18.0mag 259P/Garradd
01:15:17.08 +04:39:25.0 16.0mag 260P/McNaught
04:49:36.40 +35:04:14.8 17.5mag 295P/LINEAR
15:09:19.05 +07:17:33.2 17.5mag 391P/Kowalski
08:20:31.04 +20:16:06.8 17.9mag 450P/LONEOS
07:26:12.08 +40:29:58.8 17.9mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.8K Jun 24 03:57 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 24 03:57 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 24 03:57 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
13:52:20.180 +26:36:28.29 AT 2026phs 2026-06-03.76 21.08
19:02:22.130 +47:04:24.55 AT 2026phr 2026-04-16.90 20.76
15:04:03.130 +51:40:36.19 AT 2026phq 2026-06-08.80 20.69
14:59:06.740 +49:19:47.55 AT 2026php 2026-06-03.82 21.24
15:25:14.430 +52:47:19.27 AT 2026pho 2026-06-03.82 20.69
15:32:10.430 +55:31:52.79 AT 2026phn 2026-06-03.82 20.55
15:05:31.070 +54:01:58.04 AT 2026phm 2026-06-03.82 20.97
15:26:20.470 +34:15:03.49 AT 2026phl 2026-06-03.81 21.22
15:30:53.386 +36:56:04.14 AT 2026phk 2026-06-03.81 20.62
15:53:00.067 +39:11:14.03 AT 2026phj 2026-06-03.81 20.35
15:16:47.570 +42:26:03.51 AT 2026phi 2026-06-03.80 21.4
15:30:43.080 +44:43:29.89 AT 2026phh 2026-06-03.80 20.99
15:34:17.400 +45:38:16.24 AT 2026phg 2026-06-03.80 20.99
15:36:56.850 +49:52:01.56 AT 2026phf 2026-06-03.80 21.12
17:59:56.980 +54:59:32.40 AT 2026phe 2026-05-08.79 21.25
15:00:58.510 +55:15:48.71 AT 2026phd 2026-05-03.81 21.36
13:50:35.500 +00:18:35.99 AT 2026phc 2026-06-03.69 21.88
13:39:32.410 +05:32:10.98 AT 2026phb 2026-06-02.76 20.21
14:35:25.830 -01:38:25.40 AT 2026pha 2026-06-11.74 21.15
14:31:21.350 -01:45:35.72 AT 2026pgz 2026-06-11.74 22.45
-rw-r--r-- 1 apache apache 30K Jun 24 03:57 tns_transients_list.txt
