trmrsh/trm-ultracam — pull request #1 by StuartLittlefair (2013-07-12 03:13:45+00:00)
Title: Devel

OK Tom,

Been struggling with this one all night. There seems to be a difference between the way overscan data is handled between the pipeline and the python module. If I grab a frame from a FFOVNC run to a ucm file, and then read in the ucm file with

frm = trm.ultracam.UCAM.rucm(file)

I get the following format string

CCD 1:
Window 1 = llx, lly = 1, 1; nx, ny = 512, 1024; xbin, ybin = 1, 1
Window 2 = llx, lly = 513, 1; nx, ny = 512, 1024; xbin, ybin = 1, 1
Window 3 = llx, lly = 1025, 1; nx, ny = 28, 1032; xbin, ybin = 1, 1
Window 4 = llx, lly = 1053, 1; nx, ny = 28, 1032; xbin, ybin = 1, 1
Window 5 = llx, lly = 1, 1025; nx, ny = 512, 8; xbin, ybin = 1, 1
Window 6 = llx, lly = 513, 1025; nx, ny = 512, 8; xbin, ybin = 1, 1

But if i read the same frame direct from the .dat file with 'trm.ucam.Rdata(datfile)(100)'

CCD 1:
Window 1 = llx, lly = 1, 1; nx, ny = 540, 1032; xbin, ybin = 1, 1
Window 2 = llx, lly = 541, 1; nx, ny = 540, 1032; xbin, ybin = 1, 1

as coded. However, if I change Raw.py to look more like the format in the ucm file, the data doesn't demux properly, and a plot looks like garbage. I'm wondering if you can fix?