Use of RunShare

The purpose of Runshare is to facilitate the sharing of process runs in order to save resources.
It has been customary that lab users allow others to join in a batch run when practical, since it causes little impact to the user. Remember that this is a two-way street: If you're going to ask others to help you, then please return the favor and let others join your runs.

To use, go to:
http://www.lelandstanfordjunior.com/eData.html
Fill out the form:

Protocol:

  1. There are two types of entries you can make: Select this first with the radio buttons at the top of the page.
  2. Select a date for your run. This is the date that the posting will expire, so if you are requesting a run, and you need it by the end of the week, select a date that is at the end of the week. You can note in the comments that your wafers might be ready sooner than the posted date. If you have a reservation already, and are posting a run that you are willing to share, post the date the run will occur. (Note that the date is used to delete expired reservations, so choose the date accordingly)
  3. Select the Type of Process: Several types of processes are listed in the list. You can choose "other" and describe in the comments if your type of run is not listed. Or choose "Any Suitable" if, for instance, you need a metal, sputtered or evaporated.
  4. Enter the name of the program or process, or the material in the Program Name or Material section. This is where protocol is important.
  5. Enter the Film Thickness of the deposition. If there are multiple layers, as in the Ti/Pt/Au example above, use the same format, eg: "200/500/1200" would indicate that the first Ti layer is 200A, the Pt layer is 500A, and the gold is 1200A. If you are posting a request, or even posting a run, you can indicate a range if desired. For instance, if in the above example, you don't care much about the thickness of the top gold layer, you could write: "200/500/800-2000"
  6. Enter the number of wafers.
  7. Enter your email. You can enter whatever email you'd like. The suggested format is to use only your SNF email (IE: coral login) as the email address, and leave off the stanford.edu part, for instance: user@snf. Another spam-resistant method is to post as: user-at-hotmail-dot-com. Currently, the database is password protected to the outside world, so the spam risk should be minimal.
  8. Enter Comments. Any other information that may be useful. Some suggestions:

Viewing the List

You can view the list of postings at:http://www.lelandstanfordjunior.com/eData.html Note that if you've made a change (posting or deletion) since you last visited, you will need to press the Reload or Refresh button in your browser to get the updated list. (Your browser caches the page and doesn't look for an update unless you tell it to).
Send comments or suggestions to ericp@snf