<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi - for those not at the meeting yesterday..<div> Please remember to add a ticket with the component AnalysisRoutine when you are planning on writing a Rivet routine. We don't want to be wasting time writing the same routine twice so its quite important we are all kept informed.</div><div><br></div><div>You can look at the report:</div><div>"List of Analysis Routines"<br><div>to see what routines are being worked on (this currently includes the closed tickets too, but I can change this if people want).</div><div><br></div><div>Any other tickets related to Analysis routines should continue to go under the component Analysis.</div><div><br></div><div>Cheers,</div><div>Emily.</div><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>From: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Jonathan Butterworth <<a href="mailto:jmb@hep.ucl.ac.uk">jmb@hep.ucl.ac.uk</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Date: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">7 August 2008 13:07:31 BST</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>To: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Emily Nurse <<a href="mailto:nurse@fnal.gov">nurse@fnal.gov</a>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Cc: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Andy Buckley <<a href="mailto:andy.buckley@durham.ac.uk">andy.buckley@durham.ac.uk</a>>, <a href="mailto:rivet@projects.hepforge.org">rivet@projects.hepforge.org</a></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" color="#000000" style="font: 12.0px Helvetica; color: #000000"><b>Subject: </b></font><font face="Helvetica" size="3" style="font: 12.0px Helvetica"><b>Re: [Rivet] List of Rivet routines</b></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> </div><div><br><br>Emily Nurse wrote:<br><blockquote type="cite">ok, I've made a new component (AnalysisRoutine) and a new report that selects on this component.<br></blockquote><blockquote type="cite"><a href="http://projects.hepforge.org/rivet/trac/report/9">http://projects.hepforge.org/rivet/trac/report/9</a><br></blockquote><br>great! Other people who are planning to write, or requesting routines, please add tickets using the same format /fields as Emily has used here.<br><br>Cheers,<br>Jon<br><br><blockquote type="cite"><blockquote type="cite">It might be nicer to keep them separate from normal tickets and exclude them<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">from normal views, but to refer to active tickets that affect those analyses.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Otherwise we'll never get to close analysis tickets - just move them, which is<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">a bit artificial - and the tickets will become long and full of expired<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">information.<br></blockquote></blockquote><blockquote type="cite">I can do this by actively requiring that the other reports don't list anything with AnalysisRoutine as the component, do you want me to do that?<br></blockquote><blockquote type="cite">I'd like to be able to group these by experiment, the only way I can think of implementing this without adding more custom fields is to put the expt. name in the key words of the ticket. Does anyone know of a better way than this? It would be better if it were a drop down menu but I don't want to mess with the other tickets too much.<br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite">Emily.<br></blockquote><blockquote type="cite">On 4 Aug 2008, at 12:53, Andy Buckley wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Jonathan Butterworth wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hum.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Using the ticketing system was my idea. This is supposed to be a sort of<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">to do list (at least in my understanding) so the ticketing seemed to be<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">appropriate. They can reported as tasks rather than bugs, and there are<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">then email notifications for people interested (can add themselves to<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the cc field) in a given routine etc. Plus we can use prioritisation,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">assign them to milestones/release etc etc.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">For user documentation of analyses, I think doxygen comments should be<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">used. I'd resist having a wiki page too, too many sources of<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">(potentially inconsistent) info to maintain.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Yes, I agree with that: synchronisation is best done by keeping documentation<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">close to the code. Actually, I think we should put a lot more metadata in the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">analysis classes themselves. For example, a nice feature would be for each<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">analysis to have a "long description" or comment field, in which all current<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">issues, generator settings etc. are described, which could then be queried on<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the rivetgun command line or via the API.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I would prefer to have this than either a set of always-open tickets or<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">outdated wiki pages.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I was thinking a component like Emily suggests would be good, then we<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">can set up a DB query which gives all analyses in progress or requested,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">with people assigned to them (if any) and progress/priority. And once<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">they are written, the ticket could just refer people to the doxygen page.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Does that make you happier Andy?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Okay, I'll be open minded for once and see how it pans out!<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">It might be nicer to keep them separate from normal tickets and exclude them<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">from normal views, but to refer to active tickets that affect those analyses.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Otherwise we'll never get to close analysis tickets - just move them, which is<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">a bit artificial - and the tickets will become long and full of expired<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">information.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I think another more substantial thing that would be very useful would be<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">periodically-generated plots from all Rivet analyses, available from the Web.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">But that a) requires a lot of CPU and b) is replicating a lot of JetWeb<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">functionality (has anything happened on JetWeb, by the way?) Any comments?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Andy<br></blockquote></blockquote><br>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Prof. Jonathan Butterworth, <a href="http://www.hep.ucl.ac.uk/~jmb/">http://www.hep.ucl.ac.uk/~jmb/</a> <br>Physics and Astronomy Department Tel: +44 20 7679 3444<br>University College London Gower St, London WC1E 6BT, UK<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br><br></div></blockquote></div><br></div></body></html>