The STAR experiment

As RCF moves towards the Condor batch system I thought I'd compile a list of some useful commands here.  The ones with a * next to them should be run from the node on which you submitted your jobs.  The full Condor 6.8.3 manual is at

---

Starsim at PDSF seems to pick up different libraries than at rcf (I guess this is no surprise). The load of the default pythia library seem to fail for all tested library versions (SL06e, SL06f, starnew, starpro) - and it fails silently. Log file output includes a local checkout and compile of the pythia library seems to fix. Must replace the line in the kumac with the local library: with

Testing upload. Restored options (with head on shoulders).

Ok, after working on porting the BEMC webpages to Drupal over the past couple of days I have a list of features that I hope we can implement in our Drupal installation:

• Performance Optimizations:  I don't know if it's Drupal settings, PHP settings, or what, but this CMS is awfully slow at times.  I've set up a couple of Joomla installations at MIT that are much snappier.  This is the number one complaint I hear from other people.  It's going to be a running joke at EMC phone meetings before too long.
• Trash Bin:  What do I do with pages that I decide I don't want?  I don't see any way to trash them, so for the moment the BEMC subsystem page has a "Trash Bin" of it's own.  It sure would be nice if I could hide it, though.
• Authorship changes:  Sometimes I create pages as kocolosk that would probably be better off as staruser pages, but I don't see any way to change the authorship myself, so I've resorted on at least occasion to "trashing" the old page as best I could and then recreating a new page with a different author.  Very convoluted.
• Restricted viewership:  I would like to post analysis results in Drupal, but I can't figure out how to restrict my pages to logged in users.  At the moment I have a folder called drupal_pics in protected/spin that I put plots in.  Users are then required to type a password to see them, but again, this is something Drupal must be able to handle by itself.

Statistical errors from MB || JP1 || JP2 from 2005:

I re-examined the data - pythia comparison in my analysis after some good questions were raised during my preliminary result presentation at today's Spin PWG meeting. In particular, there was some concern over occasionally erratic error bars in the simulation histograms and also some questions about the shape of the z-vertex distributions.

These plots were made from 100 hijing events using perfect hits in the old three-layer IST and the HFT, but no SSD. Currently, it is not possible to make plots containing both the IST and the HFT as the bfc upgrade tags for the upgrade are upgr01, which contains the HFT and SSD but not the IST, and upgr02, which contains the HFT and IST but not the SSD.

I've included an Excel spreadsheet with currently assigned systematic errors as an attachment.