The following is what was done as of now regarding the BEMC status tables. Instructions can be found here

• Ran the l2status.py code provided by Alice, found the code got stuck on the following runs (still need to edit the code so to skip these runs)
  • 14137076
  • 14141047
  • 14158002
• Alice also provided the statusCheckfill2.py code.  It was ran and the output is stored in my local STAR  directory: /star/u/dolv719/BEMC_stuff.  Alice suggested that the histoPedRatio, and histoPedRatioGood be used to determine if any towers are bad.  Still need to follow up with Alice on this. 
• The final thing done at the moment was manually checking the status tables that can be found here.  6 fills were picked evenly through run13 and a table has been compiled marking which runs were bad.  Most bad towers in the pdf were plotted in red, but not all and so I added the ones that looked bad.  See the attached excel file at the bottom.
  
  • A good (0) status is marked in green, a bad (1) status is marked in red (color code)
  • If the tower was marked bad for at least half the fills the tower was considered bad for the run
  • For fill 17492 and 17534 towers 2501-2580 (status code 18) were all bad
  • Also for fill 17534 there are regions where 3 or 4 towers in a row are bad, kind of grouping pattern (status code 257).
  • Another observation is that the number of bad towers per fill increases as run 13 progesses.
  • In BEMC_status file is a list of bad towers and their status code.  Any tower id with "?" was not marked bad in the pdf, but looks bad.
• Finally I used the checkstatus code provided by Alice to compile a list of towers that should be hardcoded as bad in l2status.py.  See BEMC_hardcode.xls
  
  • If the output of status from the code was correct I marked the run not to be hardcoded.  
  • For runs that had there status code switch from good to bad, but were all clearly bad it was marked to be hardcoded out.
  • There were a few runs that I was unsure to hardcode, so I marked a "?" next to the hardcode column.