| Author: | Daniel Sela |
|---|---|
| Contact: | [email protected], [email protected], [email protected] |
| Acknowledgement: | Robert Kehoe, Govinda Dhungana, Arnon Sela |
WARNING This is not a complete substitute of the analysis of Variable star search with ROTSE data.
Table of Contents
At the beginning of the process of finding variable stars, just getting the data from one star can take an hour. After finding the coordinates of a star, one must search through all the nights to find the objid's of the same star. Then, findburst_gd must be run in IDL to extract the stars data from each night. This package attempts to simplify this process. Some of these programs are similar to the their IDL counterparts, while others are added to shorten this process. Together, these programs can shorten the time it takes to gather the data of a star from an hour to a minute or less.
- Activate a virtual environment
- Install the packages in REQUIRED
- Go to the development directory: cd /path/to/dev_dir
- Get the URL for the repository and run: git clone URL
- Add the py folders to the python path: export PYTHONPATH=/path/to/rotseana/py:/path/to/rotseutil/py:/path/to/rotsedatamodel/py:$PYTHONPATH
- Download repository as ZIP through GitHub
- Activate a virtual environment
- In command line run: pip install /path/to/git-download
- Use getcoords to create a single file with the coordinates and filtered observations over all the nights.
- After finding the coordinates of one star though the result of find_burst, use matchcoords_gd to gather the data over all the nights. The inputed file can be the output of getcoords.
- Alternatively, if you do not wish to use getcoords, you can use findcoords_gd to gather the data over all the nights of a single star. Though findcoords_gd will take longer because it has to filter observations and search through the FIT or MATCH file for the coordinates and object id's. The output of getcoords can be used as the inputed file.
creates a PDF file instead of a postscript of all the stars within the designated file. The file types supported are .datc, .dat, and .fit.
| --mindelta | Minimum delta |
| --minsig | Minimum sigma |
| --minchisq | Minimum chisq |
| --log | Saves the output under name.log. The .log must be .pdf. |
find_burst --mindelta VALUE --minsig VALUE --minchisq VALUE --log name.log -f FILE
find_burst --mindelta 0.1 --minsig 1.0 --minchisq 2.0 --log sky1.pdf -f ../000906_sky0001_1c_match.datc
For more information run find_burst -h (or --help)
Extracts the date, magnitude, and magnitude error of a star given an object idea from a file and saves it as a text file.
| --match | Works on match structured files (.dat and .datc). Only use when the file you are retrieving the data from is a match structured file. |
| --fits | Works on FIT files. Only use when the file you are retrieving the data from is a FIT structured file. |
| --mindelta | Minimum delta |
| --minsig | Minimum sigma |
| --minchisq | Minimum chisq |
| --objid | Processes a specific objid |
| --log | Saves the output as a .txt. |
findburst_gd --match FILE --mindelta VALUE --minsig VALUE --minchisq VALUE --log name.txt
findburst_gd --fits FILE --mindelta VALUE --minsig VALUE --minchisq VALUE --objid VALUE --log name.txt
findburst_gd --match 000409_xtetrans_1a_match.dat --mindelta 0.1 --minsig 1.0 --minchisq 2.0 --objid 115 --log name.txt
Extracts the coordinates from one or more files and prints them to the terminal. You can concatenate the output into a text file. getcoords filters out bad observations. Negative RA coordinates are skipped as part of the filtering process. If you are going to use getcoords, it is recommended that you run it over in advance over multiple directories. It takes time for it to run on multiple files due to the filter observation that would be executed per object on each file. Furthermore, it is recommended that you collaborate with other users on the output, since only one output needs to be created per directory.
| -f, --file | Processes the specified file. |
getcoords -f FILE
getcoords -f 000409_xtetrans_1a_match.dat
Extract object ids of similar coordinates in a file within a specified error. matchcoords works on a text coordinate file that can be produced by getcoords. When typing the coordinates, there should be no spaces, and a capital "J" in the beginning. matchcoords process is similar to findcoords, however, since it is working on previously generated good coordinates file, it is much faster. Therefore, it is recommended to generate coordinate files per directory in advance, and search through the files using matchcoords.
| -e | error with a float value. |
matchoords -e ERRORVALUE -f FILE -c "COORDINATES"
getcoords -f 000409*_match.dat > all_coords.txt matchoords -e 10 -f all_coords.txt -c "J110526.404+501802.085"
Extract the date, magnitude, and magnitude error of a star given the coordinates and an error and output it into a text file. matchcoords_gd works on a text coordinate file that can be produced by getcoords.
| -e | error with with a float value. |
| --w-ref | adds the objid and the name of the file from which the data was extracted to the text file. |
| -c | (--coord) coordinates with a string "". Do not use any spaces and use a capital "J" at the beginning. |
| -f | (--file) the file(s) that the data will be extracted from. |
matchcoords_gd -e ERRORVALUE --log NAME -c "COORDINATES" -f FILE
matchcoords_gd -e ERRORVALUE --w-ref --log NAME -c "COORDINATES" -f FILE
matchcoords_gd -e 10 -—w-ref --log name_gd -c “J111734.010+501526.228” -f ../000409_xtetrans_1a_match.dat ../*.fit
Extract object ids of similar coordinates in a file within a specified error.
| -e | error with with a float value. |
| -c | (--coord) coordinates with a string "". Do not use any spaces and use a capital "J" at the beginning. |
| -f | (--file) the file(s) that the data will be extracted from. |
findcoords -e ERRORVALUE -c "COORDINATES" -f FILE
findcoords -e 10 -c "J110526.404+501802.085" -f 000409_xtetrans_1a_match.dat
Extract the date, magnitude, and magnitude error of a star given the coordinates and an error. This program saves the output into a text file.
| -e | error with with a float value. |
| --w-ref | adds the objid and the name of the file from which the data was extracted to the text file. |
| -c | (--coord) coordinates with a string "". Do not use any spaces and use a capital "J" at the beginning. |
| -f | (--file) the file(s) that the data will be extracted from. |
findcoords_gd -e ERRORVALUE --log NAME -c "COORDINATES" -f FILE
findcoords_gd -e ERRORVALUE --w-ref --log NAME -c "COORDINATES" -f FILE
findcoords_gd -e 10 -—w-ref --log name_gd -c “J111734.010+501526.228” -f ../000409_xtetrans_1a_match.dat ../*.fit