Join The Crew:
Information for new team members
This page is intended to help new members of our team get up to speed quickly, to figure out where things are, and how to get computer accounts to get their work done. Please, everybody, edit accordingly to make getting started easier.
- E-Mail List: If you have not already done so, you may want to join the "technical group" e-mail list,
email@example.com. Contact Joel to get added to the list.
- Help List: there is another e-mail list for users requesting help. The address is
firstname.lastname@example.org (this replaced
email@example.com in Feb 2016, which you may still see references to). See below for how to get added to this list (if you want to be on it (or have to be on it even if you don't want to be on it)).
- Telecon: we usually have a weekly telecon, currently on Wednesdays at 10:00 CST (11:00 EST/8:00 PST) to discuss current issues and status. Anyone invloved in ELabs is welcome to attend, and developers will find it useful to keep up-to-date with the group. We use a free conference service (http://freeconferencecall.com) , but the call will be long distance, probably to Kansas or Indiana. The parameters (phone number to call and the access code) will generally be sent out to the e-mail list a day or two before the call, along for a request for agenda items, but the usual parameters may be at Conference Call. See Conference Call for instructions if you ever have to set up the call, or want to use their service for other meetings.
Where stuff is:
- Developers Notes are kept in this wiki. Once you get an account (see below) you too should help document your activities and contributions. It may help you to know that the wiki is a work in progress, so feel free to improve the documentation any way you can. (We can always revert edits if something gets screwed up.)
- Cluster machines: current assignment of machines in our cluster are on the Cluster Configuration page, along with other info about how the machines are configured and tied together. There is also a separate Cluster Ops page describing operational proceedures (how to do stuff on the cluster).
- Procedures: common operating procedures are currently described in a section of the main page called Trash.FGCSSPCFPFGCS2013SI#Proceedures. See also the ClusterOps page.
- E-Labs: Each e-Lab has a link on the front page for documentation about that e-Lab. Please feel free to create any page which is missing, and add as much documentation as you can (or at least as much as would be useful to you and others).
- Source Code: The source code for the e-Labs and the cosmics analysis tool are in a Subversion (SVN) repository kept on a machine at Fermilab. See below about getting an account, and see the page on SVN for more information about Subversion and how to use it.
As with a logbook, you can use this space to record things you need to remember, or things others would need to know if you were not around. (This is sometimes called the "hit by a bus" criterion: Write enough so that if you were hit by a bus then someone else could still do what needs to be done.)
Although our long-term goal is to be able to allow all ELabs participants (including developers) to use "single-sign-on" to do their work, we are not there yet. You will therefore need to get accounts on several different systems, as described in this section:
To be able to edit the developers' notes that you're reading now on wiki.quarknet.org, you'll need a Foswiki account. If the registration page
isn't active, contact Joel to have an account made.
As of February 2016, the e-Lab site www.i2u2.org is hosted from the Center for Research Computing at the University of Notre Dame. Instructions for obtaining the necessary accounts are found on the server access
The source code for the e-Lab web pages and the cosmic rays analysis tool is kept in a Subversion (SVN) repository at Fermilab. To be able to save whatever you are working on in the SVN repository you will need to get an account with Fermilab. To do so fill out and submit the form at https://fermi.service-now.com/new_acct_request.do
. If you need to add a sponsor name put "Marjorie Bardeen" and then let Marge know that you've applied for the account. Information on how to access the SVN repository is on a separate SVN
We now have a "bugzilla" bug tracking and ticket system (at http://bugzilla.mcs.anl.gov/i2u2/
) to keep track of software bugs, feature requests, and other issues. You'll need to create an account on that system to allow you to submit bug tickets. This account is separate from any of the other accounts above. To create an account go to http://bugzilla.mcs.anl.gov/i2u2/createaccount.cgi
and fill out the form. You'll receive an e-mail with a randomly generated password. Once you login you can change the password to whatever you want.
The Bugzilla installation was moved to bugzilla.quarknet.org on i2u2-wiki
. When i2u2-wiki
was upgraded to Ubuntu 20.04/MySQL 8 in 2020, the most recent stable version of Bugzilla at that time was incompatible with MySQL 8. We're waiting on a patched stable version of Bugzilla to reactivate it (as of Oct 2020).
Talk to Joel about getting added to the mailing list
If you are going to add things to the central calendar on Google Calendars then you will need an account with Google. This does not have to be a GMail account, it could be tied to a non-Google e-mail address. Further details are here
A guide to building new eLabs and new analyses
-- Main.EricMyers - 16 Jan 2008