<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12"> <TITLE>RE: [Rivet] AGILe</TITLE> </HEAD> <BODY>  Hi Frank, One more question - in our first paper we separate NSD and inelastic events. Will I have to write a projection with the trigger condition? Thanks! Sparsh -----Original Message----- From: Frank Siegert [<A HREF="mailto:frank.siegert@durham.ac.uk">mailto:frank.siegert@durham.ac.uk</A>] Sent: Tue 6/15/2010 5:46 PM To: rivet@projects.hepforge.org Cc: Sparsh Navin; MR Whalley Subject: Re: [Rivet] AGILe Hi Sparsh, Sparsh Navin, Tuesday 15 June 2010: > Been looking at writing analysis code. Cool! > I am trying to adapt existing > analyses codes to my needs. I have 3 questions - > > 1. ALICE has 3 published papers with spires ID's 8625980, 8624100 and > 8479623. On the reaction data page on any of these papers, I don't > understand what P is in ETARAP(P=3). Do you have any idea? I think this is just some nomenclature to define the selection cuts. It's not very clear to me and probably also not very important, as long as you know which figure/table in the paper the HepData table corresponds to, because there you can find the proper selection definition. > 2. In some of the papers, there is data for two (or 3) different > energies, is this a problem? No, look at CDF_2002_S4796047 as an example for one analysis with multiple Ecms. > 3. The link on the top of the page for data from all tables to appear > in one file in AIDA format doesn't work for > <A HREF="http://hepdata.cedar.ac.uk/View/8625980">http://hepdata.cedar.ac.uk/View/8625980</A> and > <A HREF="http://hepdata.cedar.ac.uk/View/8624100">http://hepdata.cedar.ac.uk/View/8624100</A> while it does for the first > paper <A HREF="http://hepdata.cedar.ac.uk/View/8479623">http://hepdata.cedar.ac.uk/View/8479623</A>. However, the > individual tables are fine. Do I have to manually save them in one > file? That seems to be a bug in HepData (which I have not come across before). I am cc'ing Mike Whalley (the HepData maintainer) so that he can have a look. Cheers, Frank </BODY> </HTML>