This analysis is done by the script util/transients/transient_factory_test31.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj
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,2461144.7013,10.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 10.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
GSC 02923-00800,2461144.7013,11.69,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
GSC 02923-00800 20260414.2013 11.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,2461144.7013,12.18,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
ATO J091.2816+42.7504,2461144.7013,12.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J091.2816+42.7504 20260414.2013 12.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.95,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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 J084.1854+41.8376,2461144.7013,12.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J084.1854+41.8376 20260414.2013 12.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
target,2461144.7013,12.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.35CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.36,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
target,2461144.7013,12.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 J097.0268+42.0348,2461144.7013,12.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J097.0268+42.0348 20260414.2013 12.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
ATO J084.5507+42.2070,2461144.7013,11.98,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J084.5507+42.2070 20260414.2013 11.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,2461144.7013,11.61,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.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
ATO J093.6704+42.5182,2461144.7013,11.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J093.6704+42.5182 20260414.2013 11.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,10.31,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 10.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461144.7013,11.11,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.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,2461144.7013,11.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.24CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 962075320005515008,2461144.7013,11.88,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 962075320005515008 20260414.2013 11.88CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,11.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.16,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.16CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
ATO J085.1588+48.3266,2461144.7013,12.24,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J085.1588+48.3266 20260414.2013 12.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
target,2461144.7013,12.20,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
ATO J094.1932+45.9045,2461144.7013,12.40,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J094.1932+45.9045 20260414.2013 12.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
Gaia DR3 960875757115766912,2461144.7013,12.32,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 960875757115766912 20260414.2013 12.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,2461144.7013,12.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 193368709093396096,2461144.7013,12.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 193368709093396096 20260414.2013 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.51,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.34,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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+46.0835,2461144.7013,12.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J086.8172+46.0835 20260414.2013 12.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
Gaia DR3 214492114168676864,2461144.7013,12.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 214492114168676864 20260414.2013 12.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 J088.9076+42.5566,2461144.7013,12.57,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J088.9076+42.5566 20260414.2013 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461144.7013,12.54,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.64,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.55,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.55CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.66,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.66CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.76,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.76CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 J085.7848+44.8738,2461144.7013,12.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J085.7848+44.8738 20260414.2013 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
ATO J089.5119+42.9112,2461144.7013,12.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J089.5119+42.9112 20260414.2013 12.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,2461144.7013,12.63,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.94,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.73,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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!
Don't forget to change the observer code for the AAVSO and VSNET format data!
**** AAVSO file format ****
#TYPE=EXTENDED
#OBSCODE=SKA
#SOFTWARE=VaST 1.0rc90 transient pipeline
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
target,2461144.7013,12.97,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.97CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.86,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.72,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
Gaia DR3 196214451344445952,2461144.7013,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 196214451344445952 20260414.2013 12.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,2461144.7013,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.89,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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
target,2461144.7013,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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,2461144.7013,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.79,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.79CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.91,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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
Gaia DR3 196214451344445952,2461144.7013,12.65,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 196214451344445952 20260414.2013 12.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,2461144.7013,12.96,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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,2461144.7013,12.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.92,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.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,2461144.7013,12.77,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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,2461144.7013,13.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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
ATO J091.9633+41.8659,2461144.7013,13.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J091.9633+41.8659 20260414.2013 13.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.01,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 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
ATO J085.9730+47.7186,2461144.7013,12.99,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J085.9730+47.7186 20260414.2013 12.99CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.13,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.13CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.05,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.05CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.21,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.21CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.15,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.15CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.38,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.38CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.26,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.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,2461144.7013,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 J092.8507+44.7430,2461144.7013,13.59,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ATO J092.8507+44.7430 20260414.2013 13.59CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.48,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.48CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,13.46,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 13.46CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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
CGCS 6107,2461144.7013,12.82,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
CGCS 6107 20260414.2013 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,2461144.7013,12.43,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.43CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 4452455,2461144.7013,12.39,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
NSVS 4452455 20260414.2013 12.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
Gaia DR3 963406759866040448,2461144.7013,11.35,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
Gaia DR3 963406759866040448 20260414.2013 11.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,2461144.7013,11.23,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 11.23CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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,2461144.7013,12.07,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
target 20260414.2013 12.07CV NMW
The AAVSO data should be submitted to https://www.aavso.org/webobs
The VSNET data, depending on how interesting the target is, should be e-mailed to
vsnet-alert@ooruri.kusastro.kyoto-u.ac.jp
vsnet-outburst-wanted@ooruri.kusastro.kyoto-u.ac.jp
vsnet-obs@ooruri.kusastro.kyoto-u.ac.jp
# Time-series data may be sent to vsnet-campaign-report@ooruri.kusastro.kyoto-u.ac.jp
Don't forget to copy the leading white spaces and change the observatory code!
The code 'C32' is 'Ka-Dar Observatory, TAU Station, Nizhny Arkhyz', the code '500' is the geocenter.
Make sure there are no trailing white spaces after the observatory code.
The string should be exactly 80 characters long to conform to the MPC format.
Mean position:
You may copy/paste the above measurements to the following online services: MPChecker (in case the button does not work) NEOCMTChecker (NEO's and comets) sat_id2 (artificial satellites; needs at least two observations to work) fitsblink_satellites (art. sat.; you'll need to save the astrometry as a text file and upload it)
Here is a stub line for reporting 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 J054825.45+461817.6,2461144.7013,11.30,0.05,CV,NO,STD,ENSEMBLE,na,na,na,na,1,na,NMW-TexasTech Camera-2 135mm f/2.2 telephoto lens + QHY600M CMOS
**** VSNET file format ****
# Here are some valid formatiing examples:
#CETFZ 20230815.9829 <13.5CV NMW
#CETFZ 20230818.9746 12.5CV NMW
#CETFZ 20230819.9732 12.6CV NMW
#TCPJ17453768-1756253 20230831.7290 12.7CV NMW
ASASSN-V J054825.45+461817.6 20260414.2013 11.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
## VaST run with SExtractor config file default.sex.telephoto_lens_onlybrightstars_v1 ##
Images processed 4
Images used for photometry 4
Ref. image: 2461061.71554414 21.01.2026 05:10:13.014 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
First image: 2461061.71554414 21.01.2026 05:10:13.014 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Last image: 2461144.70159381 14.04.2026 04:50:07.705 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 7
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.64
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: 5 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): 16254
Objects passed selection criteria: 16217
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: 14035
Average stars matched: 13687.8 (97.5258 %)
Memory usage VmPeak: 122832 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sun Apr 12 15:05:06 CDT 2026
VaST build number 1.0rc89-12-g393f88de
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-12)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Mon Apr 13 23:52:17 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: 2461061.71554414 21.01.2026 05:10:13.014 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
First image: 2461061.71554414 21.01.2026 05:10:13.014 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Last image: 2461144.70159381 14.04.2026 04:50:07.705 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
JD time system (TT/UTC/UNKNOWN): UTC
Transient candidates found: 147
FILTER key from ref. img. header: CV
Magnitude scale: instrumental
Estimated ref. image limiting mag.: -7.30
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: 53 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): 120875
Objects passed selection criteria: 120600
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: 104664
Average stars matched: 101285 (96.7713 %)
Memory usage VmPeak: 1960408 kB
Software: VaST 1.0rc90 compiled with gcc (Gentoo 15.2.1_p20260214 p5) 15.2.1 20260214
VaST compiled on Sun Apr 12 15:05:06 CDT 2026
VaST build number 1.0rc89-12-g393f88de
OpenMP enabled: Yes
SExtractor version 2.19.5 (2026-04-12)
GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
Processing completed on Tue Apr 14 00:04:13 CDT 2026
Host name: tau
############################################################
Updating neverexclude_list.txt
'/var/www/nmw_calibration/neverexclude_list.txt' -> './neverexclude_list.txt'
Choosing bad regions list
'/var/www/nmw_calibration/TTUQ2b1x1/TTUQ2_bad_region.lst' -> 'bad_region.lst'
wait
*------ default.sex.telephoto_lens_onlybrightstars_v1 ------*
'default.sex.telephoto_lens_onlybrightstars_v1' -> 'default.sex'
Starting VaST with default.sex.telephoto_lens_onlybrightstars_v1
./vast --norotation --noflagimage --starmatchraius 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
SExtractor catalog cache: saved Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat to cache
SExtractor catalog cache: saved Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.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/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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: 2461144.70103343
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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits exists and is non-empty
Saving wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits to local_wcs_cache/
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits' -> 'local_wcs_cache/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits'
wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits exists and is non-empty
Saving wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits to local_wcs_cache/
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits' -> 'local_wcs_cache/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits'
wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits exists and is non-empty
Saving wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits to local_wcs_cache/
'wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits' -> 'local_wcs_cache/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits'
wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits exists and is non-empty
Saving wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits to local_wcs_cache/
'wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits' -> 'local_wcs_cache/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits'
The image scale is 5.86"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.8"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 05:59:47.823 +46:00:35.63
Second-epoch image center 05:59:44.410 +46:01:28.09
Angular distance between the image centers 0.0176 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 05:59:47.823 +46:00:35.63
Second-epoch image center 05:59:44.682 +46:01:23.29
Angular distance between the image centers 0.0161 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 05:59:44.410 +46:01:28.09
Second-epoch second image center 05:59:44.682 +46:01:23.29
Angular distance between the image centers 0.00155 deg.
###################################
ERROR: no shift applied between second-epoch images! The distance between image centers is 0.00155 deg. (min. required shift: 0.00164 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/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits &> /tmp/tmp.MG2ktGKo7y
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits &> /tmp/tmp.I8dSOk6jmG
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits &> /tmp/tmp.20cAbOfL2D
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits &> /tmp/tmp.PgEJsl3LXU
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Calibrating the magnitude scale
Found non-empty wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
Found non-empty wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
The reference image (wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits) and catalog (wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat) found
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat' -> 'wcsmag.cat'
Read 24266 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 77.9190 to 102.4864 deg, Dec +39.9773 to +51.3461 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 77.9190 to 102.4864 deg, Dec 39.9773 to 51.3461 deg
Loaded 11816 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): 86 out of 101 total matches.
Matched with Tycho-2 101 out of 24266 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 23.040760
a=0.000000 b=1.000000 c=23.040760
From vast_summary.log: estimated ref. image limiting mag.: -7.64
Updating vast_summary.log: Estimated ref. image limiting mag.: 15.40
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 15.40
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 4 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.1 pix Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
2.2 pix Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
2.5 pix fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
2.5 pix fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Limiting magnitude estimates:
15.4 mag. Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
15.4 mag. Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
14.8 mag. fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
14.8 mag. fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
All-image limiting magnitude estimate: 14.8 (SNR ) 12.0 (80% of stars) with default.sex.telephoto_lens_onlybrightstars_v1
The first estimate is the magnitude of a star detected with a signal-to-noise ratio of following Karpov (2025, Acta Polytechnica, 65, 50).
This value should be representative of the faintest stars clearly visible in the image.
The brighter of the limiting magnitude estimates for the two second-epoch images is reported here.
The second estimate is the 80th percentile of the magnitude distribution of stars detected on all four images.
This value is representative of the faintest object that may enter the candidate transients list.
The hard cut-off for the candidate transients is 15.0 mag.
Waiting for UCAC5 plate solver
wait
############ /tmp/tmp.MG2ktGKo7y (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits' -> 'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS_IMAGE_NAME=wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS-calibrated image found: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Checking if the catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits alredy exist and is non-empty...
Catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS catalog name: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2260, passed=24266
Got 24266 stars (including 21982 good ones) from the SExtractor catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
util/solve_plate_with_UCAC5 got 24266 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 935.1'
Seting catalog search parameters based on the expected field of view 935.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012988 (46.8 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010390 (37.4 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 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 417 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 363 matched stars entering correct_measured_positions(), 321 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.91"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 354 matched stars entering correct_measured_positions(), 9707 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.36"
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 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 453 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 406 matched stars entering correct_measured_positions(), 9733 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 5.27"
Accuracy estimation diagnostic: 405 matched stars entering correct_measured_positions(), 10903 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 3.47"
Excluding outliers - 405 stars left (next iteration limit 389)
The image catalog is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits -region wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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.I8dSOk6jmG (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits' -> 'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS_IMAGE_NAME=wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS-calibrated image found: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Checking if the catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits alredy exist and is non-empty...
Catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS catalog name: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=2222, passed=24282
Got 24282 stars (including 22031 good ones) from the SExtractor catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat
util/solve_plate_with_UCAC5 got 24282 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 935 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 906 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 23378 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
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 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 935 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 23377 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.36"
Accuracy estimation diagnostic: 934 matched stars entering correct_measured_positions(), 23377 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.38"
Excluding outliers - 934 stars left (next iteration limit 1027)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits -region wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.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.20cAbOfL2D (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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS_IMAGE_NAME=wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS-calibrated image found: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Checking if the catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits alredy exist and is non-empty...
Catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS catalog name: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=841, passed=14524
Got 14524 stars (including 13676 good ones) from the SExtractor catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat
util/solve_plate_with_UCAC5 got 14524 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.4'
Seting catalog search parameters based on the expected field of view 923.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012825 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010260 (36.9 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 651 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 231 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 184 matched stars entering correct_measured_positions(), 119 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.45"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 182 matched stars entering correct_measured_positions(), 2656 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.25"
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 651 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 266 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 224 matched stars entering correct_measured_positions(), 2677 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.14"
Accuracy estimation diagnostic: 222 matched stars entering correct_measured_positions(), 3375 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.35"
Excluding outliers - 222 stars left (next iteration limit 200)
The image catalog is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits -region wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.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.PgEJsl3LXU (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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS_IMAGE_NAME=wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS-calibrated image found: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Checking if the catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits alredy exist and is non-empty...
Catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS catalog name: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=0, blended=806, passed=14404
Got 14404 stars (including 13591 good ones) from the SExtractor catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat
util/solve_plate_with_UCAC5 got 14404 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.3'
Seting catalog search parameters based on the expected field of view 923.3 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012824 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010259 (36.9 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 651 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 237 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 185 matched stars entering correct_measured_positions(), 124 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.89"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 182 matched stars entering correct_measured_positions(), 2602 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.72"
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 651 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 270 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 229 matched stars entering correct_measured_positions(), 2624 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 9.49"
Accuracy estimation diagnostic: 228 matched stars entering correct_measured_positions(), 3401 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.32"
Excluding outliers - 228 stars left (next iteration limit 200)
The image catalog is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits -region wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits'
Saving fully-calibrated image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits'
Saving fully-calibrated image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits'
Saving fully-calibrated image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
INFO: FPACK_FULLY_CALIBRATED_IMAGE=no (not compressing the image)
'wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits' -> '/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits'
Preparing the HTML report for the field Aur-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
Adding exclusion_list_local.txt__out31129.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31243.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out31333.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 14s
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: 3s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31129_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 31129_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31165_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 31165_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
**** FOUND 05:59:28.45 +45:00:45.7 in the exclusion list exclusion_list_bbsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31243_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 31243_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 31333_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 31333_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
make_report_in_HTML.sh Phase 2 (HTML assembly): 0s
make_report_in_HTML.sh TOTAL: 17s
Prepared the HTML report for the field Aur-02-Q2b1x1 with default.sex.telephoto_lens_onlybrightstars_v1
*------ done with default.sex.telephoto_lens_onlybrightstars_v1 ------*
#### The local exclusion list is exclusion_list_local.txt ####
06:14:20.67 +46:48:18.8
05:45:41.68 +43:39:24.4
05:57:10.47 +48:21:36.3
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 4 --matchstarnumber 500 --selectbestaperture --sysrem 0 --type 4 --maxsextractorflag 99 --UTC --nofind --nojdkeyword /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
SExtractor catalog cache: saved Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat to cache
SExtractor catalog cache: saved Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat to cache
VaST run complete with default.sex.telephoto_lens_vSTL
The four input images were /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Checking WCS cache directory local_wcs_cache
Found WCS cache directory local_wcs_cache
Creating symlink local_wcs_cache/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Creating symlink local_wcs_cache/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Creating symlink local_wcs_cache/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Creating symlink local_wcs_cache/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits exists and is non-empty
wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits exists and is non-empty
wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits exists and is non-empty
wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits exists and is non-empty
The image scale is 5.86"/pix, setting the soft and hard astrometric limits for filtering second-epoch detections: 5.9" and 8.8"
###################################
# Check the image center offset between the reference and the first second-epoch image (pointing accuracy)
Reference image center 05:59:47.823 +46:00:35.63
Second-epoch image center 05:59:44.410 +46:01:28.09
Angular distance between the image centers 0.0176 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 05:59:47.823 +46:00:35.63
Second-epoch image center 05:59:44.682 +46:01:23.29
Angular distance between the image centers 0.0161 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 05:59:44.410 +46:01:28.09
Second-epoch second image center 05:59:44.682 +46:01:23.29
Angular distance between the image centers 0.00155 deg.
###################################
ERROR: no shift applied between second-epoch images! The distance between image centers is 0.00155 deg. (min. required shift: 0.00164 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/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits &> /tmp/tmp.XBQRHYTBXB
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits &> /tmp/tmp.AOCFeXnaqr
Parallel run for /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits &> /tmp/tmp.43eWfpH3EN
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Running util/solve_plate_with_UCAC5 --no_photometric_catalog --iterations 2 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits &> /tmp/tmp.W1iwszm4Jr
Parallel run for /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Calibrating the magnitude scale
Found non-empty wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
Found non-empty wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits and wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
The reference image (wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits) and catalog (wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat) found
'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat' -> 'wcsmag.cat'
Read 170851 stars from the SExtractor catalog wcsmag.cat
Detected star coordinate range: RA 77.8948 to 102.5178 deg, Dec +39.9772 to +51.3479 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 77.8948 to 102.5178 deg, Dec 39.9772 to 51.3479 deg
Loaded 11844 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): 101 out of 140 total matches.
Matched with Tycho-2 140 out of 170851 detected stars.
The calibration function type and coefficients are written to calib.txt_param
util/calibrate_magnitude_scale 0.000000 1.000000 21.801794
a=0.000000 b=1.000000 c=21.801794
From vast_summary.log: estimated ref. image limiting mag.: -7.30
Updating vast_summary.log: Estimated ref. image limiting mag.: 14.50
Updated vast_limiting_magnitude.log with calibrated magnitudes
Working...
Please, PLEASE, be patient!!!
All lightcurves processed! =)
Estimated ref. image limiting mag.: 14.50
Magnitude calibration plot:
____ End of magnitude calibration ____
Applying consolidated magnitude filters...
Preparing the exclusion lists for this field
Done with filtering
Found 119 candidate transients before the final filtering. (Hard limit: 3000)
Median FWHM seeing for isolated stars:
2.0 pix Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
2.0 pix Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
2.4 pix fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
2.4 pix fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Limiting magnitude estimates:
14.5 mag. Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
14.5 mag. Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
13.8 mag. fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
13.8 mag. fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
All-image limiting magnitude estimate: 13.8 (SNR ) 13.2 (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.XBQRHYTBXB (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits' -> 'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS_IMAGE_NAME=wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS-calibrated image found: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Checking if the catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits alredy exist and is non-empty...
Catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
WCS catalog name: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=46, blended=20120, passed=170805
Got 170805 stars (including 150422 good ones) from the SExtractor catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat
util/solve_plate_with_UCAC5 got 170805 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 935.1'
Seting catalog search parameters based on the expected field of view 935.1 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012988 (46.8 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010390 (37.4 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 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 406 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 356 matched stars entering correct_measured_positions(), 310 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.13"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 352 matched stars entering correct_measured_positions(), 60456 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.06"
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 649 to 708 (Dec 40.0 to 51.3)
Done reading UCAC5 zone files...
Matched 442 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 410 matched stars entering correct_measured_positions(), 60493 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 6.05"
Accuracy estimation diagnostic: 409 matched stars entering correct_measured_positions(), 73193 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 4.14"
Excluding outliers - 409 stars left (next iteration limit 387)
The image catalog is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits -region wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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.AOCFeXnaqr (6) ############
Parsing command line arguments...
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits is already a symlink and we do not allow symlinks on symlinks
The guess is based on the existing WCS header.
Trying to blindly solve the plate (local solve-field or remote server)...
/data_ssd/NMW-TexasTech/workdir/vast_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits 569.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WARNING from replace_file_with_symlink_if_filename_contains_white_spaces() the input file /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits is already a symlink and we do not allow symlinks on symlinks
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
verification OK: /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
It's a known telescope with plate solutions that are supposed to be good.
The input image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits has a WCS header - will blindly trust it is good...
'/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits' -> 'wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits'
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS_IMAGE_NAME=wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS-calibrated image found: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Checking if the catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits alredy exist and is non-empty...
Catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat corresponding to the image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
WCS catalog name: wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=44, blended=20075, passed=170060
Got 170060 stars (including 149712 good ones) from the SExtractor catalog wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat
util/solve_plate_with_UCAC5 got 170060 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 941.5'
Seting catalog search parameters based on the expected field of view 941.5 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.013076 (47.1 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010461 (37.7 arcsec)
ITERATION 01 -- talking to VizieR, this might be slow!
UCAC5 search strategy: trying local copy first
Found a local copy of UCAC5
Reading UCAC5 zone files...
Searching UCAC5 zones 649 to 708 (Dec 40.0 to 51.4)
Done reading UCAC5 zone files...
Matched 947 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 947 matched stars entering correct_measured_positions(), 927 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 947 matched stars entering correct_measured_positions(), 166998 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.38"
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 649 to 708 (Dec 40.0 to 51.4)
Done reading UCAC5 zone files...
Matched 947 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 947 matched stars entering correct_measured_positions(), 166995 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.38"
Accuracy estimation diagnostic: 947 matched stars entering correct_measured_positions(), 166995 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 0.39"
Excluding outliers - 947 stars left (next iteration limit 1041)
Stop iterations.
The field is successfully solved and matched with the astrometric catalog! :)
The image catalog is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/reference_imgs/Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits -region wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.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.43eWfpH3EN (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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS_IMAGE_NAME=wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS-calibrated image found: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Checking if the catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits alredy exist and is non-empty...
Catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
WCS catalog name: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=10, blended=8875, passed=95772
Got 95772 stars (including 86805 good ones) from the SExtractor catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat
util/solve_plate_with_UCAC5 got 95772 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.4'
Seting catalog search parameters based on the expected field of view 923.4 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012825 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010260 (36.9 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 650 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 218 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 171 matched stars entering correct_measured_positions(), 103 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.85"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 168 matched stars entering correct_measured_positions(), 12888 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.05"
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 650 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 255 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 214 matched stars entering correct_measured_positions(), 12908 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.01"
Accuracy estimation diagnostic: 213 matched stars entering correct_measured_positions(), 18761 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 7.96"
Excluding outliers - 213 stars left (next iteration limit 184)
The image catalog is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits -region wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.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.W1iwszm4Jr (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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/util/wcs_image_calibration.sh /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits 605.0
Entering WCS image calibration mode.
ORIGINAL_FITSFILE=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
FITSFILE before on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
FITSFILE after on_the_fly=/data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
verification OK: /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS_IMAGE_NAME=wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS-calibrated image found: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Checking if the catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits alredy exist and is non-empty...
Catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat corresponding to the image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits found.
The catalog is in the new format, as expected.
The plate-solved (WCS-calibrated) image is saved to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
util/solve_plate_with_UCAC5 is preparing to read a catalog corresponding to the image /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
WCS catalog name: wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat
SExtractor catalog parsing summary: zero_flux=0, no_flux_err=0, no_mag=0, no_mag_err=0, low_SNR=13, blended=8292, passed=93333
Got 93333 stars (including 84950 good ones) from the SExtractor catalog wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat
util/solve_plate_with_UCAC5 got 93333 stars from the SExtractor catalog
Updated FoV from the plate-solved image: 923.3'
Seting catalog search parameters based on the expected field of view 923.3 arcmin
UCAC5 catalog search parameters:
catalog_search_parameters->search_radius_deg= 0.012824 (46.2 arcsec)
catalog_search_parameters->brightest_mag= 1.00
catalog_search_parameters->faintest_mag= 13.50
catalog_search_parameters->search_radius_second_step_deg 0.010259 (36.9 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 650 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 217 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 170 matched stars entering correct_measured_positions(), 106 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 11.03"
Removing outliers...
Correcting the measured astrometric positions...
Accuracy estimation diagnostic: 168 matched stars entering correct_measured_positions(), 12440 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.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 650 to 708 (Dec 40.2 to 51.2)
Done reading UCAC5 zone files...
Matched 257 stars with the local copy of UCAC5.
The local UCAC5 search seems to be a success
Accuracy estimation diagnostic: 214 matched stars entering correct_measured_positions(), 12461 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 10.33"
Accuracy estimation diagnostic: 212 matched stars entering correct_measured_positions(), 18144 with non-zero local correction accuracy
Estimated accuracy of the plate solution: 8.63"
Excluding outliers - 212 stars left (next iteration limit 184)
The image catalog is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ucac5
The DS9 region file with the matched stars is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ds9.reg
You may view it with the command:
ds9 /data_ssd/NMW-TexasTech/workdir//img_2026-04-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits -region wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits.cat.ds9.reg
The astrometric residuals vector field is written to wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-13_20.00sec_-14.90C_LIGHT_0227.fits
Saving fully-calibrated image wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_Aur-02-Q2b1x1_2026-01-20_23-10-59_20.00sec_-15.00C_LIGHT_0228.fits
Saving fully-calibrated image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-49-19_20.00sec_-5.00C_LIGHT_0771.fits
Saving fully-calibrated image wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.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-13_CI_Aur-02-Q2b1x1_235057_TTUQ2b1x1_23756_qBJEHoIj/wcs_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772.fits
Preparing the HTML report for the field Aur-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
Adding exclusion_list_local.txt__out181899.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192126.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192128.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192133.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192140.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192148.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192152.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192154.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192155.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192157.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192159.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192161.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192164.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192166.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192170.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192441.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192462.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192779.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192792.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192845.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192911.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192916.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192948.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out192968.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193009.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193010.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193044.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193060.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193073.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193075.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193076.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193078.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193155.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193167.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193184.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193232.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193233.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193234.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193249.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193262.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193279.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193330.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193332.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193344.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193352.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193360.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193362.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193371.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193399.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193405.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193419.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193467.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193473.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193492.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193501.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193510.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193533.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193536.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193545.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193556.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193569.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193574.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193575.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193609.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193621.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193664.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193687.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193756.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193764.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193793.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193801.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193838.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193867.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193875.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out193906.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194015.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194017.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194024.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194032.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out194041.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out41230.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out47690.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out52500.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out68332.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out69975.dat to exclusion_list_local.txt
Adding exclusion_list_local.txt__out75263.dat to exclusion_list_local.txt
make_report_in_HTML.sh Phase 1 (network queries): 121s
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: 61s
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192119_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192119_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (14.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192124_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192124_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (13.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192126_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192126_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192128_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192128_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192133_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192133_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192140_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192140_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192148_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192148_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192151_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192151_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192152_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192152_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192154_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192154_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192155_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192155_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192157_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192157_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192159_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192159_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192161_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192161_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192164_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192164_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192166_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192166_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192170_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192170_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192378_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192378_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
**** FOUND 05:45:41.49 +43:39:21.5 in the exclusion list exclusion_list_local.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192441_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192441_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192457_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192457_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192462_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192462_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192542_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192542_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192606_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192606_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (16.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192779_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192779_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192792_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192792_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192845_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192845_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192911_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192911_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192916_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192916_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192948_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192948_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192949_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192949_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
**** FOUND 05:56:54.60 +49:01:29.2 in the exclusion list exclusion_list_bsc.txt ****
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192968_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 192968_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 192994_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 192994_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.5") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193009_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193009_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193010_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193010_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193043_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193043_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193044_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193044_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193060_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193060_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193073_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193073_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193075_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193075_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193076_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193076_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193078_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193078_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193096_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193096_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (11.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193139_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193139_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (17.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193155_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193155_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193167_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193167_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193180_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193180_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193184_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193184_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193232_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193232_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193233_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193233_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193234_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193234_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193249_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193249_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193262_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193262_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193279_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193279_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193330_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193330_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193332_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193332_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193334_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193334_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (14.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193344_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193344_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193352_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193352_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193360_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193360_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193362_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193362_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193371_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193371_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193377_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193377_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193379_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193379_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (31.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193387_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193387_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (11.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193399_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193399_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193405_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193405_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193419_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193419_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193437_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193437_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193462_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193462_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (11.6") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193467_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193467_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193473_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193473_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193483_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193483_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193486_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193486_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (10.3") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193492_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193492_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193501_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193501_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193510_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193510_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193533_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193533_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193536_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193536_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193545_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193545_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193556_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193556_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193569_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193569_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193574_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193574_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193575_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193575_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193609_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193609_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193621_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193621_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193628_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193628_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (20.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193636_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193636_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (9.0") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193664_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193664_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193687_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193687_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193756_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193756_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193762_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193762_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193764_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193764_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193769_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193769_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (18.2") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193778_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193778_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (18.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193793_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193793_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193801_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193801_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193838_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193838_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193844_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193844_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (10.1") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193867_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193867_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193875_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193875_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193906_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 193906_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 193943_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 193943_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (10.4") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194015_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 194015_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194017_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 194017_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194024_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 194024_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194032_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 194032_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 194041_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 194041_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 69975_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 69975_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 182292_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 182292_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate as there is no shift in pixel position (shift 0.0 pix) between the two second-epoch detections and REQUIRE_PIX_SHIFT_BETWEEN_IMAGES_FOR_TRANSIENT_CANDIDATES is set to 'yes'
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 52500_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 52500_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 47690_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 47690_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 68332_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 68332_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 41230_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 41230_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 57196_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 57196_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (14.9") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 181899_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 181899_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 102378_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 102378_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (21.7") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 75263_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
Preparing report for the candidate 75263_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 63136_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 63136_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (13.8") between the two second-epoch detections
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Considering the candidate 39411_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772
The candidate 39411_fd_Aur-02-Q2b1x1_2026-04-13_23-50-07_20.00sec_-4.90C_LIGHT_0772 did not pass the final checks
Rejecting candidate due to large distance (19.0") between the two second-epoch detections
make_report_in_HTML.sh Phase 2 (HTML assembly): 4s
make_report_in_HTML.sh TOTAL: 186s
Prepared the HTML report for the field Aur-02-Q2b1x1 with default.sex.telephoto_lens_vSTL
*------ done with default.sex.telephoto_lens_vSTL ------*
#### The local exclusion list is exclusion_list_local.txt ####
06:14:20.67 +46:48:18.8
05:45:41.68 +43:39:24.4
05:57:10.47 +48:21:36.3
05:33:54.71 +46:42:34.3
05:52:14.37 +42:53:07.0
06:05:03.62 +42:45:04.0
06:05:15.74 +42:45:22.3
06:10:31.36 +44:45:11.2
05:36:46.90 +41:50:37.2
05:42:00.34 +46:28:19.2
06:16:33.70 +42:03:05.9
06:15:54.57 +44:36:21.0
06:16:01.97 +44:45:53.6
06:28:09.71 +42:02:23.7
05:38:09.42 +42:12:53.0
05:38:09.46 +41:40:53.8
06:14:39.76 +42:30:55.2
05:36:50.81 +41:58:44.2
06:11:00.97 +48:42:54.0
06:30:09.69 +46:03:54.7
06:13:09.90 +44:46:22.7
06:35:29.64 +44:48:38.1
06:05:26.24 +44:41:50.7
06:25:20.73 +42:06:38.7
06:23:55.12 +43:37:32.8
06:02:53.95 +43:00:18.5
06:11:35.31 +50:11:55.2
05:40:40.82 +48:19:53.5
05:48:55.74 +49:48:13.6
06:16:45.02 +45:53:52.9
06:03:02.72 +42:44:13.6
06:10:28.21 +47:28:45.9
05:59:38.33 +44:02:50.9
06:00:45.58 +49:57:44.2
05:57:32.41 +45:54:03.3
06:11:15.59 +45:05:30.2
05:47:14.83 +46:04:42.8
05:47:39.23 +50:01:19.6
05:55:37.25 +42:34:04.3
05:44:44.91 +48:57:11.4
05:51:54.53 +49:31:09.2
05:42:29.87 +44:45:51.9
06:07:34.33 +46:41:15.5
05:56:18.51 +46:15:14.4
06:24:57.20 +43:11:54.7
05:43:05.71 +44:52:29.7
05:57:59.08 +42:54:38.8
05:40:12.12 +49:59:20.7
05:59:56.69 +47:42:29.3
05:57:10.19 +49:12:44.0
06:09:30.56 +47:38:24.8
06:23:59.27 +49:07:14.1
06:21:37.38 +46:13:41.0
05:49:41.95 +49:47:53.3
05:38:23.95 +43:01:26.1
06:22:15.24 +49:07:56.7
06:02:11.56 +48:10:14.6
06:25:28.98 +49:51:19.8
05:57:31.29 +45:55:36.2
05:38:45.36 +46:03:56.2
06:03:20.95 +50:10:11.7
05:38:25.61 +43:01:25.0
06:24:07.70 +42:39:43.9
05:57:39.31 +46:06:17.3
06:24:45.76 +45:25:15.2
06:23:39.33 +47:07:08.4
05:49:27.11 +47:51:15.6
06:11:44.69 +50:09:38.3
06:07:51.62 +41:51:39.4
06:21:36.95 +44:33:03.5
05:43:55.42 +47:43:43.5
05:46:30.88 +45:16:45.9
06:04:03.73 +44:44:18.0
06:11:17.82 +45:05:36.6
05:56:58.13 +42:53:46.4
06:07:46.52 +44:48:08.2
06:33:27.82 +45:59:06.2
06:16:32.96 +42:12:58.7
06:09:29.12 +45:34:15.0
06:11:24.08 +44:45:02.4
06:02:41.93 +46:44:07.0
06:13:05.58 +44:00:27.2
05:47:09.11 +46:03:13.1
05:57:10.27 +48:21:26.8
05:42:59.56 +47:58:43.9
05:59:27.58 +47:36:21.9
06:09:21.32 +46:34:56.1
05:49:30.90 +46:35:57.0
05:48:24.67 +46:18:13.7
########### Completed Aur-02-Q2b1x1 ###########
The analysis was running at tau
We are allowed to update the exclusion list at tau host
Found ../exclusion_list_TTUQ2.txt
#### The exclusion list before filtering-out asteroids, bad pixels and adding Gaia sources ####
06:14:20.67 +46:48:18.8
05:45:41.68 +43:39:24.4
05:57:10.47 +48:21:36.3
05:52:14.37 +42:53:07.0
06:05:03.62 +42:45:04.0
06:05:15.74 +42:45:22.3
06:10:31.36 +44:45:11.2
05:36:46.90 +41:50:37.2
05:42:00.34 +46:28:19.2
06:16:33.70 +42:03:05.9
06:15:54.57 +44:36:21.0
06:16:01.97 +44:45:53.6
06:28:09.71 +42:02:23.7
05:38:09.42 +42:12:53.0
05:38:09.46 +41:40:53.8
06:14:39.76 +42:30:55.2
05:36:50.81 +41:58:44.2
06:11:00.97 +48:42:54.0
06:30:09.69 +46:03:54.7
06:13:09.90 +44:46:22.7
06:35:29.64 +44:48:38.1
06:05:26.24 +44:41:50.7
06:25:20.73 +42:06:38.7
06:23:55.12 +43:37:32.8
06:02:53.95 +43:00:18.5
06:11:35.31 +50:11:55.2
05:40:40.82 +48:19:53.5
05:48:55.74 +49:48:13.6
06:16:45.02 +45:53:52.9
06:03:02.72 +42:44:13.6
06:10:28.21 +47:28:45.9
05:59:38.33 +44:02:50.9
06:00:45.58 +49:57:44.2
05:57:32.41 +45:54:03.3
06:11:15.59 +45:05:30.2
05:47:14.83 +46:04:42.8
05:47:39.23 +50:01:19.6
05:55:37.25 +42:34:04.3
05:44:44.91 +48:57:11.4
05:51:54.53 +49:31:09.2
05:42:29.87 +44:45:51.9
06:07:34.33 +46:41:15.5
05:56:18.51 +46:15:14.4
06:24:57.20 +43:11:54.7
05:43:05.71 +44:52:29.7
05:57:59.08 +42:54:38.8
05:40:12.12 +49:59:20.7
05:59:56.69 +47:42:29.3
05:57:10.19 +49:12:44.0
06:09:30.56 +47:38:24.8
06:23:59.27 +49:07:14.1
06:21:37.38 +46:13:41.0
05:49:41.95 +49:47:53.3
05:38:23.95 +43:01:26.1
06:22:15.24 +49:07:56.7
06:02:11.56 +48:10:14.6
06:25:28.98 +49:51:19.8
05:57:31.29 +45:55:36.2
05:38:45.36 +46:03:56.2
06:03:20.95 +50:10:11.7
05:38:25.61 +43:01:25.0
06:24:07.70 +42:39:43.9
05:57:39.31 +46:06:17.3
06:24:45.76 +45:25:15.2
06:23:39.33 +47:07:08.4
05:49:27.11 +47:51:15.6
06:11:44.69 +50:09:38.3
06:07:51.62 +41:51:39.4
06:21:36.95 +44:33:03.5
05:43:55.42 +47:43:43.5
05:46:30.88 +45:16:45.9
06:04:03.73 +44:44:18.0
06:11:17.82 +45:05:36.6
05:56:58.13 +42:53:46.4
06:07:46.52 +44:48:08.2
06:33:27.82 +45:59:06.2
06:16:32.96 +42:12:58.7
06:09:29.12 +45:34:15.0
06:11:24.08 +44:45:02.4
06:02:41.93 +46:44:07.0
06:13:05.58 +44:00:27.2
05:47:09.11 +46:03:13.1
05:49:30.90 +46:35:57.0
05:59:27.58 +47:36:21.9
05:42:59.56 +47:58:43.9
06:09:21.32 +46:34:56.1
05:57:10.27 +48:21:26.8
05:33:54.71 +46:42:34.3
05:48:24.67 +46:18:13.7
###################################################################################
06:14:20.67 +46:48:18.8 -- not an asteroid (will add it to exclusion list)
05:45:41.68 +43:39:24.4 -- not an asteroid (will add it to exclusion list)
05:57:10.47 +48:21:36.3 -- not an asteroid (will add it to exclusion list)
05:52:14.37 +42:53:07.0 -- not an asteroid (will add it to exclusion list)
06:05:03.62 +42:45:04.0 -- not an asteroid (will add it to exclusion list)
06:05:15.74 +42:45:22.3 -- not an asteroid (will add it to exclusion list)
06:10:31.36 +44:45:11.2 -- not an asteroid (will add it to exclusion list)
05:36:46.90 +41:50:37.2 -- not an asteroid (will add it to exclusion list)
05:42:00.34 +46:28:19.2 -- not an asteroid (will add it to exclusion list)
06:16:33.70 +42:03:05.9 -- not an asteroid (will add it to exclusion list)
06:15:54.57 +44:36:21.0 -- not an asteroid (will add it to exclusion list)
06:16:01.97 +44:45:53.6 -- not an asteroid (will add it to exclusion list)
06:28:09.71 +42:02:23.7 -- not an asteroid (will add it to exclusion list)
05:38:09.42 +42:12:53.0 -- not an asteroid (will add it to exclusion list)
05:38:09.46 +41:40:53.8 -- not an asteroid (will add it to exclusion list)
06:14:39.76 +42:30:55.2 -- not an asteroid (will add it to exclusion list)
05:36:50.81 +41:58:44.2 -- not an asteroid (will add it to exclusion list)
06:11:00.97 +48:42:54.0 -- not an asteroid (will add it to exclusion list)
06:30:09.69 +46:03:54.7 -- not an asteroid (will add it to exclusion list)
06:13:09.90 +44:46:22.7 -- not an asteroid (will add it to exclusion list)
06:35:29.64 +44:48:38.1 -- not an asteroid (will add it to exclusion list)
06:05:26.24 +44:41:50.7 -- not an asteroid (will add it to exclusion list)
06:25:20.73 +42:06:38.7 -- not an asteroid (will add it to exclusion list)
06:23:55.12 +43:37:32.8 -- not an asteroid (will add it to exclusion list)
06:02:53.95 +43:00:18.5 -- not an asteroid (will add it to exclusion list)
06:11:35.31 +50:11:55.2 -- not an asteroid (will add it to exclusion list)
05:40:40.82 +48:19:53.5 -- not an asteroid (will add it to exclusion list)
05:48:55.74 +49:48:13.6 -- not an asteroid (will add it to exclusion list)
06:16:45.02 +45:53:52.9 -- not an asteroid (will add it to exclusion list)
06:03:02.72 +42:44:13.6 -- not an asteroid (will add it to exclusion list)
06:10:28.21 +47:28:45.9 -- not an asteroid (will add it to exclusion list)
05:59:38.33 +44:02:50.9 -- not an asteroid (will add it to exclusion list)
06:00:45.58 +49:57:44.2 -- not an asteroid (will add it to exclusion list)
05:57:32.41 +45:54:03.3 -- not an asteroid (will add it to exclusion list)
06:11:15.59 +45:05:30.2 -- not an asteroid (will add it to exclusion list)
05:47:14.83 +46:04:42.8 -- not an asteroid (will add it to exclusion list)
05:47:39.23 +50:01:19.6 -- not an asteroid (will add it to exclusion list)
05:55:37.25 +42:34:04.3 -- not an asteroid (will add it to exclusion list)
05:44:44.91 +48:57:11.4 -- not an asteroid (will add it to exclusion list)
05:51:54.53 +49:31:09.2 -- not an asteroid (will add it to exclusion list)
05:42:29.87 +44:45:51.9 -- not an asteroid (will add it to exclusion list)
06:07:34.33 +46:41:15.5 -- not an asteroid (will add it to exclusion list)
05:56:18.51 +46:15:14.4 -- not an asteroid (will add it to exclusion list)
06:24:57.20 +43:11:54.7 -- not an asteroid (will add it to exclusion list)
05:43:05.71 +44:52:29.7 -- not an asteroid (will add it to exclusion list)
05:57:59.08 +42:54:38.8 -- not an asteroid (will add it to exclusion list)
05:40:12.12 +49:59:20.7 -- not an asteroid (will add it to exclusion list)
05:59:56.69 +47:42:29.3 -- not an asteroid (will add it to exclusion list)
05:57:10.19 +49:12:44.0 -- not an asteroid (will add it to exclusion list)
06:09:30.56 +47:38:24.8 -- not an asteroid (will add it to exclusion list)
06:23:59.27 +49:07:14.1 -- not an asteroid (will add it to exclusion list)
06:21:37.38 +46:13:41.0 -- not an asteroid (will add it to exclusion list)
05:49:41.95 +49:47:53.3 -- not an asteroid (will add it to exclusion list)
05:38:23.95 +43:01:26.1 -- not an asteroid (will add it to exclusion list)
06:22:15.24 +49:07:56.7 -- not an asteroid (will add it to exclusion list)
06:02:11.56 +48:10:14.6 -- not an asteroid (will add it to exclusion list)
06:25:28.98 +49:51:19.8 -- not an asteroid (will add it to exclusion list)
05:57:31.29 +45:55:36.2 -- not an asteroid (will add it to exclusion list)
05:38:45.36 +46:03:56.2 -- not an asteroid (will add it to exclusion list)
06:03:20.95 +50:10:11.7 -- not an asteroid (will add it to exclusion list)
05:38:25.61 +43:01:25.0 -- not an asteroid (will add it to exclusion list)
06:24:07.70 +42:39:43.9 -- not an asteroid (will add it to exclusion list)
05:57:39.31 +46:06:17.3 -- not an asteroid (will add it to exclusion list)
06:24:45.76 +45:25:15.2 -- not an asteroid (will add it to exclusion list)
06:23:39.33 +47:07:08.4 -- not an asteroid (will add it to exclusion list)
05:49:27.11 +47:51:15.6 -- not an asteroid (will add it to exclusion list)
06:11:44.69 +50:09:38.3 -- not an asteroid (will add it to exclusion list)
06:07:51.62 +41:51:39.4 -- not an asteroid (will add it to exclusion list)
06:21:36.95 +44:33:03.5 -- not an asteroid (will add it to exclusion list)
05:43:55.42 +47:43:43.5 -- not an asteroid (will add it to exclusion list)
05:46:30.88 +45:16:45.9 -- not an asteroid (will add it to exclusion list)
06:04:03.73 +44:44:18.0 -- not an asteroid (will add it to exclusion list)
06:11:17.82 +45:05:36.6 -- not an asteroid (will add it to exclusion list)
05:56:58.13 +42:53:46.4 -- not an asteroid (will add it to exclusion list)
06:07:46.52 +44:48:08.2 -- not an asteroid (will add it to exclusion list)
06:33:27.82 +45:59:06.2 -- not an asteroid (will add it to exclusion list)
06:16:32.96 +42:12:58.7 -- not an asteroid (will add it to exclusion list)
06:09:29.12 +45:34:15.0 -- not an asteroid (will add it to exclusion list)
06:11:24.08 +44:45:02.4 -- not an asteroid (will add it to exclusion list)
06:02:41.93 +46:44:07.0 -- not an asteroid (will add it to exclusion list)
06:13:05.58 +44:00:27.2 -- not an asteroid (will add it to exclusion list)
05:47:09.11 +46:03:13.1 -- not an asteroid (will add it to exclusion list)
05:49:30.90 +46:35:57.0 -- not an asteroid (will add it to exclusion list)
05:59:27.58 +47:36:21.9 -- not an asteroid (will add it to exclusion list)
05:42:59.56 +47:58:43.9 -- not an asteroid (will add it to exclusion list)
06:09:21.32 +46:34:56.1 -- not an asteroid (will add it to exclusion list)
05:57:10.27 +48:21:26.8 -- not an asteroid (will add it to exclusion list)
05:33:54.71 +46:42:34.3 -- not an asteroid (will add it to exclusion list)
05:48:24.67 +46:18:13.7 -- not an asteroid (will add it to exclusion list)
renamed 'exclusion_list_index_html.txt_noasteroids' -> 'exclusion_list_index_html.txt'
05:33:54.71 +46:42:34.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:36:46.90 +41:50:37.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:36:50.81 +41:58:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:09.42 +42:12:53.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:09.46 +41:40:53.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:23.95 +43:01:26.1 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:25.61 +43:01:25.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:38:45.36 +46:03:56.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:40:12.12 +49:59:20.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:40:40.82 +48:19:53.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:42:00.34 +46:28:19.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:42:29.87 +44:45:51.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:42:59.56 +47:58:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:43:05.71 +44:52:29.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:43:55.42 +47:43:43.5 -- does not seem to be a hot pixel (will add it to exclusion list)
05:44:44.91 +48:57:11.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:45:41.68 +43:39:24.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:46:30.88 +45:16:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:09.11 +46:03:13.1 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:14.83 +46:04:42.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:47:39.23 +50:01:19.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:48:24.67 +46:18:13.7 -- does not seem to be a hot pixel (will add it to exclusion list)
05:48:55.74 +49:48:13.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:49:27.11 +47:51:15.6 -- does not seem to be a hot pixel (will add it to exclusion list)
05:49:30.90 +46:35:57.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:49:41.95 +49:47:53.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:51:54.53 +49:31:09.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:52:14.37 +42:53:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:55:37.25 +42:34:04.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:56:18.51 +46:15:14.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:56:58.13 +42:53:46.4 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:10.19 +49:12:44.0 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:10.27 +48:21:26.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:10.47 +48:21:36.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:31.29 +45:55:36.2 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:32.41 +45:54:03.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:39.31 +46:06:17.3 -- does not seem to be a hot pixel (will add it to exclusion list)
05:57:59.08 +42:54:38.8 -- does not seem to be a hot pixel (will add it to exclusion list)
05:59:27.58 +47:36:21.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:59:38.33 +44:02:50.9 -- does not seem to be a hot pixel (will add it to exclusion list)
05:59:56.69 +47:42:29.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:00:45.58 +49:57:44.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:02:11.56 +48:10:14.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:02:41.93 +46:44:07.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:02:53.95 +43:00:18.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:03:02.72 +42:44:13.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:03:20.95 +50:10:11.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:04:03.73 +44:44:18.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:05:03.62 +42:45:04.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:05:15.74 +42:45:22.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:05:26.24 +44:41:50.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:07:34.33 +46:41:15.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:07:46.52 +44:48:08.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:07:51.62 +41:51:39.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:09:21.32 +46:34:56.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:09:29.12 +45:34:15.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:09:30.56 +47:38:24.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:10:28.21 +47:28:45.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:10:31.36 +44:45:11.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:00.97 +48:42:54.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:15.59 +45:05:30.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:17.82 +45:05:36.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:24.08 +44:45:02.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:35.31 +50:11:55.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:11:44.69 +50:09:38.3 -- does not seem to be a hot pixel (will add it to exclusion list)
06:13:05.58 +44:00:27.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:13:09.90 +44:46:22.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:14:20.67 +46:48:18.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:14:39.76 +42:30:55.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:15:54.57 +44:36:21.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:16:01.97 +44:45:53.6 -- does not seem to be a hot pixel (will add it to exclusion list)
06:16:32.96 +42:12:58.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:16:33.70 +42:03:05.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:16:45.02 +45:53:52.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:21:36.95 +44:33:03.5 -- does not seem to be a hot pixel (will add it to exclusion list)
06:21:37.38 +46:13:41.0 -- does not seem to be a hot pixel (will add it to exclusion list)
06:22:15.24 +49:07:56.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:23:39.33 +47:07:08.4 -- does not seem to be a hot pixel (will add it to exclusion list)
06:23:55.12 +43:37:32.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:23:59.27 +49:07:14.1 -- does not seem to be a hot pixel (will add it to exclusion list)
06:24:07.70 +42:39:43.9 -- does not seem to be a hot pixel (will add it to exclusion list)
06:24:45.76 +45:25:15.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:24:57.20 +43:11:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:25:20.73 +42:06:38.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:25:28.98 +49:51:19.8 -- does not seem to be a hot pixel (will add it to exclusion list)
06:28:09.71 +42:02:23.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:30:09.69 +46:03:54.7 -- does not seem to be a hot pixel (will add it to exclusion list)
06:33:27.82 +45:59:06.2 -- does not seem to be a hot pixel (will add it to exclusion list)
06:35:29.64 +44:48:38.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)
05:33:54.71 +46:42:34.3 -- not a known variable star
05:36:46.90 +41:50:37.2 -- not a known variable star
05:36:50.81 +41:58:44.2 -- not a known variable star
05:38:09.42 +42:12:53.0 -- not a known variable star
05:38:09.46 +41:40:53.8 -- not a known variable star
05:38:23.95 +43:01:26.1 -- not a known variable star
05:38:25.61 +43:01:25.0 -- not a known variable star
05:38:45.36 +46:03:56.2 -- not a known variable star
05:40:12.12 +49:59:20.7 -- not a known variable star
05:40:40.82 +48:19:53.5 -- not a known variable star
05:42:00.34 +46:28:19.2 -- not a known variable star
05:42:29.87 +44:45:51.9 -- not a known variable star
05:42:59.56 +47:58:43.9 -- a known variable star
05:43:05.71 +44:52:29.7 -- not a known variable star
05:43:55.42 +47:43:43.5 -- not a known variable star
05:44:44.91 +48:57:11.4 -- not a known variable star
05:45:41.68 +43:39:24.4 -- a known variable star
05:46:30.88 +45:16:45.9 -- not a known variable star
05:47:09.11 +46:03:13.1 -- not a known variable star
05:47:14.83 +46:04:42.8 -- not a known variable star
05:47:39.23 +50:01:19.6 -- a known variable star
05:48:24.67 +46:18:13.7 -- a known variable star
05:48:55.74 +49:48:13.6 -- not a known variable star
05:49:27.11 +47:51:15.6 -- not a known variable star
05:49:30.90 +46:35:57.0 -- a known variable star
05:49:41.95 +49:47:53.3 -- not a known variable star
05:51:54.53 +49:31:09.2 -- not a known variable star
05:52:14.37 +42:53:07.0 -- not a known variable star
05:55:37.25 +42:34:04.3 -- not a known variable star
05:56:18.51 +46:15:14.4 -- not a known variable star
05:56:58.13 +42:53:46.4 -- not a known variable star
05:57:10.19 +49:12:44.0 -- not a known variable star
05:57:10.27 +48:21:26.8 -- not a known variable star
05:57:10.47 +48:21:36.3 -- not a known variable star
05:57:31.29 +45:55:36.2 -- not a known variable star
05:57:32.41 +45:54:03.3 -- not a known variable star
05:57:39.31 +46:06:17.3 -- not a known variable star
05:57:59.08 +42:54:38.8 -- not a known variable star
05:59:27.58 +47:36:21.9 -- not a known variable star
05:59:38.33 +44:02:50.9 -- not a known variable star
05:59:56.69 +47:42:29.3 -- not a known variable star
06:00:45.58 +49:57:44.2 -- not a known variable star
06:02:11.56 +48:10:14.6 -- not a known variable star
06:02:41.93 +46:44:07.0 -- not a known variable star
06:02:53.95 +43:00:18.5 -- not a known variable star
06:03:02.72 +42:44:13.6 -- not a known variable star
06:03:20.95 +50:10:11.7 -- not a known variable star
06:04:03.73 +44:44:18.0 -- not a known variable star
06:05:03.62 +42:45:04.0 -- not a known variable star
06:05:15.74 +42:45:22.3 -- not a known variable star
06:05:26.24 +44:41:50.7 -- not a known variable star
06:07:34.33 +46:41:15.5 -- not a known variable star
06:07:46.52 +44:48:08.2 -- not a known variable star
06:07:51.62 +41:51:39.4 -- not a known variable star
06:09:21.32 +46:34:56.1 -- a known variable star
06:09:29.12 +45:34:15.0 -- not a known variable star
06:09:30.56 +47:38:24.8 -- not a known variable star
06:10:28.21 +47:28:45.9 -- not a known variable star
06:10:31.36 +44:45:11.2 -- not a known variable star
06:11:00.97 +48:42:54.0 -- not a known variable star
06:11:15.59 +45:05:30.2 -- not a known variable star
06:11:17.82 +45:05:36.6 -- not a known variable star
06:11:24.08 +44:45:02.4 -- not a known variable star
06:11:35.31 +50:11:55.2 -- not a known variable star
06:11:44.69 +50:09:38.3 -- not a known variable star
06:13:05.58 +44:00:27.2 -- not a known variable star
06:13:09.90 +44:46:22.7 -- a known variable star
06:14:20.67 +46:48:18.8 -- not a known variable star
06:14:39.76 +42:30:55.2 -- not a known variable star
06:15:54.57 +44:36:21.0 -- not a known variable star
06:16:01.97 +44:45:53.6 -- not a known variable star
06:16:32.96 +42:12:58.7 -- not a known variable star
06:16:33.70 +42:03:05.9 -- not a known variable star
06:16:45.02 +45:53:52.9 -- not a known variable star
06:21:36.95 +44:33:03.5 -- not a known variable star
06:21:37.38 +46:13:41.0 -- not a known variable star
06:22:15.24 +49:07:56.7 -- not a known variable star
06:23:39.33 +47:07:08.4 -- not a known variable star
06:23:55.12 +43:37:32.8 -- not a known variable star
06:23:59.27 +49:07:14.1 -- not a known variable star
06:24:07.70 +42:39:43.9 -- not a known variable star
06:24:45.76 +45:25:15.2 -- not a known variable star
06:24:57.20 +43:11:54.7 -- not a known variable star
06:25:20.73 +42:06:38.7 -- not a known variable star
06:25:28.98 +49:51:19.8 -- not a known variable star
06:28:09.71 +42:02:23.7 -- not a known variable star
06:30:09.69 +46:03:54.7 -- not a known variable star
06:33:27.82 +45:59:06.2 -- not a known variable star
06:35:29.64 +44:48:38.1 -- not a known variable star
Found 82 unidentified candidates (excluding asteroids, hot pixels and known variable stars).
###################################################################################
89 candidates found (excluding asteroids and hot pixels)
This does not look like a test run
ERROR: too many candidates -- 89 (excluding asteroids and hot pixels, 82 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)2461144.70103343 -observatory V36
23:57:55.77 -03:01:10.0 Mercury (0.1mag)
02:59:52.35 +17:10:18.1 Venus (-3.9mag)
00:12:43.83 +00:18:07.9 Mars (1.2mag)
07:11:49.77 +22:47:32.2 Jupiter (-2.1mag)
00:28:22.69 +00:43:58.1 Saturn (0.9mag)
03:47:19.24 +19:46:16.1 Uranus (5.8mag)
00:10:36.25 -00:16:51.6 Neptune (7.8mag)
20:33:40.38 -22:52:31.5 Pluto (14.5mag)
22:48:28.80 -07:45:15.5 Moon (-9.2mag)
-rw-r--r-- 1 apache apache 361 Apr 13 23:52 planets.txt
############################################################
Positions of selected moons from JPL HORIZONS for JD(UT)2461144.70103343:
07:11:47.05 +22:47:40.1 Io (5.8mag)
07:11:47.81 +22:47:33.3 Europa (5.9mag)
07:11:58.76 +22:47:20.1 Ganymede (5.3mag)
07:12:16.37 +22:46:44.8 Callisto (6.6mag)
07:15:14.68 +22:36:00.5 Himalia (15.3mag)
07:11:45.86 +22:47:40.5 Thebe (16.2mag)
07:15:23.72 +23:06:03.3 Elara (17.3mag)
07:10:35.31 +23:28:29.0 Pasiphae (17.4mag)
07:20:11.85 +22:45:22.7 Carme (18.5mag)
00:28:30.59 +00:44:14.5 Titan (8.8mag)
00:28:24.61 +00:44:12.1 Rhea (10.1mag)
00:28:05.94 +00:44:24.7 Iapetus (11.5mag)
00:28:35.93 +00:44:07.2 Hyperion (14.8mag)
00:30:01.01 +00:52:57.9 Phoebe (16.8mag)
-rw-r--r-- 1 apache apache 569 Apr 13 23:52 moons.txt
############################################################
Positions of selected spacecraft from JPL HORIZONS for JD(UT)2461144.70103343:
15:30:12.50 -14:58:23.2 JWST
17:07:47.57 +44:11:29.8 Chandra
08:03:25.00 -39:34:58.0 XMM-Newton
-rw-r--r-- 1 apache apache 96 Apr 13 23:52 spacecraft.txt
############################################################
Positions of bright comets computed with util/comet_finder/main.py for JD(UT)2461144.70103343 -observatory V36
-> Warning: Longitude 255.61742 is outside valid range [-180, 180]
18:51:14.86 -28:40:27.3 13.9mag P/2010 H2 (Vales)
05:05:27.12 -69:44:51.0 17.4mag C/2014 UN271 (Bernardinelli-Bernstein)
05:32:03.76 +31:25:30.9 17.2mag C/2017 K2 (PANSTARRS)
17:30:36.14 +10:20:03.2 17.6mag C/2021 G2 (ATLAS)
23:09:44.40 +29:09:29.2 17.1mag C/2022 E2 (ATLAS)
04:27:08.60 +25:59:22.0 16.0mag C/2022 N2 (PANSTARRS)
09:03:02.76 +32:00:21.4 16.2mag C/2022 QE78 (ATLAS)
08:30:48.33 -00:20:39.9 17.3mag C/2022 R6 (PANSTARRS)
18:54:08.91 +18:22:52.1 17.5mag C/2023 A3 (Tsuchinshan-ATLAS)
15:41:15.02 -11:32:52.4 17.5mag P/2023 B1 (PANSTARRS)
09:08:28.93 -12:10:20.4 17.6mag C/2023 F3 (ATLAS)
21:52:23.45 +62:48:06.3 17.5mag C/2023 H5 (Lemmon)
19:20:43.55 -03:42:13.6 14.2mag C/2023 R1 (PANSTARRS)
21:35:50.94 +85:39:46.6 17.8mag C/2023 X2 (Lemmon)
06:17:05.01 +63:31:17.4 17.1mag C/2024 A1 (ATLAS)
05:09:23.44 +17:41:55.9 10.9mag C/2024 E1 (Wierzchos)
16:20:25.42 +06:05:43.8 17.4mag C/2024 G6 (ATLAS)
20:20:17.86 +14:47:14.1 14.6mag C/2024 J3 (ATLAS)
03:24:45.39 -22:39:36.7 16.4mag C/2024 T5 (ATLAS)
05:15:11.46 +45:44:23.1 17.7mag C/2025 J1 (Borisov)
13:46:18.75 +44:16:33.6 15.1mag C/2025 L1 (ATLAS)
03:22:26.60 -25:55:56.2 17.8mag C/2025 Q3 (ATLAS)
23:28:58.52 +19:08:07.9 8.8mag C/2025 R3 (PANSTARRS)
12:54:53.92 +02:54:10.6 17.4mag C/2025 Y1 (ATLAS)
03:12:26.88 +02:49:50.9 12.7mag C/2026 A1 (MAPS)
23:54:27.51 +36:53:05.2 14.5mag C/2026 B2 (Sun-Gao)
18:39:26.04 -09:48:54.7 11.9mag 10P/Tempel
15:02:44.12 +03:23:39.0 13.8mag 24P/Schaumasse
11:03:17.39 -01:35:04.3 15.7mag 29P/Schwassmann-Wachmann
18:00:24.95 -09:40:36.5 17.9mag 40P/Vaisala
10:37:39.38 -04:14:35.6 16.9mag 43P/Wolf-Harrington
01:45:53.34 +17:10:50.5 17.2mag 47P/Ashbrook-Jackson
07:07:27.21 +37:23:55.4 17.0mag 63P/Wild
23:26:45.53 -11:40:02.5 15.7mag 65P/Gunn
03:58:27.13 +20:38:02.3 15.9mag 76P/West-Kohoutek-Ikemura
01:01:35.98 +07:52:29.6 14.3mag 78P/Gehrels
22:57:32.52 -09:55:23.1 14.6mag 88P/Howell
02:05:19.02 +20:09:40.6 15.1mag 93P/Lovas
04:51:25.29 +32:11:28.4 16.2mag 123P/West-Hartley
08:26:15.75 +39:11:28.7 16.2mag 124P/Mrkos
02:30:26.22 +14:10:08.5 16.4mag 128P/Shoemaker-Holt
02:44:00.50 +14:16:23.0 17.5mag 131P/Mueller
01:16:43.95 +12:36:42.1 10.7mag 141P/Machholz
01:25:54.49 +04:11:54.3 10.7mag 141P-A/Machholz
00:12:04.69 +00:10:31.1 13.0mag 141P-D/Machholz
01:56:04.82 +05:57:05.2 17.8mag 141P-I/Machholz
00:57:21.70 -02:25:49.7 15.1mag 162P/SidingSpring
10:29:05.75 +30:57:18.5 18.0mag 164P/Christensen
06:33:12.25 +24:17:54.3 18.0mag 198P/ODAS
14:54:37.98 -00:15:21.3 17.6mag 210P/Christensen
21:33:36.86 -11:52:56.9 17.6mag 218P/LINEAR
17:16:05.26 -14:08:56.5 16.1mag 235P/LINEAR
05:30:36.02 +34:33:38.8 16.7mag 240P/NEAT
07:37:37.06 -05:21:46.6 17.7mag 242P/Spahr
22:12:24.76 -21:27:21.1 17.9mag 260P/McNaught
15:43:20.24 +06:52:16.6 17.5mag 391P/Kowalski
07:33:30.78 +21:21:36.3 17.7mag 450P/LONEOS
05:33:15.05 +45:08:16.8 17.5mag 493P/LONEOS
-rw-r--r-- 1 apache apache 2.9K Apr 13 23:52 comets.txt
############################################################
List of recent ASAS-SN transients from https://www.astronomy.ohio-state.edu/asassn/transients.html :
16:08:18.39 -64:11:08.80 ASASSN-26cp 2026-04-9.29 13.32
09:22:22.90 -61:02:43.70 SN2026idh 2026-04-7.97 16.34
05:06:54.12 -19:42:26.40 AT2026imr 2026-04-8 17.49
07:14:55.34 -36:03:21.40 AT2026hei 2026-04-8.12 16.7
21:35:33.14 -19:01:34.80 AT2026ihm 2026-04-8.36 16.7
04:28:24.08 -32:25:35.30 AT2026imo 2026-04-8.02 16.81
05:10:35.79 -39:38:40.80 SN 2026hnn 2026-04-7.04 17.07
09:54:32.04 -01:17:25.80 ASASSN-26cn 2026-04-7.01 15.58
07:46:24.43 -77:29:35.90 ASASSN-26co 2026-04-7.15 14.93
05:00:45.52 -29:51:06.20 AT2026hvw 2026-04-6.03 16.51
19:49:33.10 -23:37:11.00 ASASSN-26cl 2026-04-5.29 14.98
19:32:43.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
-rw-r--r-- 1 apache apache 5.8K Apr 13 23:52 asassn_transients_list.txt
############################################################
Truncated list of TOCP transients from http://www.cbat.eps.harvard.edu/unconf/tocp.html :
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
00:43:38.36 +41:15:32.4 PNV J00433836+4115324 2026-04-08.079 17.2mag
-rw-r--r-- 1 apache apache 188K Apr 13 23:52 tocp_transients_list.txt
############################################################
Truncated list of recent TNS transients from https://www.wis-tns.org/ :
11:56:46.937 +30:48:49.43 AT 2026ivi 2026-04-07.29 20.1063
12:16:21.919 +30:21:04.60 AT 2026ivh 2026-04-07.29 19.651
09:11:45.682 +30:03:32.51 AT 2026ivg 2026-04-04.17 19.5142
09:55:25.809 -27:42:27.02 AT 2026ivf 2026-04-08.21 18.51
09:46:07.094 +07:14:13.61 AT 2026ive 2026-04-08.15 19.9446
09:29:29.340 -01:21:08.51 AT 2026ivd 2026-04-05.15 19.4593
09:53:27.521 +16:01:50.20 AT 2026ivc 2026-04-07.17 20.1328
10:57:27.283 +18:19:29.99 AT 2026ivb 2026-04-07.87 19.71
12:50:08.105 +01:17:40.78 AT 2026iva 2026-04-07.89 19.96
10:38:31.370 -04:47:42.62 AT 2026iuz 2026-04-07.85 18.9
13:03:44.252 +20:35:06.20 AT 2026iuy 2026-04-06.96 19.7
13:53:33.216 -46:24:12.81 AT 2026iux 2026-04-07.63 19.83
20:29:30.119 -10:56:33.33 AT 2026iuw 2026-03-29.79 19.55
13:31:30.960 -32:00:09.92 AT 2026iuv 2026-04-07.60 18.91
14:00:56.468 -25:06:29.29 AT 2026iuu 2026-04-07.35 18.482
13:27:25.132 +09:30:53.72 AT 2026iut 2026-04-05.33 19.4971
13:57:28.106 -31:36:18.49 AT 2026ius 2026-04-07.61 19.27
09:54:32.050 -01:17:25.84 SN 2026iur 2026-04-07.01 15.9
14:24:08.131 +22:56:14.71 AT 2026iuq 2026-04-07.38 19.91
10:07:28.221 -17:12:04.00 AT 2026iup 2026-04-05.31 20.26
-rw-r--r-- 1 apache apache 30K Apr 13 23:52 tns_transients_list.txt
