...

assigned to environment variable SIT_SVN_USER.

Creating Your Own User Repository

Use the following command to create your own package:

psvn -u newpkg <my-new-package-name>

The package name should not include the "<>" above.  Once you have created your package you can check it out of the repository with:

 
svn co http://pswww.slac.stanford.edu/svn/pdsrepo/pdsrepo/<my-new-package-name>

The above would work on machines around the world if you have a SLAC "kerberos ticket".  You can see your tickets with the command "klist". You can get at ticket on systems with a "kinit" command like this:

kinit mySlacAccountName@SLAC.STANFORD.EDU  (the CAPS are required for SLAC.STANFORD.EDU!)

If you don't have a ticket, you can get readonly access to the repository like this:

svn co http://pswww.slac.stanford.edu/svn-readonly/pdsrepo/<my-new-package-name>

If you are working in a psana "test release" instead of the above, you can checkout your code with:

addpkg -u <my-new-package-name>

svn commit -m "my message describing changes" .    (note the "." at the end of the line!)

Access to users' software repository

...

• Public repository for users' code
• Main PSDM Subversion repository

Command line interface

SVN-based command-line interface is identical for both repositories. The only difference is that the key "-u" should be added to the addpkg and psvn newpkg commands for users' repository. For example,

psvn -u newpkg <my-new-package-name>

 addpkg -u <package-name>

...

Inclusion of the package in official release

Publicly available LCLS offline releases can be seen in the directory associated with $SIT_RELDIR environment variable. Inclusion in release means that the package will be compiled nightly and its modules and applications will be available by default to anyone who want to use them, with appropriate version tag. Packages from both repositories can be included in LCLS offline release system by a personal request to the release coordinator (currently Andy).

...