Swope + e2v CCD Reduction Manual
Started on March 20, 2014 (Carlos)
Basically the automatic pipeline does everything. You only will deal with data that
was not recognized as CSP data by the software.
If observer ran OBS_QUICK_SWO_NC_RED
- Connect to csp2 machine and go to work directory.
> cd /csp21/work/SWO_NC_20180924_25
- Check the pipeline has finished the reduction.
For example comparing the created files date with the computer date as:
> ls -lrt ; date
- In parallel you can check the partial automatic results and the S/N of the targets
opening in a new browser tab: REDUCTIONS
- The automatized pipelines classifies the objects in 4 groups,
CSP "known" objects (objects we are already following)
CSP "new" objects (objects which we just started to follow today)
No-CSP objects (external objects, typically requests from SPIRITS, NIDIA, KEVIN, ...)
No-Processed objects (objects which have not been solved astrometrically, so they are unidentified)
- Check the list of every group as:
> more list_new_obj.txt
> more list_ext_obj.txt
> more list_no_proc.txt
> more list_old_csp.txt
- The "known" portion of the data should been already processed.
That meaning: saved at the data repository, photometric measurements
were done on science and standard fiels and uploaded to the database,
the night was calibrated, and the local sequences and the SNe photometry
So from here we should only deal with the other 3 data groups.
- External Data
- If the "list_ext_obj.txt" is not empty. Open the file and fix the
file numbering (change the xx --> 01, 02, ... etc.)
Then you can execute the file, in this way moving the data to the repository.
> source list_ext_obj.txt
- No-Processed Data
- If the "list_no_proc.txt" is not empty, you need to give an astrometric solution
to the images, once they are solved you can run SPREAD with them, so the software
can identify the fields they belong to. If the target is new, you will need to
add the name and coords to the file /csp21/work/CATALOG.txt (at the end of the list please),
and the run SPREAD.
Check and run the spread.txt file, then you can run MAGINS with the stored files
and a catalog (if the object is new, the catalog needs to be created).
Once the photometry was measured, upload it to the database. And run
MAGLSEQ and MAGSN to update the local sequence and SN photometries.
- New CSP Data
- If the file "list_new_obj.txt" is not empty, you will need to
enter the objects name and coords to the end of the file /csp21/work/CATALOG.txt
and create a local sequence catalog. Then upload the catalog to the database.
Then run SPREAD on the images, source the spread.txt file, run MAGINS
on the stored images, upload the photometry to the database, and
update the local sequence and SNe photometries with MAGLSEQ and MAGSN.
- You are done!
- Now you can clean the directory with:
> rm ccd*fits fcd*fits
- Please check the photometric calibrations of the night with:
> more CAL/ZP.txt
and comment with me (carlos) if they don't look normal.
And finally, please, take a critical look on the data. Think about how to improve
observations and communicate with the pertinent people to make our data quality
- Comment on the reduction in the night report.
- Check and update the SN log.