WIP: Added the notebook which injects Bad Pixel Frequency Map to database.

Dear Misha and Karim,

I have added a new notebook which is supposed to analyze the FastCCD baseline as a function of time and temperature using the dark data taken in Detlab. These data were collected for 10 hours.

This notebook also computes a bad pixel frequency plot which tells us the frequency at which a pixel's signal goes beyond +/- 5 sigma away from mdian(offset) or median(noise). We intend to inject this bad pixel frequency map into the calibration database. The idea is the users can set a desired threshold on the frequency and have access to pixels that are not always bad but are only bad a certain frequency.

A few things I would like to mention are: 1- Karim is kindly making a new constant in the calibration database corresponding to the FastCCD device. I called this constant "BadPixelsFrequency", so Karim: if you could please keep the name the same, if possible, that would be truly appreciated.

2- If you run the last cell, it will not work right now because "BadPixelsFrequency" attribute does not yet exist.

3- After a discussion with Karim and later with Michele, we decided to inject into the database the bias voltage, detector integration time, detector gain, temperature and creation time from the first sequence of the first run as identifier conditions for this new constant. Please note that unlike other constants, this new constant is not computed based on one sequence of one run alone. But it is rather computed from 288 sequences of 10 runs. However, fortunately, the bias voltage, detector integration time, and detector gain are identical for all of them. The temperature varies a bit from one sequence to the next but the variation over the entire sequences is less than 1 degC, so I think if we take temperature from sequence_0 of the first run, it is fine. The only thing that remains is the creation time, of which we have 10 for the 10 runs. In other words, we have 10 creation times spanning over 10 hours. Right now, I have chosen to inject the creation time for the first run. If you think this is not a good decision, please let me know. I think if you could please set a limit on it and say if the creation time is within a time window starting from the one I inject to the database until 10 hours later, then this constant can be retrieved from the database.

Thank you all for your time. Best, Kiana