9:30a – 12:30a
Chromatin analysis
- loading Bogdan’s black area data.
- units or normalization is off somehow. These clearly don’t line up as expected.
- Redoing the spot-processing myself. Working on F1 data (very high background, this is a bit frustrating).
- F10 data looks pretty good, low background
- see data
- continuing work on Library2 summary, see post
Tuck RAM update
I can’t turn the computer off at the moment because people are using it. I had previously booked a few hours this morning to turn the machine off and try to install the RAM. here’s what I tried during that interval:
I first installed the six new 8 GB modules in the adjacent positions of the existing six 4 GB modules. Upon booting, if I check computer properties, the system says 72 GB of RAM, 23 usable.
I then removed the 6 old 4 GB modules and installed the new 8 GB modules in their place (these memory card slots have a blue plastic trim instead of a black plastic trim like the other 12). The system still boots fine. Now it says 40 GB of RAM, 23 usable.
I will contact all the users and try to arrange an alternative time when I can freely turn the machine off to shuffle the positions of the modules if necessary and check the BIOS. If you let me know what times work for you, I’ll try to find times that work for all the other users to cease their computation and for me to be free to work on troubleshooting the RAM install.
Alright, looks like this is going to get delayed a month or more, rebooting Tuck is not acceptable. I suppose we can still stick the old DIMMs from Tuck on Cajal.
storm-control update
- debugged my new
imagewriters.pyfor STORM2. - python / numpy uses matlab style indexing for images (Height by Width), so you need (ypix,xpix) not (xpix,ypix) in reshaping arrays.
- fixed bug resulting from previous failure to rezero the average image. Now initialized as zeros.
- still need to commit my changes on STORM2 and push back to my personal branch.