LPC Organization

Enabling: Physics Tools

LPC news and recent developments:

Sept 26, 2005:

Version 1.35 of the roadmap document is now available.

May 13, 2005:

Transparenecies for Liz's talk on the new framework and edm project, given at the general USCMS meeting is posted here for archival purposes.

February 21, 2005:

Shaun Ashby's slides from the SCRAM V1 Tutorial given at CERN. These are useful for those participating in the EDM redesign project since the EDM project uses scramv1 on SL3 machines only. Also Natalia has prepared a shorter presentation specifically for EDM developers.

August 6, 2004:

Accessing the LPC_EDM Wiki

LPC_EDM Wiki

LPC WORKING GROUPS

here

LPC Wiki Pages

A Wiki is a page automatically generated from an easily editable source, suitable for posting multi-contributor technical discussions on the web.

The following Wiki's for LPC topics exist:

LPC_EDM Wiki

LPC Documents are kept in a DocDB database.

Instructions for how to access a document, or to add or modify your own document, are here.

How to Access LPC Documents

LPC Documents are kept in a DocDB database.

Instructions for how to access a document, or to add or modify your own document, are here.

Documents from the Re-engineering Project

Ideas for RecHit redesign.

How to Access the LPC cvs Repository

To browse the contents of the CVS repository click here (select lpc in the CVS root tab).
To obtain read-only access to the LPC cvs repository (which allows you to check out and update LPC packages):

setenv CVSROOT = :pserver:anonymous@cdcvs.fnal.gov:/cvs/lpc
In your home directory, the file .cvspass must contain the line

Somebody should fill this in.
If your .cvspass file does not contain the above line, you can instead login with the password lpc .

This provides access even if the local system does not use Kerberos for secure logins.

To obtain write privilege for a specific LPC package, which goes via the CVSROOT

Somebody should fill this in

Write access to the LPC repository does require Kerberos. So if you have write privileges make sure your have a valid kerberos ticket and set:

setenv CVSROOT lpccvs@cdcvs.fnal.gov:/cvs/lpc

For any questions and to request write access please contact the LPC cvs administrators.

The LPC Packages

The LPC packages are split into three categories:

Packages in LPC-production (relatively mature) status
Packages available but not declared production
Packages which during development were in the LPC repository but which are now part of the official CMS software.

***Production-status Packages***
Package Name - - - - - - - - -	Version and Release Info - - - - - - -	Brief Description - - - - - -- - -	Getting Started and Full Documentation - - - - - - - - -
`Documents`	1.0.0	LPC Document organization	How To Use LPC's DocDB -

***Development-status Packages***
Package Name - - - - - - - - -	Version and Release Info - - - - - - -	Brief Description - - - - - -- - -	Getting Started and Full Documentation - - - - - - - - -
`Documentation`	1.0.0	Here as a sample entry	How To Use LPC's DocDB -

***CMS Packages Originally From LPC***
Package Name - - - - - - - - -	Brief Description - - - - - -- - -	Getting Started and Full Documentation - - - - - - - - -
`NoneYet`	None have done this yet	*Link to Docs would be here*

Adding to Offline Coordination Pages

The organization of the Offline Coordination web pages is intended to make it trivial to insert LPC members' additions and improvements.

The source of the pages is kept in cvs, in the WebPages subdirectory of the Documentation package. Contributers can check out that package, make changes (including adding files) locally, and check the package back in.

(We request that you use relative links only for other web pages in this package, and that you exercise each new link you have added, to see that the links all resolve properly.)

An hourly cron job will automatically pull the modified pages over to the place where the publicly accessible LPC web pages are being served. Thus the modified pages should be available to all, within one hour of the cvs check in.