| Version 1 (modified by , 12 years ago) ( diff ) |
|---|
These are Heather's notes (and status) for SAS37 / ipptopsps
build of minis
This was done with minimal problems. Addstar ff/ sky had problems initially, Gene put in fixes for that. The faults that I have in the minis (only a handful of faults) are related to cluster / gpc1 problems. Rather than sort them out, I left those few exposures out. It's not complete (to ~10 exposures).
The labels and associated minis:
| stage | label | mini |
| cam | SAS.20141118 | SAS.20141118.cam |
| sky | SAS.20141118.rerun | SAS.20141118.sky.rerun.V2 |
| fullforce | SAS.20141118.rerun | SAS.20141118.ff.rerun.V2 |
| diff | SAS.20141118 | SAS.20141118.diff |
merge of SAS
This was done with no problems for diff, minimal problems for sky/cam/ff. First, there was a faulted sky, which reported no errors and completed on retry. I don't know how that affects the mergedvodb. Then, ff had problems to merge (related to the lensing stuff, Gene investigated and fixed). I was then able to merge ff into the mergedvodb. I redid the mergedvodb (to make absolutely certain that it's good)
| Name | minis | order |
| SAS.20141118.diff | SAS.20141118.diff | 1 |
| SAS.20141118.V2 | SAS.20141118.sky.rerun.V2 | 1 |
| SAS.20141118.V2 | SAS.20141118.cam | 2 |
| SAS.20141118.V2 | SAS.20141118.ff.rerun.V2 | 3 |
calibration of SAS
I intend to put a definitive set of rules/scripts for this. So far, neither SAS has been calibrated. The rules should be different for each
SAS.20141118.diff
- addstar resort
- relphot -averages -update
- (gene ?? relastro? what params?)
SAS.20141118.V2
Previous SASes have been calibrated this way:
- in tools/dvodb_calib
- run.addstar.resort
- run.setphot
- gene.run.relastro.part1
- gene.run.relastro.part2
- gene.run.relphot.3pinew
SAS 36 was calibrated by Gene this way:
{{{ for the sas calibration, see the file /data/ipp064.0/eugene/fforce.20140714/run.sascals and other files referenced in that script.
there are a few points:
- the sas images do not have ubercal zero points. I have defined a group of ubercal-tied exposures (ucal.smfs) which need to be merged into the database before running 'setphot'. I did this manually. you probably should just make a reference mini from this set to be used for this purpose
- sas does not need the koppenhoefer correction, so I have skipped that step. ditto for galaxy motion / quasar tie
- the current best boundary tree is /data/ipp064.0/eugene/relastro.20140923/tess.3pi.fits, but the version in the fforce.20140714 directory is OK for sas.
- the current best ubercal table is ucalqy_bigflat.fits in fforce.20140714
}}} Heather notes that I should do run.addstar.resort before doing gene's method
ipptopsps progress
I am nearly done with FW/FO stuff, the other batches have been done and tested.
Example batches that I tested:
- 9196 --> DO Batch
- 9200 --> DF Batch
- 9065 --> ST Batch
- 9067 --> P2 Batch
- 9192 --> OB Batch
I opened each batch in topcat and checked that the columns were mostly sensible and investigated 0's or -999s as necessary
DO Batch
- DiffObject
- skycellID = -1 (not sure what it should be)
- ra/dec err = -999
- qfPerfect not by filter (H: need to fix)
- ng/nr/ni/nz/ny = 0 (H: need to investigate)
DF Batch
- DiffMeta
- magSat = 0. (???)
- DiffToImage
- has 60 chips... (H: needs to select only the chips , see how Stacks do this)
- DiffDetection
- telluricExt = 0 (this is in the dvo)
- momentM3*/M4* = -999 (not in cmf)
- appFillF = -999 (not in cmf)
P2 Batch
- FrameMeta (ok!)
- ImageMeta
- magSat =0
- completMag =0
- psfModelID = -999
- Detection
- posAngle = -999
- extNSigma = -999 (H: I put this in here, but do we calculate it for camera?)
- zp changes in a funny pattern (it looks like each chip is cut into 4 quarters, each quarter a different zp)
- psfMajorFWHM = -999
- psfMinorFWHM = -999
- psfCore = -999
- apFlux/apFluxErr/appFillF = 0
OB Batch
- ObjectThin
- nStackObjectRows = 0 (not sure if this is just for this batch or for all)
- MeanObject (ok!)
ST Batch
(this batch was a lucky batch that only had one filter (near the edge) - so I only checked z filter)
- StackMeta
- magSat, completMag, astroScat,photoScat, nAstro, nPhoRef, calibmodnum = -999
- StackObjectThin
- bestDetection = -999
- StackObjectAttributes
- bestDetection = -999
- zExtNSigma = -999
- StackModelFitExp
- stackDetectRowID = -999
- bestDetection = -999
- zexpRadiusErr, zExpAbErr, zExpPhiErr, zExpCf = -999
- StackModelFitDev
- stackDetectRowID = -999
- bestDetection = -999
- zDevRadiusErr, zDevAbErr, zDevPhiErr, zDevCf = -999
- StackModelFitSer
- stackDetectRowID = -999
- bestDetection = -999
- zSerRadiusErr, zSerAbErr, zSerPhiErr, zSerCf = -999
- StackPetrosian
- stackDetectRowID = -999
- bestDetection = -999
- StackApFlx
- stackDetectRowID = -999
- bestDetection = -999
- StackApFlxEGUnc
- stackDetectRowID = -999
- bestDetection = -999
- apertures 6-10 unfilled
- StackApFlxEGCon6
- stackDetectRowID = -999
- bestDetection = -999
- apertures 6-10 unfilled
- StackApFlxEGCon8
- stackDetectRowID = -999
- bestDetection = -999
- apertures 6-10 unfilled
Things I still need to fix
- number of apertures (from 10 to 9)
- aperture metadata
Attachments (1)
- zpfor136491.png (66.6 KB ) - added by 11 years ago.
Download all attachments as: .zip
