Sortostat/Notebook: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
**Does the leak influence the timing of the events, by making the image processing take too long? (e.g. why does the timing graph get noisy after awhile?) | **Does the leak influence the timing of the events, by making the image processing take too long? (e.g. why does the timing graph get noisy after awhile?) | ||
**Is it the MATLAB thread that blows up or the LabView? | **Is it the MATLAB thread that blows up or the LabView? | ||
*output the direction of sorting to the output file | *output the direction of sorting to the output file | ||
*Make the list of experiments to evaluate the device performance limits. | *Make the list of experiments to evaluate the device performance limits. | ||
| Line 16: | Line 15: | ||
*Do fluctuations in the total cell count correlate with anything? | *Do fluctuations in the total cell count correlate with anything? | ||
*Move all the pictures from the last run to the same HD (back up the ones from the long zigzag run). | *Move all the pictures from the last run to the same HD (back up the ones from the long zigzag run). | ||
**Waiting for the new drive to come in. | |||
*Clean up the MATLAB scripts (particularly the image processing, have lots of old versions lying around). | |||
==Done== | |||
*Change the code so that when flipping based on the CFP it is the moving average that is used, rather than a single image. | |||
==References== | ==References== | ||
*[[Sortostat/Foundry report card]] - post notes on each chip fabricated so can document common failure points in fabrication to better avoid them. | *[[Sortostat/Foundry report card]] - post notes on each chip fabricated so can document common failure points in fabrication to better avoid them. | ||
Revision as of 12:34, 11 July 2007
Experiments
To Do List
- Figure out the MATLAB memory leak
- I suspect this is because I'm not closing the image files properly in the MATLAB script that runs, or it could be something more annoying.
- Does the leak influence the timing of the events, by making the image processing take too long? (e.g. why does the timing graph get noisy after awhile?)
- Is it the MATLAB thread that blows up or the LabView?
- output the direction of sorting to the output file
- Make the list of experiments to evaluate the device performance limits.
- Work on the model and compare to experimental results.
- How much faster can we drive it given the timing?
- Are there more or less cells in a sort vs a screen?
- No, looked at this before last lab meeting, but should write it up.
- Do fluctuations in the total cell count correlate with anything?
- Move all the pictures from the last run to the same HD (back up the ones from the long zigzag run).
- Waiting for the new drive to come in.
- Clean up the MATLAB scripts (particularly the image processing, have lots of old versions lying around).
Done
- Change the code so that when flipping based on the CFP it is the moving average that is used, rather than a single image.
References
- Sortostat/Foundry report card - post notes on each chip fabricated so can document common failure points in fabrication to better avoid them.
