This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv
The list of candidates will appear below. Please manually reload the page every few minutes untill the 'Processing complete' message appears.
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,11.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 11.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0418017+711356,2461140.7330,12.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0418017+711356 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.91CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 1107824833330759168,2461140.7330,14.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 1107824833330759168 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 11 19.38 +71 20 07.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,2461140.7330,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.85CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 494020057648447232,2461140.7330,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 494020057648447232 20260410.2330 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 488216324179547008,2461140.7330,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 488216324179547008 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.47,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.25,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.25CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 493935979369184384,2461140.7330,12.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 493935979369184384 20260410.2330 12.98CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0418017+711356,2461140.7330,13.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0418017+711356 20260410.2330 13.14CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,12.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 12.95CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J086.8172+63.8616,2461140.7330,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J086.8172+63.8616 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 550080208475367936,2461140.7330,12.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 550080208475367936 20260410.2330 12.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,11.84,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 11.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 31 10.38 +71 05 34.5 11.5 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS 504503,2461140.7330,11.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 504503 20260410.2330 11.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,11.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501158808690643712,2461140.7330,12.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501158808690643712 20260410.2330 12.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,12.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 12.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,12.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 12.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 493787098621550976,2461140.7330,12.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 493787098621550976 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 488406638472452992,2461140.7330,12.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 488406638472452992 20260410.2330 12.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 12.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.04,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.04CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.01CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.11CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.32CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 490831370847792128,2461140.7330,13.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 490831370847792128 20260410.2330 13.20CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.52CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 543369201816548608,2461140.7330,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 543369201816548608 20260410.2330 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 35 33.81 +72 09 34.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
Gaia DR3 543554194647739648,2461140.7330,13.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 543554194647739648 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.56,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.56CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.65CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549776773329331584,2461140.7330,13.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549776773329331584 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ASASSN-V J040218.37+701948.3,2461140.7330,13.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J040218.37+701948.3 20260410.2330 13.61CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.68CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
CzeV3511,2461140.7330,13.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
CzeV3511 20260410.2330 13.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 490079549712449664,2461140.7330,13.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 490079549712449664 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.86CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500429214005075328,2461140.7330,13.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500429214005075328 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 495750899407105536,2461140.7330,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 495750899407105536 20260410.2330 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500260374549067648,2461140.7330,13.80,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500260374549067648 20260410.2330 13.80CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 496662806863733504,2461140.7330,13.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 496662806863733504 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.87CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 13.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 495284156721043456,2461140.7330,13.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 495284156721043456 20260410.2330 13.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500815211307320960,2461140.7330,13.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500815211307320960 20260410.2330 13.78CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 494493951459077632,2461140.7330,13.81,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 494493951459077632 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 543588824966840960,2461140.7330,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 543588824966840960 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 490460702288529408,2461140.7330,13.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 490460702288529408 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.00,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.00CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500381767504460928,2461140.7330,14.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500381767504460928 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 29 05.95 +72 34 27.7 14.0 U Cas 9 0
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501513920883078528,2461140.7330,14.09,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501513920883078528 20260410.2330 14.09CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,13.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.08,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501224680607043840,2461140.7330,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501224680607043840 20260410.2330 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501261445525925120,2461140.7330,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501261445525925120 20260410.2330 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.17,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
ATO J068.9234+70.7526,2461140.7330,14.14,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J068.9234+70.7526 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549963797683423488,2461140.7330,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549963797683423488 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 495108853335613824,2461140.7330,14.12,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 495108853335613824 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501681007994316928,2461140.7330,14.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501681007994316928 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.33,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.06,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.22,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.22CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 490846282975486592,2461140.7330,14.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 490846282975486592 20260410.2330 14.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 34 20.81 +74 24 39.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
Gaia DR3 544824611614302720,2461140.7330,14.27,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 544824611614302720 20260410.2330 14.27CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.26CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549939402265939072,2461140.7330,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549939402265939072 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549694653553706880,2461140.7330,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549694653553706880 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 550713527173998976,2461140.7330,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 550713527173998976 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.28,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.28CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.30CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500459008196048384,2461140.7330,14.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500459008196048384 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501372427481419392,2461140.7330,14.41,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501372427481419392 20260410.2330 14.41CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 500152003934148864,2461140.7330,14.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 500152003934148864 20260410.2330 14.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.29,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.37,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.44,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501444956590704640,2461140.7330,14.42,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501444956590704640 20260410.2330 14.42CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 542860231012687360,2461140.7330,14.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 542860231012687360 20260410.2330 14.36CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 496761006995740800,2461140.7330,14.52,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 496761006995740800 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549722557959851648,2461140.7330,14.49,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549722557959851648 20260410.2330 14.49CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 544628211349836288,2461140.7330,14.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 544628211349836288 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 25 11.52 +69 09 38.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,2461140.7330,14.53,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.51CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549489182318300672,2461140.7330,14.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549489182318300672 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.68,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.60,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.58,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.58CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 549489182318300672,2461140.7330,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 549489182318300672 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 496893223268577920,2461140.7330,14.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 496893223268577920 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 543429228280647168,2461140.7330,14.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 543429228280647168 20260410.2330 14.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 499327267132848384,2461140.7330,14.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 499327267132848384 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.71,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 495088374931962624,2461140.7330,14.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 495088374931962624 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.90,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.90CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 490568450130320768,2461140.7330,14.62,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 490568450130320768 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.73CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 35 01.80 +71 45 16.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,2461140.7330,14.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.82CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.78,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.96CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.85,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
Gaia DR3 501861126039685760,2461140.7330,14.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 501861126039685760 20260410.2330 14.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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.87,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,14.93,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 14.93CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461140.7330,11.19,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260410.2330 11.19CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
TCP 2026 04 10.2330* 03 30 07.19 +68 46 01.8 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
NSVS J0330092+684552,2461140.7330,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0330092+684552 20260410.2330 12.89CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting a new transient to the TOCP.
Don't forget to set the constellation name and the number of days since the last non-detection!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
NSVS J0418017+711356,2461140.7330,12.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-1 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS J0418017+711356 20260410.2330 12.34CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
First image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Last image: 2461140.73338980 10.04.2026 05:35:54.879 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 4
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.51
Magnitude-Size filter: Disabled
For each source choose aperture with the smallest scatter: YES
Photometric errors rescaling: NO
Number of identified bad images: 0
Number of SysRem iterations: 0
User-specified moving object: none
Computation time: 7 seconds
Number of parallel threads: 24
SExtractor parameter file: default.sex
Some important SExtractor parameters:
DETECT_MINAREA 10.0 # minimum number of pixels above threshold
DETECT_THRESH 10.0 # or , in mag.arcsec-2
ANALYSIS_THRESH 10.0 # or , in mag.arcsec-2
SATUR_LEVEL 55000.0 # level (in ADUs) at which arises saturation
GAIN 0.37 # detector gain in e-/ADU
Total objects detected (at least 2 times): 16719
Objects passed selection criteria: 16693
Measurements per detected object (mean, median, min, max): 3.3 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.3 4.0 2 4
Average stars detected per image: 14526
Average stars matched: 14137 (97.322 %)
Memory usage VmPeak: 121336 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 8 18:56:33 CDT 2026
VaST build number 1.0rc89-5-g00c52b5f
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Fri Apr 10 00:38:02 CDT 2026
Host name: tau
############################################################
## VaST run with SExtractor config file default.sex.telephoto_lens_vSTL ##
Images processed 4
Images used for photometry 4
Ref. image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
First image: 2461049.69585608 09.01.2026 04:41:51.965 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Last image: 2461140.73338980 10.04.2026 05:35:54.879 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 211
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.20
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: 57 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): 115864
Objects passed selection criteria: 115582
Measurements per detected object (mean, median, min, max): 3.5 4.0 2 4
Measurements per selected object (mean, median, min, max): 3.5 4.0 2 4
Average stars detected per image: 105546
Average stars matched: 101854 (96.502 %)
Memory usage VmPeak: 1942316 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Wed Apr 8 18:56:33 CDT 2026
VaST build number 1.0rc89-5-g00c52b5f
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-08)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Fri Apr 10 00:49:31 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ1b1x1/TTUQ1_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat to cache
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.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/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.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: 2461140.73268060
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_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits exists and is non-empty
Saving wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits to local_wcs_cache/
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits exists and is non-empty
Saving wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits to local_wcs_cache/
'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits'
wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits exists and is non-empty
Saving wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits to local_wcs_cache/
'wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits' -> 'local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits'
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:47:59.534 +70:00:06.49
Angular distance between the image centers 0.0649 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:47:58.860 +69:59:38.36
Angular distance between the image centers 0.0617 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 04:47:59.534 +70:00:06.49
Second-epoch second image center 04:47:58.860 +69:59:38.36
Angular distance between the image centers 0.00787 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/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits &> /tmp/tmp.DlCMkHviQn
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits &> /tmp/tmp.EC5Jkm5SKO
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits &> /tmp/tmp.KFKDbFAjWE
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits &> /tmp/tmp.tAZDw06dGh
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Calibrating the magnitude scale
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.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_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
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_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
The reference image (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits) and catalog (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat) found
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat' -> 'wcsmag.cat'
Read 17535 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 44.4953 to 100.0749 deg, Dec +62.8164 to +75.4615 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 44.4953 to 100.0749 deg, Dec 62.8164 to 75.4615 deg
Loaded 14408 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): 7701 out of 8346 total matches.
Matched with Tycho-2 8346 out of 17535 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.930229
a=0.000000 b=1.000000 c=22.930229
From vast_summary.log: estimated ref. image limiting mag.: -7.51
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.42
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.42
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 3 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.0 pix Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
2.0 pix Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
2.1 pix fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
2.1 pix fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Limiting magnitude estimates:
15.4 mag. Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
15.4 mag. Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
14.9 mag. fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
14.9 mag. fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
All-image limiting magnitude estimate: 14.9 (SNR ) 11.9 (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.DlCMkHviQn (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1440, passed=17535
Got 17535 stars (including 16074 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
util/solve_plate_with_UCAC5 got 17535 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (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.010460 (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
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 950 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.37"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 970 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Accuracy estimation diagnostic: 969 matched stars entering correct_measured_positions(), 17045 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Excluding outliers - 969 stars left (next iteration limit 1065)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.EC5Jkm5SKO (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=1424, passed=17523
Got 17523 stars (including 16079 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
util/solve_plate_with_UCAC5 got 17523 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (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.010460 (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
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 949 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17070 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 17071 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.32"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.KFKDbFAjWE (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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=811, passed=11727
Got 11727 stars (including 10905 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat
util/solve_plate_with_UCAC5 got 11727 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.4'
Seting catalog search parameters based on the expected field of view 932.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012950 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010360 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 267 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 217 matched stars entering correct_measured_positions(), 173 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.81"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 209 matched stars entering correct_measured_positions(), 2521 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.88"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 315 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 280 matched stars entering correct_measured_positions(), 2551 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.71"
Accuracy estimation diagnostic: 280 matched stars entering correct_measured_positions(), 3374 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.43"
Excluding outliers - 280 stars left (next iteration limit 229)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.tAZDw06dGh (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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat
SExtractor catalog parsing summary: zero_flux=5, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=806, passed=11662
Got 11662 stars (including 10837 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat
util/solve_plate_with_UCAC5 got 11662 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.4'
Seting catalog search parameters based on the expected field of view 932.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012950 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010360 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 271 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 219 matched stars entering correct_measured_positions(), 173 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.97"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 211 matched stars entering correct_measured_positions(), 2463 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.98"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 317 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 284 matched stars entering correct_measured_positions(), 2494 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.78"
Accuracy estimation diagnostic: 283 matched stars entering correct_measured_positions(), 3357 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.51"
Excluding outliers - 283 stars left (next iteration limit 232)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits'
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits'
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out21272.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out21472.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 16s
Pre-generating preview images in parallel...
Done pre-generating preview images.
Pre-generating finding charts in parallel...
Done pre-generating finding charts.
make_report_in_HTML.sh Pre-generation: 2s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21272_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 21272_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21472_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 21472_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 21502_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 21502_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (16.2") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 18s
Prepared the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
05:18:59.88 +64:31:26.9
04:17:58.82 +71:13:47.4
wait
*------ default.sex.telephoto_lens_vSTL ------*
'default.sex.telephoto_lens_vSTL' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_vSTL
./vast --norotation --noflagimage --starmatchraius 3.5 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat to cache
SExtractor catalog cache: saved Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Creating symlink local_wcs_cache/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Creating symlink local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Creating symlink local_wcs_cache/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Creating symlink local_wcs_cache/exclusion_list.txt
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
Plate-solving the images
wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits exists and is non-empty
wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits exists and is non-empty
wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits exists and is non-empty
wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits exists and is non-empty
The image scale is 5.90"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.9"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:47:59.534 +70:00:06.49
Angular distance between the image centers 0.0649 deg.
Soft limit: 0.50 deg. Hard limit: 1.00 deg.
###################################
###################################
# Check the image center offset between the reference and the second second-epoch image (pointing accuracy)
Reference image center 04:47:16.792 +69:58:46.61
Second-epoch image center 04:47:58.860 +69:59:38.36
Angular distance between the image centers 0.0617 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 04:47:59.534 +70:00:06.49
Second-epoch second image center 04:47:58.860 +69:59:38.36
Angular distance between the image centers 0.00787 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/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits &> /tmp/tmp.CB1pSt0wtD
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits &> /tmp/tmp.Ax5AENLCjt
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits &> /tmp/tmp.sUBuVVkKla
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits &> /tmp/tmp.ECN0s97WU9
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Calibrating the magnitude scale
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.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_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
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_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
Found non-empty wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits and wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
The reference image (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits) and catalog (wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat) found
'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat' -> 'wcsmag.cat'
Read 121322 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 44.3972 to 100.3253 deg, Dec +62.8165 to +75.4640 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 44.3972 to 100.3253 deg, Dec 62.8165 to 75.4640 deg
Loaded 14499 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): 6542 out of 8413 total matches.
Matched with Tycho-2 8413 out of 121322 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 22.798908
a=0.000000 b=1.000000 c=22.798908
From vast_summary.log: estimated ref. image limiting mag.: -7.20
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.60
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.60
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 189 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
1.9 pix Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
1.9 pix Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
1.9 pix fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
1.9 pix fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Limiting magnitude estimates:
15.6 mag. Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
15.6 mag. Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
15.1 mag. fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
15.1 mag. fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
All-image limiting magnitude estimate: 15.1 (SNR ) 14.5 (80% of stars) with default.sex.telephoto_lens_vSTL
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.CB1pSt0wtD (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=20, blended=10875, passed=121302
Got 121302 stars (including 110227 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat
util/solve_plate_with_UCAC5 got 121302 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (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.010460 (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
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 956 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118877 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118876 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 118876 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.34"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.Ax5AENLCjt (6) ############
Parsing command line arguments...
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits 573.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits' -> 'wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS_IMAGE_NAME=wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS-calibrated image found: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Checking if the catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits alredy exist and is non-empty...
Catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat corresponding to the image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
WCS catalog name: wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=28, blended=10830, passed=121526
Got 121526 stars (including 110505 good ones) from the SExtractor catalog wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat
util/solve_plate_with_UCAC5 got 121526 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.4'
Seting catalog search parameters based on the expected field of view 941.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013075 (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.010460 (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
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 946 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119031 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 764 to 829 (Dec 62.8 to 75.5)
Done reading UCAC5 zone files...
Matched 971 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119030 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.35"
Accuracy estimation diagnostic: 970 matched stars entering correct_measured_positions(), 119030 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.34"
Excluding outliers - 970 stars left (next iteration limit 1067)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits -region wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.sUBuVVkKla (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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=35, blended=5864, passed=91044
Got 91044 stars (including 85027 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat
util/solve_plate_with_UCAC5 got 91044 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.4'
Seting catalog search parameters based on the expected field of view 932.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012950 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010360 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 276 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 225 matched stars entering correct_measured_positions(), 184 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.83"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 218 matched stars entering correct_measured_positions(), 20650 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.51"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 319 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 292 matched stars entering correct_measured_positions(), 20672 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.49"
Accuracy estimation diagnostic: 290 matched stars entering correct_measured_positions(), 27173 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.41"
Excluding outliers - 290 stars left (next iteration limit 239)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
############ /tmp/tmp.ECN0s97WU9 (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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.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-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS_IMAGE_NAME=wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS-calibrated image found: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Checking if the catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits alredy exist and is non-empty...
Catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat corresponding to the image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
WCS catalog name: wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=26, blended=5867, passed=90847
Got 90847 stars (including 84816 good ones) from the SExtractor catalog wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat
util/solve_plate_with_UCAC5 got 90847 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 932.4'
Seting catalog search parameters based on the expected field of view 932.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012950 (46.6 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010360 (37.3 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 274 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 225 matched stars entering correct_measured_positions(), 183 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.98"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 218 matched stars entering correct_measured_positions(), 20365 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.95"
ITERATION 02 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 766 to 828 (Dec 63.4 to 75.3)
Done reading UCAC5 zone files...
Matched 316 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 290 matched stars entering correct_measured_positions(), 20391 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.90"
Accuracy estimation diagnostic: 289 matched stars entering correct_measured_positions(), 27194 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.37"
Excluding outliers - 289 stars left (next iteration limit 239)
The image catalog is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits -region wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits.cat.astrometric_residuals
Option '-n' not using photometric catalogs, just stick with astrometry
opt '-i': 2 is the maximum number of iterations
Copying WCS-calibrated images back to input directory
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_Cam-06-Q1b1x1_2026-01-08_22-41-51_20.00sec_-14.90C_LIGHT_0169.fits
Saving fully-calibrated image wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_Cam-06-Q1b1x1_2026-01-08_22-42-29_20.00sec_-15.00C_LIGHT_0170.fits
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-34-53_20.00sec_-5.00C_LIGHTs_0100.fits
Saving fully-calibrated image wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
The destination file is already there - not rewriting /data_ssd/NMW-TexasTech/workdir//img_2026-04-10_CI_Cam-06-Q1b1x1_003650_TTUQ1b1x1_24885_ceby9KYv/wcs_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101.fits
Preparing the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_gaiadr2.txt__out142033.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_gaiadr2.txt__out142058.dat to exclusion_list_gaiadr2.txt
Adding exclusion_list_local.txt__out141956.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141973.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141978.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141984.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141986.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141991.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141994.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141998.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out141999.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142000.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142003.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142008.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142010.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142015.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142016.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142018.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142023.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142024.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142029.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142038.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142040.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142041.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142042.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142044.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142046.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142047.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142055.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142057.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142059.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142065.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142066.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142068.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142070.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142072.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142073.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142074.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142283.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142296.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142508.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142559.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142599.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142647.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142742.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142768.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142799.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142822.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142827.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142843.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142885.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142941.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out142972.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143135.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143142.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143178.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143220.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143233.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143239.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143243.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143254.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143298.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143302.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143346.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143347.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143349.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143368.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143394.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143400.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143428.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143443.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143449.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143464.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143479.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143480.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143481.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143557.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143571.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143577.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143579.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143593.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143594.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143625.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143649.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143662.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143671.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143678.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143704.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143727.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143731.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143733.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143738.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143747.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143800.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143813.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143837.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143840.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143846.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143856.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143871.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143875.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143886.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143917.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143922.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143947.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143969.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out143970.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144009.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144037.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144045.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144052.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144080.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144083.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144101.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144111.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144118.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144120.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144125.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144155.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144158.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144165.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144198.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144241.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144243.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144259.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144290.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144291.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144330.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144348.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144354.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144413.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144447.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144463.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144477.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144483.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144486.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144494.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144502.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144522.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144527.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144530.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144560.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144581.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144650.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144654.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144681.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144682.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144729.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144744.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144745.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144781.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144782.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144797.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144827.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144855.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144860.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144869.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144887.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out144920.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out46725.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out78258.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out89441.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 237s
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: 103s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141956_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141956_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141973_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141973_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141978_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141978_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141981_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 141981_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141984_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141984_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141986_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141986_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141989_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 141989_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141991_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141991_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141994_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141994_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141998_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141998_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 141999_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 141999_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142000_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142000_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142003_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142003_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142008_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142008_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142010_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142010_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142015_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142015_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142016_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142016_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142018_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142018_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142022_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142022_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (15.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142023_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142023_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142024_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142024_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142029_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142029_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142033_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142033_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 03:40:47.77 +66:28:45.1 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=14.08, MAG_FAINT_SEARCH_LIMIT=15.06)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142038_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142038_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142040_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142040_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142041_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142042_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142042_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142044_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142044_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142045_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142045_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142046_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142046_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142047_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142047_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142055_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142055_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142057_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142057_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142058_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142058_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 04:34:25.44 +71:29:11.6 in Gaia DR2 blend (GAIA_DR2_CLIENT=#vizquery#, MAG_MEAN=13.37, MAG_FAINT_SEARCH_LIMIT=14.35)
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142059_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142059_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142065_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142065_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142066_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142066_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142068_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142068_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142070_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142070_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142071_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142071_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 03:56:29.89 +73:31:46.1 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142072_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142072_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142073_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142073_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142074_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142074_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142283_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142283_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142296_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142296_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142508_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142508_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142517_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142517_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (10.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142559_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142559_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142599_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142599_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142647_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142647_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142711_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142711_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 04:13:39.92 +72:09:31.9 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142742_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142742_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142768_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142768_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142799_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142799_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142822_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142822_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142827_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142827_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142843_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142843_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142885_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142885_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142941_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142941_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142953_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142953_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 04:13:31.08 +72:06:11.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142964_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 142964_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 03:55:26.03 +74:20:36.7 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 142972_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 142972_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143135_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143135_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143142_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143142_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143158_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143158_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 04:01:16.97 +73:02:37.0 in the exclusion list exclusion_list.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143178_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143178_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143192_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143192_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (23.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143220_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143220_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143233_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143233_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143239_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143239_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143243_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143243_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143254_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143254_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143278_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143278_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 04:05:42.21 +68:39:52.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143298_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143298_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143302_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143302_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143346_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143346_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143347_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143347_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143349_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143349_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143368_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143368_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143394_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143394_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143400_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143400_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143428_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143428_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143443_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143443_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143449_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143449_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143464_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143464_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143479_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143479_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143480_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143480_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143481_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143481_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143515_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143515_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
**** FOUND 03:56:11.71 +71:48:26.5 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143557_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143557_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143571_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143571_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143577_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143577_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143579_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143579_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143593_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143593_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143594_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143594_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143624_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143624_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (13.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143625_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143625_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143649_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143649_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143662_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143662_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143671_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143671_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143672_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143672_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143678_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143678_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143683_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143683_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (17.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143704_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143704_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143727_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143727_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143731_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143731_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143733_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143733_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143738_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143738_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143747_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143747_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143800_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143800_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143813_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143813_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143837_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143837_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143840_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143840_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143846_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143846_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143856_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143856_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143871_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143871_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143875_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143875_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143886_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143886_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143917_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143917_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143922_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143922_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143947_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143947_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143959_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 143959_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143969_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143969_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 143970_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 143970_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144009_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144009_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144037_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144037_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144045_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144045_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144052_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144052_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144080_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144080_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144083_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144083_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144101_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144101_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144111_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144111_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144118_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144118_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144120_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144120_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144125_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144125_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144155_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144155_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144158_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144158_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144165_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144165_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144198_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144198_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144241_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144241_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144243_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144243_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144259_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144259_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144277_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144277_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (10.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144290_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144290_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144291_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144291_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144330_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144330_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144348_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144348_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144354_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144354_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144413_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144413_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144447_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144447_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144463_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144463_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144477_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144477_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144483_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144483_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144486_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144486_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144494_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144494_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144502_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144502_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144522_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144522_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144527_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144527_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144530_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144530_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144539_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144539_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (15.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144560_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144560_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144581_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144581_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144650_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144650_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144654_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144654_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144677_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144677_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144681_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144681_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144682_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144682_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144729_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144729_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144744_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144744_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144745_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144745_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144781_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144781_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144782_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144782_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144785_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144785_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (16.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144797_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144797_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144816_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144816_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (11.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144826_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144826_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (10.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144827_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144827_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144855_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144855_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144860_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144860_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144869_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144869_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144879_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144879_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144887_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144887_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144920_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 144920_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144971_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144971_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (15.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 144975_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 144975_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 78258_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 78258_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 135829_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
The candidate 135829_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101 did not pass the final checks
Rejecting candidate due to large distance (26.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 89441_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 89441_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 46725_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
Preparing report for the candidate 46725_fd_Cam-06-Q1b1x1_2026-04-10_00-35-54_20.00sec_-4.90C_LIGHTs_0101
make_report_in_HTML.sh Phase 2 (HTML assembly): 7s
make_report_in_HTML.sh TOTAL: 347s
Prepared the HTML report for the field Cam-06-Q1b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
05:18:59.88 +64:31:26.9
04:17:58.82 +71:13:47.4
04:39:04.72 +69:38:45.2
04:33:37.91 +68:34:29.0
05:19:55.00 +72:59:35.7
04:58:06.80 +74:35:53.5
04:32:38.67 +73:19:54.2
04:14:04.72 +68:05:08.5
04:50:07.41 +69:35:22.3
04:15:18.36 +71:12:30.5
04:10:48.41 +69:12:03.4
05:00:53.28 +72:21:19.7
06:18:34.44 +70:58:19.0
06:06:19.66 +71:33:14.9
04:32:03.50 +69:06:00.2
03:41:23.14 +73:57:34.0
04:16:59.23 +66:56:34.0
04:02:25.24 +73:49:49.2
03:11:19.38 +71:20:07.2
06:10:38.34 +69:13:50.1
03:48:57.57 +74:40:49.8
03:55:17.27 +68:37:36.4
04:50:42.12 +66:56:50.1
03:57:25.02 +71:08:04.4
03:57:05.49 +69:13:40.5
04:36:07.77 +72:44:58.4
03:42:20.51 +64:48:38.9
04:01:32.93 +72:47:39.3
05:02:57.33 +67:49:32.8
04:20:30.65 +67:31:02.0
04:34:24.79 +65:49:45.6
04:05:43.61 +69:16:58.7
04:18:00.13 +71:13:44.2
04:46:57.39 +65:43:21.2
05:47:13.95 +63:52:18.1
04:35:12.83 +72:39:17.2
04:20:23.07 +74:29:04.2
05:21:42.03 +73:12:40.0
03:31:10.38 +71:05:34.5
04:26:16.31 +74:20:57.9
04:13:18.95 +72:06:40.4
04:59:21.73 +70:28:04.0
05:02:35.63 +66:52:10.2
04:00:26.55 +68:34:44.3
03:41:11.32 +64:55:58.3
05:30:41.56 +64:20:56.8
05:13:09.21 +67:32:21.5
05:23:36.20 +72:15:28.4
04:09:44.10 +68:22:55.7
05:22:44.92 +71:33:13.4
04:17:15.32 +66:59:00.9
05:27:58.48 +73:37:41.4
04:13:00.12 +68:33:59.5
04:19:10.67 +74:37:05.8
03:45:46.08 +72:07:50.9
03:35:33.81 +72:09:34.6
05:21:00.13 +67:06:46.4
04:47:46.24 +71:29:19.1
05:09:18.90 +64:59:29.0
04:48:25.91 +74:26:44.6
03:41:09.93 +64:55:31.5
04:17:38.93 +67:04:05.5
03:59:29.24 +73:51:00.6
04:02:16.51 +70:20:27.8
05:21:40.64 +67:08:13.9
03:55:20.71 +67:27:40.9
05:28:24.76 +72:20:51.2
03:49:45.91 +66:15:02.3
05:25:27.11 +70:14:48.7
04:27:18.63 +71:47:29.7
05:47:42.05 +63:51:33.0
04:26:59.32 +67:44:57.1
04:14:17.98 +70:46:27.3
04:33:24.87 +68:43:31.3
04:11:01.41 +72:56:59.2
05:03:24.03 +68:22:02.9
03:57:22.44 +71:25:13.2
04:32:41.69 +72:06:18.2
05:16:16.53 +73:34:02.9
03:44:22.59 +69:26:59.6
03:43:37.98 +65:18:07.0
03:39:22.57 +72:29:10.2
04:09:29.90 +67:40:43.9
04:17:17.51 +72:26:52.7
04:28:56.80 +71:42:40.0
03:29:05.95 +72:34:27.7
04:21:32.08 +73:15:18.0
04:50:09.07 +70:08:17.5
04:08:57.10 +70:52:51.0
04:49:57.43 +72:53:08.0
04:22:59.13 +72:23:38.8
04:18:04.63 +72:27:35.5
04:49:51.47 +72:55:37.9
05:52:20.64 +67:28:37.5
04:35:40.16 +70:45:20.5
04:56:00.41 +72:50:52.9
04:03:44.64 +74:47:27.9
04:05:31.60 +71:29:14.5
04:27:07.88 +73:05:36.1
03:49:44.93 +74:40:41.0
03:56:05.81 +69:11:18.7
04:25:06.38 +74:17:00.6
05:58:53.03 +73:19:28.0
04:10:04.82 +68:43:40.5
04:04:50.45 +71:07:36.3
04:28:59.69 +71:40:57.0
03:34:20.81 +74:24:39.9
04:47:58.33 +70:11:14.0
04:31:47.38 +73:35:51.2
04:04:26.73 +74:32:47.9
04:16:43.13 +74:05:24.2
05:10:59.14 +67:46:34.0
04:00:27.02 +74:52:12.7
05:04:44.13 +70:01:36.2
04:16:53.25 +69:10:01.7
05:30:17.85 +72:06:09.7
04:28:20.46 +72:11:56.8
04:01:42.66 +71:10:40.2
05:13:26.36 +67:30:48.7
03:47:48.46 +71:28:10.7
04:12:50.87 +72:36:29.7
04:30:15.17 +71:07:54.9
04:47:10.69 +68:13:44.9
05:14:14.35 +72:17:16.8
05:33:20.14 +71:26:28.1
05:49:53.03 +64:51:32.5
04:08:45.99 +72:57:55.2
03:37:47.29 +70:36:07.2
04:33:43.38 +69:31:02.3
03:54:50.39 +73:15:07.6
03:43:40.85 +74:07:45.9
03:25:11.52 +69:09:38.4
04:34:40.02 +70:19:54.1
04:07:40.13 +73:08:41.2
04:41:23.86 +74:33:35.1
05:52:55.63 +71:04:24.7
04:59:20.88 +74:14:02.2
04:07:29.01 +73:08:18.9
04:28:12.81 +72:44:30.5
05:42:22.76 +73:44:12.0
04:18:20.56 +69:21:42.9
04:49:58.99 +70:21:49.2
04:30:27.18 +69:08:45.4
03:55:32.14 +72:12:09.9
05:22:54.10 +73:35:19.3
04:30:35.02 +74:52:15.3
04:04:38.77 +71:07:13.1
05:51:59.06 +73:16:02.2
04:15:14.68 +68:02:33.6
04:40:37.05 +68:37:18.3
03:35:01.80 +71:45:16.5
04:39:13.58 +74:52:20.2
04:43:49.57 +68:38:15.6
04:42:19.75 +70:57:59.6
04:40:21.20 +70:31:01.2
04:51:18.07 +72:47:35.5
04:49:04.46 +74:15:36.3
06:29:09.83 +71:43:23.1
04:09:59.36 +72:59:44.2
04:18:00.31 +71:14:04.1
05:18:58.24 +64:31:36.5
03:30:07.19 +68:46:01.8
########### Completed Cam-06-Q1b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ1.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
05:18:59.88 +64:31:26.9
04:17:58.82 +71:13:47.4
04:39:04.72 +69:38:45.2
04:33:37.91 +68:34:29.0
05:19:55.00 +72:59:35.7
04:58:06.80 +74:35:53.5
04:32:38.67 +73:19:54.2
04:14:04.72 +68:05:08.5
04:50:07.41 +69:35:22.3
04:15:18.36 +71:12:30.5
04:10:48.41 +69:12:03.4
05:00:53.28 +72:21:19.7
06:18:34.44 +70:58:19.0
06:06:19.66 +71:33:14.9
04:32:03.50 +69:06:00.2
03:41:23.14 +73:57:34.0
04:16:59.23 +66:56:34.0
04:02:25.24 +73:49:49.2
03:11:19.38 +71:20:07.2
06:10:38.34 +69:13:50.1
03:48:57.57 +74:40:49.8
03:55:17.27 +68:37:36.4
04:50:42.12 +66:56:50.1
03:57:25.02 +71:08:04.4
03:57:05.49 +69:13:40.5
04:36:07.77 +72:44:58.4
03:42:20.51 +64:48:38.9
04:01:32.93 +72:47:39.3
05:02:57.33 +67:49:32.8
04:20:30.65 +67:31:02.0
04:34:24.79 +65:49:45.6
04:05:43.61 +69:16:58.7
04:18:00.13 +71:13:44.2
04:46:57.39 +65:43:21.2
05:47:13.95 +63:52:18.1
04:35:12.83 +72:39:17.2
04:20:23.07 +74:29:04.2
05:21:42.03 +73:12:40.0
03:31:10.38 +71:05:34.5
04:26:16.31 +74:20:57.9
04:13:18.95 +72:06:40.4
04:59:21.73 +70:28:04.0
05:02:35.63 +66:52:10.2
04:00:26.55 +68:34:44.3
03:41:11.32 +64:55:58.3
05:30:41.56 +64:20:56.8
05:13:09.21 +67:32:21.5
05:23:36.20 +72:15:28.4
04:09:44.10 +68:22:55.7
05:22:44.92 +71:33:13.4
04:17:15.32 +66:59:00.9
05:27:58.48 +73:37:41.4
04:13:00.12 +68:33:59.5
04:19:10.67 +74:37:05.8
03:45:46.08 +72:07:50.9
03:35:33.81 +72:09:34.6
05:21:00.13 +67:06:46.4
04:47:46.24 +71:29:19.1
05:09:18.90 +64:59:29.0
04:48:25.91 +74:26:44.6
03:41:09.93 +64:55:31.5
04:17:38.93 +67:04:05.5
03:59:29.24 +73:51:00.6
04:02:16.51 +70:20:27.8
05:21:40.64 +67:08:13.9
03:55:20.71 +67:27:40.9
05:28:24.76 +72:20:51.2
03:49:45.91 +66:15:02.3
05:25:27.11 +70:14:48.7
04:27:18.63 +71:47:29.7
05:47:42.05 +63:51:33.0
04:26:59.32 +67:44:57.1
04:14:17.98 +70:46:27.3
04:33:24.87 +68:43:31.3
04:11:01.41 +72:56:59.2
05:03:24.03 +68:22:02.9
03:57:22.44 +71:25:13.2
04:32:41.69 +72:06:18.2
05:16:16.53 +73:34:02.9
03:44:22.59 +69:26:59.6
03:43:37.98 +65:18:07.0
03:39:22.57 +72:29:10.2
04:09:29.90 +67:40:43.9
04:17:17.51 +72:26:52.7
04:28:56.80 +71:42:40.0
03:29:05.95 +72:34:27.7
04:21:32.08 +73:15:18.0
04:50:09.07 +70:08:17.5
04:08:57.10 +70:52:51.0
04:49:57.43 +72:53:08.0
04:22:59.13 +72:23:38.8
04:18:04.63 +72:27:35.5
04:49:51.47 +72:55:37.9
05:52:20.64 +67:28:37.5
04:35:40.16 +70:45:20.5
04:56:00.41 +72:50:52.9
04:03:44.64 +74:47:27.9
04:05:31.60 +71:29:14.5
04:27:07.88 +73:05:36.1
03:49:44.93 +74:40:41.0
03:56:05.81 +69:11:18.7
04:25:06.38 +74:17:00.6
05:58:53.03 +73:19:28.0
04:10:04.82 +68:43:40.5
04:04:50.45 +71:07:36.3
04:28:59.69 +71:40:57.0
03:34:20.81 +74:24:39.9
04:47:58.33 +70:11:14.0
04:31:47.38 +73:35:51.2
04:04:26.73 +74:32:47.9
04:16:43.13 +74:05:24.2
05:10:59.14 +67:46:34.0
04:00:27.02 +74:52:12.7
05:04:44.13 +70:01:36.2
04:16:53.25 +69:10:01.7
05:30:17.85 +72:06:09.7
04:28:20.46 +72:11:56.8
04:01:42.66 +71:10:40.2
05:13:26.36 +67:30:48.7
03:47:48.46 +71:28:10.7
04:12:50.87 +72:36:29.7
04:30:15.17 +71:07:54.9
04:47:10.69 +68:13:44.9
05:14:14.35 +72:17:16.8
05:33:20.14 +71:26:28.1
05:49:53.03 +64:51:32.5
04:08:45.99 +72:57:55.2
03:37:47.29 +70:36:07.2
04:33:43.38 +69:31:02.3
03:54:50.39 +73:15:07.6
03:43:40.85 +74:07:45.9
03:25:11.52 +69:09:38.4
04:34:40.02 +70:19:54.1
04:07:40.13 +73:08:41.2
04:41:23.86 +74:33:35.1
05:52:55.63 +71:04:24.7
04:59:20.88 +74:14:02.2
04:07:29.01 +73:08:18.9
04:28:12.81 +72:44:30.5
05:42:22.76 +73:44:12.0
04:18:20.56 +69:21:42.9
04:49:58.99 +70:21:49.2
04:30:27.18 +69:08:45.4
03:55:32.14 +72:12:09.9
05:22:54.10 +73:35:19.3
04:30:35.02 +74:52:15.3
04:04:38.77 +71:07:13.1
05:51:59.06 +73:16:02.2
04:15:14.68 +68:02:33.6
04:40:37.05 +68:37:18.3
03:35:01.80 +71:45:16.5
04:39:13.58 +74:52:20.2
04:43:49.57 +68:38:15.6
04:42:19.75 +70:57:59.6
04:40:21.20 +70:31:01.2
04:51:18.07 +72:47:35.5
04:49:04.46 +74:15:36.3
06:29:09.83 +71:43:23.1
04:09:59.36 +72:59:44.2
05:18:58.24 +64:31:36.5
03:30:07.19 +68:46:01.8
04:18:00.31 +71:14:04.1
###################################################################################
05:18:59.88 +64:31:26.9 -- not an asteroid (will add it to exclusion list)
04:17:58.82 +71:13:47.4 -- not an asteroid (will add it to exclusion list)
04:39:04.72 +69:38:45.2 -- not an asteroid (will add it to exclusion list)
04:33:37.91 +68:34:29.0 -- not an asteroid (will add it to exclusion list)
05:19:55.00 +72:59:35.7 -- not an asteroid (will add it to exclusion list)
04:58:06.80 +74:35:53.5 -- not an asteroid (will add it to exclusion list)
04:32:38.67 +73:19:54.2 -- not an asteroid (will add it to exclusion list)
04:14:04.72 +68:05:08.5 -- not an asteroid (will add it to exclusion list)
04:50:07.41 +69:35:22.3 -- not an asteroid (will add it to exclusion list)
04:15:18.36 +71:12:30.5 -- not an asteroid (will add it to exclusion list)
04:10:48.41 +69:12:03.4 -- not an asteroid (will add it to exclusion list)
05:00:53.28 +72:21:19.7 -- not an asteroid (will add it to exclusion list)
06:18:34.44 +70:58:19.0 -- not an asteroid (will add it to exclusion list)
06:06:19.66 +71:33:14.9 -- not an asteroid (will add it to exclusion list)
04:32:03.50 +69:06:00.2 -- not an asteroid (will add it to exclusion list)
03:41:23.14 +73:57:34.0 -- not an asteroid (will add it to exclusion list)
04:16:59.23 +66:56:34.0 -- not an asteroid (will add it to exclusion list)
04:02:25.24 +73:49:49.2 -- not an asteroid (will add it to exclusion list)
03:11:19.38 +71:20:07.2 -- not an asteroid (will add it to exclusion list)
06:10:38.34 +69:13:50.1 -- not an asteroid (will add it to exclusion list)
03:48:57.57 +74:40:49.8 -- not an asteroid (will add it to exclusion list)
03:55:17.27 +68:37:36.4 -- not an asteroid (will add it to exclusion list)
04:50:42.12 +66:56:50.1 -- not an asteroid (will add it to exclusion list)
03:57:25.02 +71:08:04.4 -- not an asteroid (will add it to exclusion list)
03:57:05.49 +69:13:40.5 -- not an asteroid (will add it to exclusion list)
04:36:07.77 +72:44:58.4 -- not an asteroid (will add it to exclusion list)
03:42:20.51 +64:48:38.9 -- not an asteroid (will add it to exclusion list)
04:01:32.93 +72:47:39.3 -- not an asteroid (will add it to exclusion list)
05:02:57.33 +67:49:32.8 -- not an asteroid (will add it to exclusion list)
04:20:30.65 +67:31:02.0 -- not an asteroid (will add it to exclusion list)
04:34:24.79 +65:49:45.6 -- not an asteroid (will add it to exclusion list)
04:05:43.61 +69:16:58.7 -- not an asteroid (will add it to exclusion list)
04:18:00.13 +71:13:44.2 -- not an asteroid (will add it to exclusion list)
04:46:57.39 +65:43:21.2 -- not an asteroid (will add it to exclusion list)
05:47:13.95 +63:52:18.1 -- not an asteroid (will add it to exclusion list)
04:35:12.83 +72:39:17.2 -- not an asteroid (will add it to exclusion list)
04:20:23.07 +74:29:04.2 -- not an asteroid (will add it to exclusion list)
05:21:42.03 +73:12:40.0 -- not an asteroid (will add it to exclusion list)
03:31:10.38 +71:05:34.5 -- not an asteroid (will add it to exclusion list)
04:26:16.31 +74:20:57.9 -- not an asteroid (will add it to exclusion list)
04:13:18.95 +72:06:40.4 -- not an asteroid (will add it to exclusion list)
04:59:21.73 +70:28:04.0 -- not an asteroid (will add it to exclusion list)
05:02:35.63 +66:52:10.2 -- not an asteroid (will add it to exclusion list)
04:00:26.55 +68:34:44.3 -- not an asteroid (will add it to exclusion list)
03:41:11.32 +64:55:58.3 -- not an asteroid (will add it to exclusion list)
05:30:41.56 +64:20:56.8 -- not an asteroid (will add it to exclusion list)
05:13:09.21 +67:32:21.5 -- not an asteroid (will add it to exclusion list)
05:23:36.20 +72:15:28.4 -- not an asteroid (will add it to exclusion list)
04:09:44.10 +68:22:55.7 -- not an asteroid (will add it to exclusion list)
05:22:44.92 +71:33:13.4 -- not an asteroid (will add it to exclusion list)
04:17:15.32 +66:59:00.9 -- not an asteroid (will add it to exclusion list)
05:27:58.48 +73:37:41.4 -- not an asteroid (will add it to exclusion list)
04:13:00.12 +68:33:59.5 -- not an asteroid (will add it to exclusion list)
04:19:10.67 +74:37:05.8 -- not an asteroid (will add it to exclusion list)
03:45:46.08 +72:07:50.9 -- not an asteroid (will add it to exclusion list)
03:35:33.81 +72:09:34.6 -- not an asteroid (will add it to exclusion list)
05:21:00.13 +67:06:46.4 -- not an asteroid (will add it to exclusion list)
04:47:46.24 +71:29:19.1 -- not an asteroid (will add it to exclusion list)
05:09:18.90 +64:59:29.0 -- not an asteroid (will add it to exclusion list)
04:48:25.91 +74:26:44.6 -- not an asteroid (will add it to exclusion list)
03:41:09.93 +64:55:31.5 -- not an asteroid (will add it to exclusion list)
04:17:38.93 +67:04:05.5 -- not an asteroid (will add it to exclusion list)
03:59:29.24 +73:51:00.6 -- not an asteroid (will add it to exclusion list)
04:02:16.51 +70:20:27.8 -- not an asteroid (will add it to exclusion list)
05:21:40.64 +67:08:13.9 -- not an asteroid (will add it to exclusion list)
03:55:20.71 +67:27:40.9 -- not an asteroid (will add it to exclusion list)
05:28:24.76 +72:20:51.2 -- not an asteroid (will add it to exclusion list)
03:49:45.91 +66:15:02.3 -- not an asteroid (will add it to exclusion list)
05:25:27.11 +70:14:48.7 -- not an asteroid (will add it to exclusion list)
04:27:18.63 +71:47:29.7 -- not an asteroid (will add it to exclusion list)
05:47:42.05 +63:51:33.0 -- not an asteroid (will add it to exclusion list)
04:26:59.32 +67:44:57.1 -- not an asteroid (will add it to exclusion list)
04:14:17.98 +70:46:27.3 -- not an asteroid (will add it to exclusion list)
04:33:24.87 +68:43:31.3 -- not an asteroid (will add it to exclusion list)
04:11:01.41 +72:56:59.2 -- not an asteroid (will add it to exclusion list)
05:03:24.03 +68:22:02.9 -- not an asteroid (will add it to exclusion list)
03:57:22.44 +71:25:13.2 -- not an asteroid (will add it to exclusion list)
04:32:41.69 +72:06:18.2 -- not an asteroid (will add it to exclusion list)
05:16:16.53 +73:34:02.9 -- not an asteroid (will add it to exclusion list)
03:44:22.59 +69:26:59.6 -- not an asteroid (will add it to exclusion list)
03:43:37.98 +65:18:07.0 -- not an asteroid (will add it to exclusion list)
03:39:22.57 +72:29:10.2 -- not an asteroid (will add it to exclusion list)
04:09:29.90 +67:40:43.9 -- not an asteroid (will add it to exclusion list)
04:17:17.51 +72:26:52.7 -- not an asteroid (will add it to exclusion list)
04:28:56.80 +71:42:40.0 -- not an asteroid (will add it to exclusion list)
03:29:05.95 +72:34:27.7 -- not an asteroid (will add it to exclusion list)
04:21:32.08 +73:15:18.0 -- not an asteroid (will add it to exclusion list)
04:50:09.07 +70:08:17.5 -- not an asteroid (will add it to exclusion list)
04:08:57.10 +70:52:51.0 -- not an asteroid (will add it to exclusion list)
04:49:57.43 +72:53:08.0 -- not an asteroid (will add it to exclusion list)
04:22:59.13 +72:23:38.8 -- not an asteroid (will add it to exclusion list)
04:18:04.63 +72:27:35.5 -- not an asteroid (will add it to exclusion list)
04:49:51.47 +72:55:37.9 -- not an asteroid (will add it to exclusion list)
05:52:20.64 +67:28:37.5 -- not an asteroid (will add it to exclusion list)
04:35:40.16 +70:45:20.5 -- not an asteroid (will add it to exclusion list)
04:56:00.41 +72:50:52.9 -- not an asteroid (will add it to exclusion list)
04:03:44.64 +74:47:27.9 -- not an asteroid (will add it to exclusion list)
04:05:31.60 +71:29:14.5 -- not an asteroid (will add it to exclusion list)
04:27:07.88 +73:05:36.1 -- not an asteroid (will add it to exclusion list)
03:49:44.93 +74:40:41.0 -- not an asteroid (will add it to exclusion list)
03:56:05.81 +69:11:18.7 -- not an asteroid (will add it to exclusion list)
04:25:06.38 +74:17:00.6 -- not an asteroid (will add it to exclusion list)
05:58:53.03 +73:19:28.0 -- not an asteroid (will add it to exclusion list)
04:10:04.82 +68:43:40.5 -- not an asteroid (will add it to exclusion list)
04:04:50.45 +71:07:36.3 -- not an asteroid (will add it to exclusion list)
04:28:59.69 +71:40:57.0 -- not an asteroid (will add it to exclusion list)
03:34:20.81 +74:24:39.9 -- not an asteroid (will add it to exclusion list)
04:47:58.33 +70:11:14.0 -- not an asteroid (will add it to exclusion list)
04:31:47.38 +73:35:51.2 -- not an asteroid (will add it to exclusion list)
04:04:26.73 +74:32:47.9 -- not an asteroid (will add it to exclusion list)
04:16:43.13 +74:05:24.2 -- not an asteroid (will add it to exclusion list)
05:10:59.14 +67:46:34.0 -- not an asteroid (will add it to exclusion list)
04:00:27.02 +74:52:12.7 -- not an asteroid (will add it to exclusion list)
05:04:44.13 +70:01:36.2 -- not an asteroid (will add it to exclusion list)
04:16:53.25 +69:10:01.7 -- not an asteroid (will add it to exclusion list)
05:30:17.85 +72:06:09.7 -- not an asteroid (will add it to exclusion list)
04:28:20.46 +72:11:56.8 -- not an asteroid (will add it to exclusion list)
04:01:42.66 +71:10:40.2 -- not an asteroid (will add it to exclusion list)
05:13:26.36 +67:30:48.7 -- not an asteroid (will add it to exclusion list)
03:47:48.46 +71:28:10.7 -- not an asteroid (will add it to exclusion list)
04:12:50.87 +72:36:29.7 -- not an asteroid (will add it to exclusion list)
04:30:15.17 +71:07:54.9 -- not an asteroid (will add it to exclusion list)
04:47:10.69 +68:13:44.9 -- not an asteroid (will add it to exclusion list)
05:14:14.35 +72:17:16.8 -- not an asteroid (will add it to exclusion list)
05:33:20.14 +71:26:28.1 -- not an asteroid (will add it to exclusion list)
05:49:53.03 +64:51:32.5 -- not an asteroid (will add it to exclusion list)
04:08:45.99 +72:57:55.2 -- not an asteroid (will add it to exclusion list)
03:37:47.29 +70:36:07.2 -- not an asteroid (will add it to exclusion list)
04:33:43.38 +69:31:02.3 -- not an asteroid (will add it to exclusion list)
03:54:50.39 +73:15:07.6 -- not an asteroid (will add it to exclusion list)
03:43:40.85 +74:07:45.9 -- not an asteroid (will add it to exclusion list)
03:25:11.52 +69:09:38.4 -- not an asteroid (will add it to exclusion list)
04:34:40.02 +70:19:54.1 -- not an asteroid (will add it to exclusion list)
04:07:40.13 +73:08:41.2 -- not an asteroid (will add it to exclusion list)
04:41:23.86 +74:33:35.1 -- not an asteroid (will add it to exclusion list)
05:52:55.63 +71:04:24.7 -- not an asteroid (will add it to exclusion list)
04:59:20.88 +74:14:02.2 -- not an asteroid (will add it to exclusion list)
04:07:29.01 +73:08:18.9 -- not an asteroid (will add it to exclusion list)
04:28:12.81 +72:44:30.5 -- not an asteroid (will add it to exclusion list)
05:42:22.76 +73:44:12.0 -- not an asteroid (will add it to exclusion list)
04:18:20.56 +69:21:42.9 -- not an asteroid (will add it to exclusion list)
04:49:58.99 +70:21:49.2 -- not an asteroid (will add it to exclusion list)
04:30:27.18 +69:08:45.4 -- not an asteroid (will add it to exclusion list)
03:55:32.14 +72:12:09.9 -- not an asteroid (will add it to exclusion list)
05:22:54.10 +73:35:19.3 -- not an asteroid (will add it to exclusion list)
04:30:35.02 +74:52:15.3 -- not an asteroid (will add it to exclusion list)
04:04:38.77 +71:07:13.1 -- not an asteroid (will add it to exclusion list)
05:51:59.06 +73:16:02.2 -- not an asteroid (will add it to exclusion list)
04:15:14.68 +68:02:33.6 -- not an asteroid (will add it to exclusion list)
04:40:37.05 +68:37:18.3 -- not an asteroid (will add it to exclusion list)
03:35:01.80 +71:45:16.5 -- not an asteroid (will add it to exclusion list)
04:39:13.58 +74:52:20.2 -- not an asteroid (will add it to exclusion list)
04:43:49.57 +68:38:15.6 -- not an asteroid (will add it to exclusion list)
04:42:19.75 +70:57:59.6 -- not an asteroid (will add it to exclusion list)
04:40:21.20 +70:31:01.2 -- not an asteroid (will add it to exclusion list)
04:51:18.07 +72:47:35.5 -- not an asteroid (will add it to exclusion list)
04:49:04.46 +74:15:36.3 -- not an asteroid (will add it to exclusion list)
06:29:09.83 +71:43:23.1 -- not an asteroid (will add it to exclusion list)
04:09:59.36 +72:59:44.2 -- not an asteroid (will add it to exclusion list)
05:18:58.24 +64:31:36.5 -- not an asteroid (will add it to exclusion list)
03:30:07.19 +68:46:01.8 -- not an asteroid (will add it to exclusion list)
04:18:00.31 +71:14:04.1 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
03:11:19.38 +71:20:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:25:11.52 +69:09:38.4 -- does not seem to be a hot pixel (will add it to exclusion list)
03:29:05.95 +72:34:27.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:30:07.19 +68:46:01.8 -- does not seem to be a hot pixel (will add it to exclusion list)
03:31:10.38 +71:05:34.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:34:20.81 +74:24:39.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:35:01.80 +71:45:16.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:35:33.81 +72:09:34.6 -- does not seem to be a hot pixel (will add it to exclusion list)
03:37:47.29 +70:36:07.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:39:22.57 +72:29:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:41:09.93 +64:55:31.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:41:11.32 +64:55:58.3 -- does not seem to be a hot pixel (will add it to exclusion list)
03:41:23.14 +73:57:34.0 -- does not seem to be a hot pixel (will add it to exclusion list)
03:42:20.51 +64:48:38.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:43:37.98 +65:18:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
03:43:40.85 +74:07:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:44:22.59 +69:26:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
03:45:46.08 +72:07:50.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:47:48.46 +71:28:10.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:48:57.57 +74:40:49.8 -- does not seem to be a hot pixel (will add it to exclusion list)
03:49:44.93 +74:40:41.0 -- does not seem to be a hot pixel (will add it to exclusion list)
03:49:45.91 +66:15:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
03:54:50.39 +73:15:07.6 -- does not seem to be a hot pixel (will add it to exclusion list)
03:55:17.27 +68:37:36.4 -- does not seem to be a hot pixel (will add it to exclusion list)
03:55:20.71 +67:27:40.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:55:32.14 +72:12:09.9 -- does not seem to be a hot pixel (will add it to exclusion list)
03:56:05.81 +69:11:18.7 -- does not seem to be a hot pixel (will add it to exclusion list)
03:57:05.49 +69:13:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
03:57:22.44 +71:25:13.2 -- does not seem to be a hot pixel (will add it to exclusion list)
03:57:25.02 +71:08:04.4 -- does not seem to be a hot pixel (will add it to exclusion list)
03:59:29.24 +73:51:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:00:26.55 +68:34:44.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:00:27.02 +74:52:12.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:01:32.93 +72:47:39.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:01:42.66 +71:10:40.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:02:16.51 +70:20:27.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:02:25.24 +73:49:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:03:44.64 +74:47:27.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:04:26.73 +74:32:47.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:04:38.77 +71:07:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:04:50.45 +71:07:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:05:31.60 +71:29:14.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:05:43.61 +69:16:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:07:29.01 +73:08:18.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:07:40.13 +73:08:41.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:08:45.99 +72:57:55.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:08:57.10 +70:52:51.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:09:29.90 +67:40:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:09:44.10 +68:22:55.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:09:59.36 +72:59:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:10:04.82 +68:43:40.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:10:48.41 +69:12:03.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:11:01.41 +72:56:59.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:12:50.87 +72:36:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:13:00.12 +68:33:59.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:13:18.95 +72:06:40.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:14:04.72 +68:05:08.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:14:17.98 +70:46:27.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:15:14.68 +68:02:33.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:15:18.36 +71:12:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:16:43.13 +74:05:24.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:16:53.25 +69:10:01.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:16:59.23 +66:56:34.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:15.32 +66:59:00.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:17.51 +72:26:52.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:38.93 +67:04:05.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:17:58.82 +71:13:47.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:18:00.13 +71:13:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:18:00.31 +71:14:04.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:18:04.63 +72:27:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:18:20.56 +69:21:42.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:19:10.67 +74:37:05.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:20:23.07 +74:29:04.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:20:30.65 +67:31:02.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:21:32.08 +73:15:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:22:59.13 +72:23:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:25:06.38 +74:17:00.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:16.31 +74:20:57.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:26:59.32 +67:44:57.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:27:07.88 +73:05:36.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:27:18.63 +71:47:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
04:28:12.81 +72:44:30.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:28:20.46 +72:11:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
04:28:56.80 +71:42:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:28:59.69 +71:40:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:15.17 +71:07:54.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:27.18 +69:08:45.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:30:35.02 +74:52:15.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:31:47.38 +73:35:51.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:32:03.50 +69:06:00.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:32:38.67 +73:19:54.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:32:41.69 +72:06:18.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:33:24.87 +68:43:31.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:33:37.91 +68:34:29.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:33:43.38 +69:31:02.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:34:24.79 +65:49:45.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:34:40.02 +70:19:54.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:35:12.83 +72:39:17.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:35:40.16 +70:45:20.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:36:07.77 +72:44:58.4 -- does not seem to be a hot pixel (will add it to exclusion list)
04:39:04.72 +69:38:45.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:39:13.58 +74:52:20.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:40:21.20 +70:31:01.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:40:37.05 +68:37:18.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:41:23.86 +74:33:35.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:42:19.75 +70:57:59.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:43:49.57 +68:38:15.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:46:57.39 +65:43:21.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:47:10.69 +68:13:44.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:47:46.24 +71:29:19.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:47:58.33 +70:11:14.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:48:25.91 +74:26:44.6 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:04.46 +74:15:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:51.47 +72:55:37.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:57.43 +72:53:08.0 -- does not seem to be a hot pixel (will add it to exclusion list)
04:49:58.99 +70:21:49.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:07.41 +69:35:22.3 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:09.07 +70:08:17.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:50:42.12 +66:56:50.1 -- does not seem to be a hot pixel (will add it to exclusion list)
04:51:18.07 +72:47:35.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:56:00.41 +72:50:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
04:58:06.80 +74:35:53.5 -- does not seem to be a hot pixel (will add it to exclusion list)
04:59:20.88 +74:14:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
04:59:21.73 +70:28:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:00:53.28 +72:21:19.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:02:35.63 +66:52:10.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:02:57.33 +67:49:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:03:24.03 +68:22:02.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:04:44.13 +70:01:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:09:18.90 +64:59:29.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:10:59.14 +67:46:34.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:13:09.21 +67:32:21.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:13:26.36 +67:30:48.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:14:14.35 +72:17:16.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:16:16.53 +73:34:02.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:18:58.24 +64:31:36.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:18:59.88 +64:31:26.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:19:55.00 +72:59:35.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:21:00.13 +67:06:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:21:40.64 +67:08:13.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:21:42.03 +73:12:40.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:22:44.92 +71:33:13.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:22:54.10 +73:35:19.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:23:36.20 +72:15:28.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:25:27.11 +70:14:48.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:27:58.48 +73:37:41.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:28:24.76 +72:20:51.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:30:17.85 +72:06:09.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:30:41.56 +64:20:56.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:33:20.14 +71:26:28.1 -- does not seem to be a hot pixel (will add it to exclusion list)
05:42:22.76 +73:44:12.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:13.95 +63:52:18.1 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:42.05 +63:51:33.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:49:53.03 +64:51:32.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:51:59.06 +73:16:02.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:52:20.64 +67:28:37.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:52:55.63 +71:04:24.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:58:53.03 +73:19:28.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:06:19.66 +71:33:14.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:10:38.34 +69:13:50.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:18:34.44 +70:58:19.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:29:09.83 +71:43:23.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)
03:11:19.38 +71:20:07.2 -- not a known variable star
03:25:11.52 +69:09:38.4 -- not a known variable star
03:29:05.95 +72:34:27.7 -- not a known variable star
03:30:07.19 +68:46:01.8 -- a known variable star
03:31:10.38 +71:05:34.5 -- not a known variable star
03:34:20.81 +74:24:39.9 -- not a known variable star
03:35:01.80 +71:45:16.5 -- not a known variable star
03:35:33.81 +72:09:34.6 -- not a known variable star
03:37:47.29 +70:36:07.2 -- not a known variable star
03:39:22.57 +72:29:10.2 -- not a known variable star
03:41:09.93 +64:55:31.5 -- not a known variable star
03:41:11.32 +64:55:58.3 -- not a known variable star
03:41:23.14 +73:57:34.0 -- not a known variable star
03:42:20.51 +64:48:38.9 -- not a known variable star
03:43:37.98 +65:18:07.0 -- not a known variable star
03:43:40.85 +74:07:45.9 -- not a known variable star
03:44:22.59 +69:26:59.6 -- not a known variable star
03:45:46.08 +72:07:50.9 -- not a known variable star
03:47:48.46 +71:28:10.7 -- not a known variable star
03:48:57.57 +74:40:49.8 -- not a known variable star
03:49:44.93 +74:40:41.0 -- not a known variable star
03:49:45.91 +66:15:02.3 -- not a known variable star
03:54:50.39 +73:15:07.6 -- a known variable star
03:55:17.27 +68:37:36.4 -- not a known variable star
03:55:20.71 +67:27:40.9 -- not a known variable star
03:55:32.14 +72:12:09.9 -- not a known variable star
03:56:05.81 +69:11:18.7 -- not a known variable star
03:57:05.49 +69:13:40.5 -- not a known variable star
03:57:22.44 +71:25:13.2 -- not a known variable star
03:57:25.02 +71:08:04.4 -- not a known variable star
03:59:29.24 +73:51:00.6 -- not a known variable star
04:00:26.55 +68:34:44.3 -- not a known variable star
04:00:27.02 +74:52:12.7 -- not a known variable star
04:01:32.93 +72:47:39.3 -- not a known variable star
04:01:42.66 +71:10:40.2 -- not a known variable star
04:02:16.51 +70:20:27.8 -- not a known variable star
04:02:25.24 +73:49:49.2 -- not a known variable star
04:03:44.64 +74:47:27.9 -- not a known variable star
04:04:26.73 +74:32:47.9 -- not a known variable star
04:04:38.77 +71:07:13.1 -- not a known variable star
04:04:50.45 +71:07:36.3 -- not a known variable star
04:05:31.60 +71:29:14.5 -- not a known variable star
04:05:43.61 +69:16:58.7 -- not a known variable star
04:07:29.01 +73:08:18.9 -- not a known variable star
04:07:40.13 +73:08:41.2 -- not a known variable star
04:08:45.99 +72:57:55.2 -- not a known variable star
04:08:57.10 +70:52:51.0 -- not a known variable star
04:09:29.90 +67:40:43.9 -- not a known variable star
04:09:44.10 +68:22:55.7 -- not a known variable star
04:09:59.36 +72:59:44.2 -- not a known variable star
04:10:04.82 +68:43:40.5 -- not a known variable star
04:10:48.41 +69:12:03.4 -- not a known variable star
04:11:01.41 +72:56:59.2 -- not a known variable star
04:12:50.87 +72:36:29.7 -- not a known variable star
04:13:00.12 +68:33:59.5 -- not a known variable star
04:13:18.95 +72:06:40.4 -- not a known variable star
04:14:04.72 +68:05:08.5 -- not a known variable star
04:14:17.98 +70:46:27.3 -- not a known variable star
04:15:14.68 +68:02:33.6 -- not a known variable star
04:15:18.36 +71:12:30.5 -- not a known variable star
04:16:43.13 +74:05:24.2 -- not a known variable star
04:16:53.25 +69:10:01.7 -- not a known variable star
04:16:59.23 +66:56:34.0 -- not a known variable star
04:17:15.32 +66:59:00.9 -- not a known variable star
04:17:17.51 +72:26:52.7 -- not a known variable star
04:17:38.93 +67:04:05.5 -- not a known variable star
04:17:58.82 +71:13:47.4 -- a known variable star
04:18:00.13 +71:13:44.2 -- a known variable star
04:18:00.31 +71:14:04.1 -- a known variable star
04:18:04.63 +72:27:35.5 -- not a known variable star
04:18:20.56 +69:21:42.9 -- not a known variable star
04:19:10.67 +74:37:05.8 -- not a known variable star
04:20:23.07 +74:29:04.2 -- not a known variable star
04:20:30.65 +67:31:02.0 -- not a known variable star
04:21:32.08 +73:15:18.0 -- not a known variable star
04:22:59.13 +72:23:38.8 -- not a known variable star
04:25:06.38 +74:17:00.6 -- not a known variable star
04:26:16.31 +74:20:57.9 -- not a known variable star
04:26:59.32 +67:44:57.1 -- a known variable star
04:27:07.88 +73:05:36.1 -- not a known variable star
04:27:18.63 +71:47:29.7 -- not a known variable star
04:28:12.81 +72:44:30.5 -- not a known variable star
04:28:20.46 +72:11:56.8 -- not a known variable star
04:28:56.80 +71:42:40.0 -- not a known variable star
04:28:59.69 +71:40:57.0 -- not a known variable star
04:30:15.17 +71:07:54.9 -- not a known variable star
04:30:27.18 +69:08:45.4 -- not a known variable star
04:30:35.02 +74:52:15.3 -- not a known variable star
04:31:47.38 +73:35:51.2 -- not a known variable star
04:32:03.50 +69:06:00.2 -- not a known variable star
04:32:38.67 +73:19:54.2 -- not a known variable star
04:32:41.69 +72:06:18.2 -- not a known variable star
04:33:24.87 +68:43:31.3 -- not a known variable star
04:33:37.91 +68:34:29.0 -- not a known variable star
04:33:43.38 +69:31:02.3 -- not a known variable star
04:34:24.79 +65:49:45.6 -- not a known variable star
04:34:40.02 +70:19:54.1 -- not a known variable star
04:35:12.83 +72:39:17.2 -- not a known variable star
04:35:40.16 +70:45:20.5 -- not a known variable star
04:36:07.77 +72:44:58.4 -- not a known variable star
04:39:04.72 +69:38:45.2 -- not a known variable star
04:39:13.58 +74:52:20.2 -- not a known variable star
04:40:21.20 +70:31:01.2 -- not a known variable star
04:40:37.05 +68:37:18.3 -- not a known variable star
04:41:23.86 +74:33:35.1 -- not a known variable star
04:42:19.75 +70:57:59.6 -- not a known variable star
04:43:49.57 +68:38:15.6 -- not a known variable star
04:46:57.39 +65:43:21.2 -- not a known variable star
04:47:10.69 +68:13:44.9 -- not a known variable star
04:47:46.24 +71:29:19.1 -- not a known variable star
04:47:58.33 +70:11:14.0 -- not a known variable star
04:48:25.91 +74:26:44.6 -- not a known variable star
04:49:04.46 +74:15:36.3 -- a known variable star
04:49:51.47 +72:55:37.9 -- not a known variable star
04:49:57.43 +72:53:08.0 -- not a known variable star
04:49:58.99 +70:21:49.2 -- not a known variable star
04:50:07.41 +69:35:22.3 -- not a known variable star
04:50:09.07 +70:08:17.5 -- not a known variable star
04:50:42.12 +66:56:50.1 -- not a known variable star
04:51:18.07 +72:47:35.5 -- not a known variable star
04:56:00.41 +72:50:52.9 -- not a known variable star
04:58:06.80 +74:35:53.5 -- not a known variable star
04:59:20.88 +74:14:02.2 -- not a known variable star
04:59:21.73 +70:28:04.0 -- not a known variable star
05:00:53.28 +72:21:19.7 -- not a known variable star
05:02:35.63 +66:52:10.2 -- not a known variable star
05:02:57.33 +67:49:32.8 -- not a known variable star
05:03:24.03 +68:22:02.9 -- not a known variable star
05:04:44.13 +70:01:36.2 -- not a known variable star
05:09:18.90 +64:59:29.0 -- not a known variable star
05:10:59.14 +67:46:34.0 -- not a known variable star
05:13:09.21 +67:32:21.5 -- not a known variable star
05:13:26.36 +67:30:48.7 -- not a known variable star
05:14:14.35 +72:17:16.8 -- not a known variable star
05:16:16.53 +73:34:02.9 -- not a known variable star
05:18:58.24 +64:31:36.5 -- not a known variable star
05:18:59.88 +64:31:26.9 -- not a known variable star
05:19:55.00 +72:59:35.7 -- not a known variable star
05:21:00.13 +67:06:46.4 -- not a known variable star
05:21:40.64 +67:08:13.9 -- not a known variable star
05:21:42.03 +73:12:40.0 -- not a known variable star
05:22:44.92 +71:33:13.4 -- not a known variable star
05:22:54.10 +73:35:19.3 -- not a known variable star
05:23:36.20 +72:15:28.4 -- not a known variable star
05:25:27.11 +70:14:48.7 -- not a known variable star
05:27:58.48 +73:37:41.4 -- not a known variable star
05:28:24.76 +72:20:51.2 -- not a known variable star
05:30:17.85 +72:06:09.7 -- not a known variable star
05:30:41.56 +64:20:56.8 -- not a known variable star
05:33:20.14 +71:26:28.1 -- not a known variable star
05:42:22.76 +73:44:12.0 -- not a known variable star
05:47:13.95 +63:52:18.1 -- not a known variable star
05:47:42.05 +63:51:33.0 -- not a known variable star
05:49:53.03 +64:51:32.5 -- not a known variable star
05:51:59.06 +73:16:02.2 -- not a known variable star
05:52:20.64 +67:28:37.5 -- not a known variable star
05:52:55.63 +71:04:24.7 -- not a known variable star
05:58:53.03 +73:19:28.0 -- not a known variable star
06:06:19.66 +71:33:14.9 -- not a known variable star
06:10:38.34 +69:13:50.1 -- not a known variable star
06:18:34.44 +70:58:19.0 -- not a known variable star
06:29:09.83 +71:43:23.1 -- not a known variable star
Found 155 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
162 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 162 (excluding asteroids and hot pixels, 155 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)2461140.73268060 -observatory V36
23:38:26.62 -04:53:38.3 Mercury (0.2mag)
02:40:43.41 +15:34:37.9 Venus (-3.9mag)
00:01:26.21 -00:56:31.5 Mars (1.2mag)
07:10:11.35 +22:50:09.1 Jupiter (-2.1mag)
00:26:35.59 +00:32:46.6 Saturn (0.9mag)
03:46:30.76 +19:43:39.7 Uranus (5.8mag)
00:10:04.56 -00:20:12.1 Neptune (7.8mag)
20:33:28.29 -22:52:27.0 Pluto (14.5mag)
19:33:32.68 -25:57:25.5 Moon (-10.4mag)
-rw-r--r-- 1 apache apache 362 Apr 10 00:38 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461140.73268060:
07:10:03.82 +22:50:23.1 Io (5.7mag)
07:10:18.24 +22:49:52.0 Europa (5.9mag)
07:10:09.02 +22:50:06.1 Ganymede (5.3mag)
07:09:50.36 +22:50:58.1 Callisto (6.6mag)
07:13:45.80 +22:40:34.1 Himalia (15.3mag)
07:10:08.37 +22:50:16.7 Thebe (16.2mag)
07:13:49.35 +23:10:06.4 Elara (17.3mag)
07:08:40.68 +23:33:10.4 Pasiphae (17.4mag)
07:18:38.43 +22:47:33.9 Carme (18.5mag)
00:26:45.62 +00:32:37.5 Titan (8.8mag)
00:26:34.15 +00:33:02.7 Rhea (10.1mag)
00:26:27.02 +00:33:49.1 Iapetus (11.5mag)
00:26:49.21 +00:32:35.4 Hyperion (14.8mag)
00:28:16.92 +00:42:11.3 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 10 00:38 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461140.73268060:
15:10:10.10 -11:52:22.1 JWST
19:28:41.76 +11:00:34.2 Chandra
08:07:05.43 -40:53:59.6 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 10 00:38 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461140.73268060 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:49:21.32 -28:27:05.4 13.9mag P/2010 H2 (Vales)
05:02:43.26 -69:56:31.8 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:31:16.71 +31:23:59.6 17.2mag C/2017 K2 (PANSTARRS)
17:30:51.17 +09:51:31.9 17.6mag C/2021 G2 (ATLAS)
23:08:36.14 +29:00:32.7 17.0mag C/2022 E2 (ATLAS)
04:22:34.46 +25:52:44.9 15.9mag C/2022 N2 (PANSTARRS)
09:02:21.72 +31:57:59.1 16.2mag C/2022 QE78 (ATLAS)
08:30:19.45 -00:46:38.8 17.3mag C/2022 R6 (PANSTARRS)
18:54:56.74 +18:02:35.6 17.5mag C/2023 A3 (Tsuchinshan-ATLAS)
15:42:26.04 -11:36:17.5 17.5mag P/2023 B1 (PANSTARRS)
09:10:31.23 -12:49:24.7 17.6mag C/2023 F3 (ATLAS)
21:48:07.87 +62:34:52.1 17.5mag C/2023 H5 (Lemmon)
19:23:45.59 -03:39:02.1 14.2mag C/2023 R1 (PANSTARRS)
21:40:31.99 +85:07:45.7 17.8mag C/2023 X2 (Lemmon)
06:15:35.79 +63:32:51.7 17.1mag C/2024 A1 (ATLAS)
05:00:32.23 +16:14:06.2 10.7mag C/2024 E1 (Wierzchos)
16:22:49.84 +05:26:34.0 17.4mag C/2024 G6 (ATLAS)
20:19:01.48 +13:43:53.9 14.7mag C/2024 J3 (ATLAS)
03:21:15.26 -23:16:40.8 16.4mag C/2024 T5 (ATLAS)
05:11:54.93 +46:45:27.1 17.7mag C/2025 J1 (Borisov)
14:02:45.87 +41:10:02.2 14.9mag C/2025 L1 (ATLAS)
03:16:21.25 -25:20:04.1 17.8mag C/2025 Q3 (ATLAS)
23:07:00.01 +19:42:22.6 9.4mag C/2025 R3 (PANSTARRS)
12:56:37.75 +02:39:13.5 17.5mag C/2025 Y1 (ATLAS)
02:30:43.41 +03:29:24.9 11.0mag C/2026 A1 (MAPS)
23:42:54.70 +36:06:13.0 14.4mag C/2026 B2 (Sun-Gao)
18:31:41.48 -10:01:14.7 12.2mag 10P/Tempel
15:07:56.26 +03:46:14.2 13.5mag 24P/Schaumasse
11:04:27.60 -01:43:10.2 15.7mag 29P/Schwassmann-Wachmann
17:58:50.92 -09:49:49.3 17.8mag 40P/Vaisala
10:38:05.99 -04:34:50.9 16.8mag 43P/Wolf-Harrington
01:39:45.87 +16:29:53.5 17.2mag 47P/Ashbrook-Jackson
07:00:19.56 +38:14:20.0 17.0mag 63P/Wild
23:21:37.45 -12:09:08.0 15.7mag 65P/Gunn
03:48:02.58 +19:13:29.1 15.9mag 76P/West-Kohoutek-Ikemura
00:52:53.03 +07:05:22.9 14.4mag 78P/Gehrels
22:45:17.74 -11:05:32.0 14.6mag 88P/Howell
01:54:14.85 +19:04:40.5 15.1mag 93P/Lovas
04:44:07.49 +31:58:04.7 16.3mag 123P/West-Hartley
08:21:54.99 +41:01:27.5 16.2mag 124P/Mrkos
02:24:21.13 +13:43:13.4 16.4mag 128P/Shoemaker-Holt
02:36:15.23 +13:46:32.1 17.5mag 131P/Mueller
00:56:14.76 +11:09:41.3 10.9mag 141P/Machholz
01:05:52.81 +02:42:24.7 11.0mag 141P-A/Machholz
23:54:08.43 -01:08:09.2 13.5mag 141P-D/Machholz
01:35:35.96 +04:25:41.6 17.9mag 141P-I/Machholz
00:46:19.92 -04:24:55.7 15.2mag 162P/SidingSpring
10:29:50.36 +31:14:53.5 17.9mag 164P/Christensen
06:25:50.89 +24:25:12.4 17.9mag 198P/ODAS
15:01:39.96 -00:42:09.5 17.5mag 210P/Christensen
21:21:39.90 -12:50:36.2 17.5mag 218P/LINEAR
17:14:37.83 -14:36:54.3 16.2mag 235P/LINEAR
05:22:08.13 +34:13:46.6 16.7mag 240P/NEAT
07:35:49.56 -05:48:37.7 17.7mag 242P/Spahr
15:44:43.53 +06:35:53.7 17.5mag 391P/Kowalski
07:32:08.17 +21:20:25.6 17.6mag 450P/LONEOS
05:27:33.97 +45:22:16.6 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 10 00:38 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
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.55 -22:39:33.40 ASASSN-26cm 2026-04-4.3 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.70 -27:51:49.80 SN2026gvk 2026-03-30 15.48
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.80 -63:44:05.50 ASASSN-26ch 2026-03-27.86 13.02
11:23:19.04 +34:22:38.00 SN2026fwt 2026-03-27.3 16.56
19:03:49.79 +37:04:05.20 ASASSN-26ce 2026-03-26.56 16.3
20:26:56.07 -52:54:06.50 AT2026hiy 2026-03-26.35 16.95
05:25:54.76 -30:15:35.80 ASASSN-26cg 2026-03-25.07 16.88
06:57:16.49 -26:54:37.20 SN2026fzb 2026-03-25.14 15.8
14:37:38.23 -43:00:52.30 ASASSN-26cd 2026-03-24.24 12.52
17:34:53.03 +06:04:29.70 AT2026gzl 2026-03-23.27 15.82
08:30:02.60 -35:12:47.50 ASASSN-26cf 2026-03-23.2 14.82
16:54:25.33 +37:49:56.60 SN 2026evz 2026-03-21.32 17.54
17:06:19.20 -18:54:19.50 ASASSN-26bx 2026-03-21.25 16.39
19:01:16.28 -29:29:23.10 ASASSN-26bw 2026-03-21.33 15.81
08:46:05.75 +10:47:39.80 ASASSN-26ca 2026-03-21.13 14.27
12:14:58.16 +63:47:16.20 SN 2026fvx 2026-03-21.12 15.6
18:02:55.90 -75:23:02.60 ASASSN-26bz 2026-03-21.32 16.16
12:16:02.88 -53:16:33.80 ASASSN-26cc 2026-03-20.04 15.48
13:08:21.85 +29:13:44.20 SN 2026fmh 2026-03-20.16 -0.33
19:56:38.48 -34:45:21.50 ASASSN-26cb 2026-03-20.35 -3.26
14:32:41.15 -41:38:48.50 ASASSN-26by 2026-03-20.15 -1.31
13:00:42.99 +37:18:34.60 SN2026fjc 2026-03-19.5 15.97
06:02:44.21 -04:11:06.20 ASASSN-26bv 2026-03-19.19 15.67
12:20:27.96 -45:55:38.40 ASASSN-26bt 2026-03-18.8 16.32
07:49:57.30 -56:14:35.10 ASASSN-26bu 2026-03-19.19 15.74
06:04:29.75 +53:23:34.00 SN 2026eza 2026-03-18.2 17.48
11:54:57.87 +69:19:28.90 AT2026fsf 2026-03-18.14 16.95
10:44:46.95 +58:27:29.30 SN 2026enn 2026-03-18.13 17.53
20:45:54.04 -73:26:43.00 AT 2026ezy 2026-03-18.13 16.83
06:53:18.10 -59:10:49.30 ASASSN-26bs 2026-03-18.02 16.93
07:45:09.29 -62:14:36.20 ASASSN-26br 2026-03-16.16 16.78
19:24:27.93 -52:04:36.40 AT 2023uk 2026-03-16.35 14.2
04:52:54.50 -15:20:57.10 AT2026fhw 2026-03-14.06 SDSS
11:10:34.24 +02:58:48.10 SN2026drr 2026-03-14.08 0.2
07:26:45.73 -27:45:13.90 ASASSN-26bo 2026-03-14.17 13.8
16:35:46.94 +58:12:28.40 SN2026ebt 2026-03-12.41 17.12
13:01:19.46 +15:42:15.50 SN2026ehe 2026-03-12.34 -0.18
09:15:55.41 +10:08:09.70 SN2026efq 2026-03-12.16 0.06
03:31:20.92 -35:29:29.00 SN2026evh 2026-03-12.05 17.29
06:26:19.15 -85:18:28.10 AT2026ffp 2026-03-12.16 0.37
14:16:42.30 -41:18:36.50 AT2026fij 2026-03-12.05 15.97
10:45:04.71 +00:06:13.10 SN 2026exe 2026-03-11.78 16.48
18:07:45.58 +69:43:01.00 SN2026ess 2026-03-12.37 17.37
13:11:03.58 +49:06:31.80 AT2026ewa 2026-03-12.42 16.77
15:03:25.23 -63:11:22.20 ASASSN-26bp 2026-03-11.92 13.33
13:09:37.25 -35:50:25.20 AT2024cmo 2026-03-11.12 16.29
13:06:01.97 -15:50:14.40 AT2026fdy 2026-03-10.33 16.68
11:30:09.70 -47:26:45.00 ASASSN-26bn 2026-03-10.3 15.14
05:03:25.25 -24:16:50.40 (= Gaia 2026-03-9.09 14.32
03:42:32.53 -04:17:53.70 ASASSN-26bm 2026-03-8.04 15.22
04:31:00.53 -68:29:50.20 ASASSN-26bl 2026-03-7.9 10.26
16:18:17.61 +41:25:11.40 SN 2026dkf 2026-03-6.31 16.7
13:45:00.35 +61:16:50.90 SN 2026ejl 2026-03-6.41 -0.66
09:27:45.33 -37:49:33.00 ASASSN-26bk 2026-03-2.06 13.58
20:22:01.20 +23:47:47.30 ASASSN-26bi 2026-02-28.51 15.86
11:16:22.10 +29:26:22.80 AT2026enm 2026-02-28.39 16.88
08:05:59.83 -48:39:35.60 ASASSN-26bh 2026-02-26.05 14.64
13:24:27.02 -45:57:01.40 ASASSN-26bg 2026-02-26.35 15.28
17:27:50.95 -68:28:46.40 ASASSN-26bf 2026-02-26.3 16.28
18:03:39.29 +19:58:46.30 ASASSN-26be 2026-02-25.56 14.95
17:40:18.19 +07:20:59.60 SN 2026crm 2026-02-24.34 16.9
18:38:36.11 -79:28:58.40 ASASSN-26bb 2026-02-24.36 16.11
17:43:29.75 +11:24:00.60 ASASSN-26bc 2026-02-23.37 -3.37
16:59:41.08 -80:01:51.20 ASASSN-26bd 2026-02-23.3 14.38
11:23:31.77 -08:39:15.40 SN2026cff 2026-02-23.15 -1.08
14:55:17.39 -05:56:05.30 SN2026dmk 2026-02-23.22 -0.76
12:28:15.19 +44:27:20.80 SN2026cjz 2026-02-23.47 15.62
12:12:29.55 -02:40:43.30 AT2026dsk 2026-02-23.4 17.21
09:21:05.29 +06:11:42.80 SN2026chr 2026-02-23.1 17.39
16:05:38.61 +18:06:07.40 SN 2026dsy 2026-02-23.36 17.15
04:55:50.66 -29:52:57.70 SN 2026dpg 2026-02-23.11 15.75
04:21:28.18 -53:22:54.40 AT2026drl 2026-02-21.03 17.31
11:50:37.32 +55:21:13.70 SN 2026dix 2026-02-21.43 16.39
16:21:19.69 -63:47:29.40 ASASSN-26az 2026-02-21.03 17.02
02:45:30.93 -54:17:43.10 SN 2026cju 2026-02-21.04 17.54
01:58:40.68 +47:34:50.10 ASASSN-26av 2026-02-21.09 15.97
18:35:53.01 -42:31:38.90 ASASSN-26aw 2026-02-21.12 15.89
11:40:18.88 -39:45:09.20 ASASSN-26ax 2026-02-21.08 15.73
02:26:23.52 -51:42:29.80 ASASSN-26ay 2026-02-21.04 13.93
08:46:07.66 +01:17:43.90 ASASSN-26ba 2026-02-20.23 15.43
14:15:47.49 -48:05:16.60 SN2026dez 2026-02-19.31 15.91
17:25:53.90 -23:28:31.50 ASASSN-26au 2026-02-18.33 15.82
16:07:59.09 -24:00:10.00 SN2026cmv 2026-02-17.28 16.19
18:15:01.25 -37:43:36.70 ASASSN-26at 2026-02-16.36 15.94
13:01:07.22 -11:25:16.10 AT2026bzh 2026-02-12.16 17.22
10:56:29.81 -07:07:25.30 SN 2026bre 2026-02-12.16 17.15
08:55:43.51 -53:26:11.50 ASASSN-26as 2026-02-12.2 16.54
06:33:50.98 -41:46:25.10 ASASSN-26ar 2026-02-12.04 16.42
12:15:22.43 +23:59:39.60 SN2026bzg 2026-02-11.27 16.32
08:01:10.95 -03:43:14.30 AT2026coj 2026-02-9.25 13.73
12:44:00.18 -57:03:46.80 ASASSN-26aq 2026-02-9.18 16
-rw-r--r-- 1 apache apache 5.8K Apr 10 00:38 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
06:57:11.19 -17:24:43.9 TCP J06571119-1724439 2026-01-18.5375 14.2mag
00:42:52.23 +41:01:44.7 PNV J00425223+4101447 2026-01-19.5505 18.74Cmag
09:54:46.47 +69:06:31.7 PNV J09544647+6906317 2026-01-26.8081 19.3mag
18:08:51.99 -26:16:21.9 TCP J18085199-2616219 2026-01-31.8519 12.2mag
08:01:11.02 -03:43:14.1 TCP J08011102-0343141 2026-02-08.8090 15.10Cmag
05:19:15.40 -02:04:51.5 TCP J05191540-0204515 2026-02-13.4306 14.5mag
10:52:41.26 +36:40:08.9 TCP J10524126+3640089 2026-02-17.6065 17.4mag
05:50:50.81 +36:22:45.1 TCP J05505081+3622451 2026-02-17.5511 15.7mag
00:42:51.33 +41:13:49.1 PNV J00425133+4113491 2026-02-20.738 18.3mag
00:43:04.88 +41:29:41.4 PNV J00430488+4129414 2026-02-20.5923 18.84Cmag
17:43:29.74 +11:24:00.3 TCP J17432974+1124003 2026-02-22.3773 13.6mag
09:55:01.59 +69:08:42.7 PNV J09550159+6908427 2026-02-20.893 19.0mag
07:03:25.76 -12:41:40.1 TCP J07032576-1241401 2026-03-10.4268 15.4mag
00:42:36.82 +41:16:05.8 PNV J00423682+4116058 2026-03-12.5744 17.24Cmag
07:26:45.79 -27:45:14.1 TCP J07264579-2745141 2026-03-17.4417 14.8mag
17:57:19.56 -28:08:14.7 TCP J17571956-2808147 2026-03-19.7972 14.5mag
08:46:05.73 +10:47:39.7 TCP J08460573+1047397 2026-03-21.1936 14.5mag
09:55:38.83 +69:05:21.7 PNV J09553883+6905217 2026-04-01.893 19.4mag
19:32:43.67 -22:39:30.7 TCP J19324367-2239307 2026-04-05.4395 13.6mag
16:16:36.03 +44:52:28.9 TCP J16163603+4452289 2026-04-05.6655 14.2mag
-rw-r--r-- 1 apache apache 187K Apr 10 00:38 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
09:24:18.822 -19:21:24.31 AT 2026ikf 2026-03-25.57 19.79
08:18:48.927 -23:32:12.08 AT 2026ike 2026-02-12.51 20.2
08:47:41.490 -21:46:40.10 AT 2026ikd 2026-03-28.41 19.49
08:34:30.248 -07:09:24.85 AT 2026ikc 2026-03-29.44 19.28
13:21:25.078 +79:09:18.53 AT 2026ikb 2026-03-25.43 20.7322
09:05:18.124 -19:48:21.41 AT 2026ika 2026-03-09.36 20.58
08:38:25.468 +06:11:03.79 AT 2026ijz 2026-03-09.32 21.99
08:00:34.010 +04:48:18.04 AT 2026ijy 2026-03-09.31 21.07
09:02:07.082 +07:27:03.87 AT 2026ijx 2026-02-17.43 21.29
10:37:20.784 +30:59:50.95 AT 2026ijw 2026-03-10.33 20.2
16:00:37.915 +06:38:30.61 AT 2026ijv 2026-03-28.57 20.5
13:51:30.137 +25:53:04.17 AT 2026iju 2026-03-28.41 20.07
12:52:01.341 -19:06:48.80 AT 2026ijt 2026-01-28.59 20.22
11:38:25.995 -11:34:40.48 AT 2026ijs 2026-01-16.56 21.1
07:12:41.661 +56:25:20.59 AT 2026ijr 2026-01-19.40 20.76
09:34:48.813 +06:57:40.76 AT 2026ijq 2026-01-26.43 21.57
10:49:59.384 +25:17:19.22 AT 2026ijp 2026-04-04.17 19.836
08:20:22.449 +03:44:22.06 AT 2026ijo 2026-04-02.18 19.8276
06:41:34.987 -19:08:36.17 AT 2026ijn 2026-02-05.26 20.38
12:35:13.975 +41:45:24.96 AT 2026ijm 2026-04-02.31 19.9925
-rw-r--r-- 1 apache apache 30K Apr 10 00:38 tns_transients_list.txt
