Sortostat/Notebook: Difference between revisions
From OpenWetWare
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
*Figure out the MATLAB memory leak | *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. | **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?) | |||
*Change the code so that when flipping based on the CFP it is the moving average that is used, rather than a single image. | *Change the code so that when flipping based on the CFP it is the moving average that is used, rather than a single image. | ||
*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? | |||
==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 16:34, 7 June 2007
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?)
- Change the code so that when flipping based on the CFP it is the moving average that is used, rather than a single image.
- 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?
References
- Sortostat/Foundry report card - post notes on each chip fabricated so can document common failure points in fabrication to better avoid them.
