From chquay at MtHolyoke.edu Sun Feb 1 00:56:06 2004 From: chquay at MtHolyoke.edu (Charis Quay Huei Li) Date: Sun, 1 Feb 2004 03:56:06 -0500 (EST) Subject: reservation till 3:30am? Message-ID: plase? thanks. charis. From hendrikb at stanford.edu Sun Feb 1 09:07:56 2004 From: hendrikb at stanford.edu (Hendrik Bluhm) Date: Sun, 1 Feb 2004 09:07:56 -0800 (PST) Subject: Finishing 15 min early on Raith Message-ID: Hi Vignesh, I expect to have my sample unloaded at about 8:45. Hendrik --------------------------------------------------- Hendrik Bluhm Department of Physics Stanford University Work adress: Moler Lab Lab. for Advanced Materials Phone: (650) 723-4012 McCullough Bldg. Fax: (650) 725-2189 476 Lomita Mall Stanford, CA 94305 From vigneshg at stanford.edu Sun Feb 1 11:26:54 2004 From: vigneshg at stanford.edu (Vignesh Gowrishankar) Date: Sun, 1 Feb 2004 11:26:54 -0800 Subject: Sunday reservation 11am - 4pm Message-ID: <1075663614.401d52fe095ab@webmail.stanford.edu> Just started with the first half hour. Thanks y'all. From lsmoore at stanford.edu Sun Feb 1 16:28:27 2004 From: lsmoore at stanford.edu (Lindsay Shannon Moore) Date: Sun, 1 Feb 2004 16:28:27 -0800 Subject: sunday 3:30-8:30 please In-Reply-To: References: Message-ID: <1075681707.401d99ab4c03d@webmail.stanford.edu> i will sign them out as i think of it. please don't interrupt that time. thanks! From mtopinka at stanford.edu Sun Feb 1 21:01:14 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Sun, 01 Feb 2004 21:01:14 -0800 Subject: now(8:30pm) thru midnight 2/8 please. Thx Message-ID: <5.2.0.9.0.20040201210032.0211d888@mtopinka.pobox.stanford.edu> From mtopinka at stanford.edu Sun Feb 1 22:10:36 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Sun, 01 Feb 2004 22:10:36 -0800 Subject: stats for Raith reservations in the coming week. Message-ID: <5.2.0.9.0.20040201210401.00b6aa98@mtopinka.pobox.stanford.edu> Hi everyone. I liked and am following Dan's suggestion to compile stats on Raith usage to help us decide on a reasonable policy. I've compiled stats on the usage logged into coral as of right now for the next week from 8:30pm 2/1/2004 through 8:30pm 2/8/2004. I've also included a quick analysis of what a 10hr or 8hr cap on reservations would buy us. I wanted to get this to people so that those who are interested could become familiar with the numbers before the town-hall meeting tomorrow. By the way, just to avoid misunderstandings, an "8 or 10 hour cap / 2week on RESERVATIONS" is not the same as an "8 or 10 hour cap / 2week on USAGE". Now, no policy we come up with will be *perfect*! But, that said, I'm in favor of making an 8 hour cap with a 2 week reservation-horizon policy, because I think the numbers in this spreadsheet show that this policy would open up enough time in the reservation schedule to allow people to make reservations in a more sane fashion (ending the current every-30-minutes-reservation ridiculousness), and I believe this policy would also result in a fair allocation of hours among users. Again (sorry for repeating myself) this WILL NOT limit people to 8 hours of usage per 2 weeks. I hopefully can explain myself more fully tomorrow. If you're interested in looking at the reservation stats for the coming week, here are the different columns in the attached spreadsheet are (from left to right) ColumnA: username (I just called people UserA, UserB, UserC, etc. to keep it anonymous) ColumnB: Tot.Hours: just the total hours reserved for the coming week by that user ColumnC: #.of.reservations by each user ColumnD: average length of each reservation by that user ColumnE: minimum # of hours that would have to be opened by that user right now with a 10 hour cap. (Assuming that users simply get rid of just enough time to get under new cap) ColumnF: actual # of hours that might reasonably be expected to be opened by that user right now with a 10 hour cap (Assuming that users give up all reservations that would exceed 10hr cap, and don't expand their other ones. This is a rough estimate which uses ColumnD) ColumnG & H: same as E & F but with an 8 hour cap. I've included simple analyses (I know they're not perfect) of what the two simplest proposals for solving the time-crunch problem would probably buy us. Those two proposals are to make a 10hr cap or an 8hr cap. (See the descriptions of the columns above for the algorithm I used to get these numbers) It makes no difference to the numbers in the spreadsheet whether we allow people to reserve two weeks in advance, although I have to say that I firmly believe extending the reservation horizon out to 2 weeks while simultaneously lowering the current-reservations-cap to 10 or 8 hours would completely solve the "every-30-minutes" problem. I can explain more my reasoning on that at "town-meeting" tomorrow. -------------- next part -------------- A non-text attachment was scrubbed... Name: reservation_stats.xls Type: application/octet-stream Size: 17920 bytes Desc: not available URL: From altug at stanford.edu Mon Feb 2 00:33:06 2004 From: altug at stanford.edu (Hatice Altug) Date: Mon, 2 Feb 2004 00:33:06 -0800 Subject: Monday 12:00-8:30am on 9Feb References: <1075681707.401d99ab4c03d@webmail.stanford.edu> Message-ID: <144501c3e967$2eb4f3e0$da5540ab@hatice> thanks From hendrikb at stanford.edu Mon Feb 2 04:07:55 2004 From: hendrikb at stanford.edu (Hendrik Bluhm) Date: Mon, 2 Feb 2004 04:07:55 -0800 (PST) Subject: Open slots Message-ID: Hi, 1) I opened up 1 1/2 hrs tomorrow morning. Please leave at least the first 1/2 h to Lindsay (lsmoore). Let me know if the time would be used better if I free up the last hour rather than the first. 2) If my writes today and tomorrow are successfull, I will cancel my sessions on Wed and Thu. Hendrik --------------------------------------------------- Hendrik Bluhm Department of Physics Stanford University Work adress: Moler Lab Lab. for Advanced Materials Phone: (650) 723-4012 McCullough Bldg. Fax: (650) 725-2189 476 Lomita Mall Stanford, CA 94305 From hendrikb at stanford.edu Mon Feb 2 06:30:28 2004 From: hendrikb at stanford.edu (Hendrik Bluhm) Date: Mon, 2 Feb 2004 06:30:28 -0800 (PST) Subject: Unloading now. Done early on Raith. Message-ID: --------------------------------------------------- Hendrik Bluhm Department of Physics Stanford University Work adress: Moler Lab Lab. for Advanced Materials Phone: (650) 723-4012 McCullough Bldg. Fax: (650) 725-2189 476 Lomita Mall Stanford, CA 94305 From dwshin at stanford.edu Mon Feb 2 09:26:22 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Mon, 2 Feb 2004 09:26:22 -0800 Subject: Can I reserve 5:00 pm to 11:30 pm, next Tuesday? In-Reply-To: References: Message-ID: <1075742782.401e883e484f4@webmail.stanford.edu> Can I reserve next Tuesday (2/9/2004) from 5:00 pm to 11:30 pm? If OK with you, could you leave those blocks unbooked.... (I mean in coral tomorrow...) or if you have any concerns, could you let me know? Thank you. Sincerely, Dongwoon From dwshin at stanford.edu Mon Feb 2 09:30:13 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Mon, 2 Feb 2004 09:30:13 -0800 Subject: Sorry, I meant 2/10 Tuesday, not 2/9 (no message contents) In-Reply-To: <1075742782.401e883e484f4@webmail.stanford.edu> References: <1075742782.401e883e484f4@webmail.stanford.edu> Message-ID: <1075743012.401e892501044@webmail.stanford.edu> Sorry, I meant 2/10 Tuesday, not 2/9 Dong-Woon Shin : > Can I reserve next Tuesday (2/9/2004) from 5:00 pm to 11:30 pm? > > If OK with you, could you leave those blocks unbooked.... (I mean in > coral > tomorrow...) or if you have any concerns, could you let me know? > > Thank you. > > Sincerely, > Dongwoon > From scaccag at stanford.edu Mon Feb 2 10:16:57 2004 From: scaccag at stanford.edu (Luigi Scaccabarozzi) Date: Mon, 2 Feb 2004 10:16:57 -0800 (PST) Subject: Can I reserve 5:00 pm to 11:30 pm, next Tuesday? In-Reply-To: <1075742782.401e883e484f4@webmail.stanford.edu> Message-ID: Dong-Woon, as I understand, and as it has been working so far, you have to actually book on coral the first half hour and then send an email where you specify how long do you need the reservation to be. That's to avoid immediate "email" booking of the next few weeks. Please can someone correct me if I'm wrong? Gigi On Mon, 2 Feb 2004, Dong-Woon Shin wrote: > Can I reserve next Tuesday (2/9/2004) from 5:00 pm to 11:30 pm? > > If OK with you, could you leave those blocks unbooked.... (I mean in coral > tomorrow...) or if you have any concerns, could you let me know? > > Thank you. > > Sincerely, > Dongwoon > From mtopinka at stanford.edu Mon Feb 2 11:24:27 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Mon, 02 Feb 2004 11:24:27 -0800 Subject: Can I reserve 5:00 pm to 11:30 pm, next Tuesday? In-Reply-To: References: <1075742782.401e883e484f4@webmail.stanford.edu> Message-ID: <5.2.0.9.0.20040202112254.021d0058@mtopinka.pobox.stanford.edu> That seems to be the agreed upon etiquette at this point. So, Dong-Woon, you can have that slot if you manage to get the first half hour (at 5:00 tomorrow) booked. Good luck! -Mark At 10:16 AM 2/2/2004 -0800, Luigi Scaccabarozzi wrote: >Dong-Woon, >as I understand, and as it has been working so far, you have to >actually book on coral the first half hour and then send an email where >you specify how long do you need the reservation to be. That's to avoid >immediate "email" booking of the next few weeks. >Please can someone correct me if I'm wrong? >Gigi > >On Mon, 2 Feb 2004, Dong-Woon Shin wrote: > > > Can I reserve next Tuesday (2/9/2004) from 5:00 pm to 11:30 pm? > > > > If OK with you, could you leave those blocks unbooked.... (I mean in coral > > tomorrow...) or if you have any concerns, could you let me know? > > > > Thank you. > > > > Sincerely, > > Dongwoon > > From grupp at snowmass.Stanford.EDU Mon Feb 2 12:29:09 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Mon, 2 Feb 2004 12:29:09 -0800 (PST) Subject: reserving thru 130, thanks, dan Message-ID: --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From mtopinka at stanford.edu Mon Feb 2 13:47:52 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Mon, 02 Feb 2004 13:47:52 -0800 Subject: Town Hall Meeting at 2:00 Message-ID: <5.2.0.9.0.20040202134719.0239f600@mtopinka.pobox.stanford.edu> A last minute reminder to everybody- Raith town hall meeting at 2:00pm in CISX101, last I heard. From mtopinka at stanford.edu Mon Feb 2 14:00:39 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Mon, 02 Feb 2004 14:00:39 -0800 Subject: plz now (2:00pm) thru 5:00pm next Monday Thanks! Message-ID: <5.2.0.9.0.20040202140016.0238b6a0@mtopinka.pobox.stanford.edu> From hendrikb at stanford.edu Mon Feb 2 16:58:23 2004 From: hendrikb at stanford.edu (Hendrik Bluhm) Date: Mon, 2 Feb 2004 16:58:23 -0800 (PST) Subject: Thu morning free Message-ID: --------------------------------------------------- Hendrik Bluhm Department of Physics Stanford University Work adress: Moler Lab Lab. for Advanced Materials Phone: (650) 723-4012 McCullough Bldg. Fax: (650) 725-2189 476 Lomita Mall Stanford, CA 94305 From cumings at stanford.edu Mon Feb 2 17:33:20 2004 From: cumings at stanford.edu (John Cumings) Date: Mon, 02 Feb 2004 17:33:20 -0800 Subject: 2-9 until 7:30 thx. Message-ID: <200402030133.i131XKLY014325@elaine21.Stanford.EDU> ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ From goldhaber-gordon at stanford.edu Mon Feb 2 18:07:50 2004 From: goldhaber-gordon at stanford.edu (David Goldhaber-Gordon) Date: Mon, 2 Feb 2004 18:07:50 -0800 Subject: Stanford Raith website Message-ID: <000b01c3e9fa$8699fb80$46d642ab@stanford.edu> Hi all, As I mentioned during the Town Hall meeting today, we have at Stanford a collaborative website for sharing info about the Raith. This includes instructions, tips, process info, results of writes, etc. The URL is: http://elrey.stanford.edu:8080/Raith Anyone can read the site. It's also very easy to edit it in a standard web browser, and you're all welcome and indeed encouraged to edit it, adding your own insights. However, you do need a username and password for editing. Please do not share these with those who are not qualified on the Raith system. Username: wraith Password: nazgul I strongly encourage you to visit the site, use the material there, and add your own. In particular, please add process info for different materials, and results, especially pictures, from your writes. We all have a lot to learn from each other. If you are concerned about making your results world-viewable, let me know. I would be happy to set up a related site that requires a Stanford-only password for not just writing but also reading. Best, David ---------------------------------------------------------------------------- David Goldhaber-Gordon goldhaber-gordon at stanford.edu Assistant Professor of Physics davidg at post.harvard.edu Stanford University (permanent forwarding) www.goldhaber-gordon.com (650) 725-2047 (lab) (650) 724-3709 (office) Address for letters or packages: Administrative Associate: David Goldhaber-Gordon Roberta Edwards Geballe Laboratory for Advanced Materials McCullough, Rm. 338 McCullough Building, Room 346 Phone: (650) 723-8028 476 Lomita Mall Fax: (650) 724-3681 Stanford, CA 94305-4045 email: redward at stanford.edu From cumings at stanford.edu Mon Feb 2 18:39:36 2004 From: cumings at stanford.edu (John Cumings) Date: Mon, 02 Feb 2004 18:39:36 -0800 Subject: clarification & proposal Message-ID: <200402030239.i132daND018357@elaine2.Stanford.EDU> All, When I say that I want my session to go until 7:30, I mean the next user may sign up for the time slot marked "19:30", which begins at 7:30 PM. I propose that we stick to this protocol: when the next user may sign up for time beginning at XX:XX, we say in the email that we want the sesion to go "until XX:XX", just to make it fair & clear for all. This is just to help keep things smooth until better rules & protocols are in place. Cheers, -John ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ From scaccag at stanford.edu Mon Feb 2 20:01:39 2004 From: scaccag at stanford.edu (Luigi Scaccabarozzi) Date: Mon, 2 Feb 2004 20:01:39 -0800 (PST) Subject: raith: please res. until 7.30AM TUESDAY 2/9 Message-ID: From hendrikb at stanford.edu Mon Feb 2 22:39:25 2004 From: hendrikb at stanford.edu (Hendrik Bluhm) Date: Mon, 2 Feb 2004 22:39:25 -0800 (PST) Subject: Canceled res tomorrow 5:30 am Message-ID: Sorry for the late notice. Sample turned out to be sufficiently dead to make further processing pointless. Hendrik --------------------------------------------------- Hendrik Bluhm Department of Physics Stanford University Work adress: Moler Lab Lab. for Advanced Materials Phone: (650) 723-4012 McCullough Bldg. Fax: (650) 725-2189 476 Lomita Mall Stanford, CA 94305 From chquay at MtHolyoke.edu Tue Feb 3 10:37:09 2004 From: chquay at MtHolyoke.edu (Charis Quay Huei Li) Date: Tue, 3 Feb 2004 13:37:09 -0500 (EST) Subject: res. cancelled friday morning In-Reply-To: Message-ID: 2:30-5am. charis. From grupp at snowmass.Stanford.EDU Tue Feb 3 10:49:48 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Tue, 3 Feb 2004 10:49:48 -0800 (PST) Subject: making res til 1 on 2/10? Message-ID: i'm not sure if this is within the new system, so i am willing to remove later if needed. but it is a time slot i need. no email yet on the new system. thanks, dan --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From dwshin at stanford.edu Tue Feb 3 11:09:43 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Tue, 3 Feb 2004 11:09:43 -0800 Subject: making res til 11:30 pmon 2/10 (from 5:00 pm) ? In-Reply-To: References: Message-ID: <1075835383.401ff1f7106f1@webmail.stanford.edu> Sure... and I would like to reserve until 11:30 pm from 5:00 pm on 2/10, right after James as stated earlier... Good luck on your writing. - Dongwoon ?? Dan Grupp : > i'm not sure if this is within the new system, so i am willing to > remove > later if needed. but it is a time slot i need. no email yet on the new > system. > thanks, > dan > > -------------------------------------------------------------------------- - > Dr. Daniel Grupp, Visiting Scholar > Center for Integrated Systems > Stanford University > Stanford, CA 94305 > (650) 724-6911 > FAX: 723-4659 > -------------------------------------------------------------------------- - > > From dwshin at stanford.edu Tue Feb 3 17:33:06 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Tue, 3 Feb 2004 17:33:06 -0800 Subject: res til 11:30 pm on 2/10 In-Reply-To: <1075835383.401ff1f7106f1@webmail.stanford.edu> References: <1075835383.401ff1f7106f1@webmail.stanford.edu> Message-ID: <1075858386.40204bd23e2e5@webmail.stanford.edu> Reservation right on coral. 5:00 pm until 11:30 pm on 2/10 Thank you. Sincerely, Dongwoon Dong-Woon Shin : > > Sure... > > and I would like to reserve until 11:30 pm from 5:00 pm on 2/10, > right after James as stated earlier... > > Good luck on your writing. > > - Dongwoon > > ?? Dan Grupp : > > > i'm not sure if this is within the new system, so i am willing to > > remove > > later if needed. but it is a time slot i need. no email yet on the new > > system. > > thanks, > > dan > > > > > -------------------------------------------------------------------------- > - > > Dr. Daniel Grupp, Visiting Scholar > > Center for Integrated Systems > > Stanford University > > Stanford, CA 94305 > > (650) 724-6911 > > FAX: 723-4659 > > > -------------------------------------------------------------------------- > - > > > > > > > From dwshin at stanford.edu Tue Feb 3 23:36:30 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Tue, 3 Feb 2004 23:36:30 -0800 Subject: DONE: res til 11:30 pm, 2/10, NEXT user please reserve... In-Reply-To: <1075858386.40204bd23e2e5@webmail.stanford.edu> References: <1075835383.401ff1f7106f1@webmail.stanford.edu> <1075858386.40204bd23e2e5@webmail.stanford.edu> Message-ID: <1075880189.4020a0fe0109b@webmail.stanford.edu> I am done with the reservation. Thank you. Sincerely, Dongwoon Dong-Woon Shin : > > Reservation right on coral. > 5:00 pm until 11:30 pm on 2/10 > > Thank you. > > Sincerely, > Dongwoon From ajavey at stanford.edu Wed Feb 4 00:35:57 2004 From: ajavey at stanford.edu (Ali Javey) Date: Wed, 4 Feb 2004 00:35:57 -0800 (PST) Subject: reserving Wednesday 00:00 - 04:00 Message-ID: I've got the first 1/2 hour block. Will be very appreciated if you can please leave that slut to me. Thanks.... Ali From ACREMANN at SSRL.SLAC.STANFORD.EDU Wed Feb 4 05:03:36 2004 From: ACREMANN at SSRL.SLAC.STANFORD.EDU (ACREMANN at SSRL.SLAC.STANFORD.EDU) Date: Wed, 04 Feb 2004 05:03:36 -0800 (PST) Subject: Want to extend my reservation till 07:30 on Fri, Feb 11. Message-ID: <01L66X5SYRC292C1YN@SSRL.SLAC.STANFORD.EDU> Hi Please let me extend my reservation on Friday, Feb 11 til 06:30am. Thanks a lot Yves From sandrew at stanford.edu Wed Feb 4 05:09:07 2004 From: sandrew at stanford.edu (Scott D. Andrews) Date: Wed, 4 Feb 2004 05:09:07 -0800 (PST) Subject: Raith free until 7:30 Message-ID: Similar computer crash issues as last time. Had to give up this attempt. -Scott From hungtao at stanford.edu Wed Feb 4 08:06:43 2004 From: hungtao at stanford.edu (Hung-Tao Chou) Date: Wed, 4 Feb 2004 08:06:43 -0800 Subject: 2/11 til 10:30 thx Message-ID: <1075910803.40211893cbcdd@webmail.stanford.edu> 2/11 6:30 to 10:30 Thank you -Hungtao From cumings at stanford.edu Wed Feb 4 11:22:07 2004 From: cumings at stanford.edu (John Cumings) Date: Wed, 04 Feb 2004 11:22:07 -0800 Subject: 2-11 until 13:00 Thanks! Message-ID: <200402041922.i14JM7sL007255@elaine18.Stanford.EDU> ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ From kcrozier at stanford.edu Wed Feb 4 13:31:54 2004 From: kcrozier at stanford.edu (Kenneth Brian Crozier) Date: Wed, 04 Feb 2004 13:31:54 -0800 Subject: RAITH, 2-11, 13:00-21:00 Thanks! In-Reply-To: <200402041922.i14JM7sL007255@elaine18.Stanford.EDU> Message-ID: <5.2.0.9.2.20040204133016.011f1100@kcrozier.pobox.stanford.edu> hello, it would be great if I could reserve the raith 13:00-21:00 on 2/11/04 (wednesday next week). Thanks ! Ken Crozier From mtopinka at stanford.edu Wed Feb 4 20:59:56 2004 From: mtopinka at stanford.edu (Mark Allen Topinka) Date: Wed, 4 Feb 2004 20:59:56 -0800 Subject: Raith free 2.5hours (7:30am-10:00am) tomorrow :( Sorry! Message-ID: <1075957196.4021cdcc43a22@webmail.stanford.edu> I just am not going to be able to complete everything I need to complete by tomorrow morning. I'm very sorry for the late cancellation, and I hope somebody is able to snap it up!! -Mark From lsmoore at stanford.edu Wed Feb 4 21:39:53 2004 From: lsmoore at stanford.edu (Lindsay Moore) Date: Wed, 04 Feb 2004 21:39:53 -0800 Subject: reservation until 1am 2/11/04-2/12/04 In-Reply-To: <1075957196.4021cdcc43a22@webmail.stanford.edu> Message-ID: <5.1.1.5.2.20040204213209.045ea880@lsmoore.pobox.stanford.edu> thanks! From chquay at MtHolyoke.edu Thu Feb 5 01:33:39 2004 From: chquay at MtHolyoke.edu (Charis Quay Huei Li) Date: Thu, 5 Feb 2004 04:33:39 -0500 (EST) Subject: reservation til 7am Message-ID: thanks! charis. From edo at stanford.edu Thu Feb 5 10:17:32 2004 From: edo at stanford.edu (Edo Waks) Date: Thu, 5 Feb 2004 10:17:32 -0800 Subject: reservation on 2-12 until 4 Message-ID: Thanks, Edo Waks From grupp at snowmass.Stanford.EDU Thu Feb 5 11:17:29 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Thu, 5 Feb 2004 11:17:29 -0800 (PST) Subject: i will be competing for the slot after Edo at 4pm today. how about you? Message-ID: i am NOT reserving this slot, but i would like to know if i will have (and who you are!) any competition starting at 4 today. Less stressful if i know i am not going to face a battle! THanks, DAn --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From lsmoore at stanford.edu Thu Feb 5 11:25:48 2004 From: lsmoore at stanford.edu (Lindsay Moore) Date: Thu, 05 Feb 2004 11:25:48 -0800 Subject: reservation until 1am 2/11/04-2/12/04 In-Reply-To: <5.1.1.5.2.20040204213209.045ea880@lsmoore.pobox.stanford.e du> References: <1075957196.4021cdcc43a22@webmail.stanford.edu> Message-ID: <5.1.1.5.2.20040205112447.01abee00@lsmoore.pobox.stanford.edu> Dan. please remove your name from my reservation slot 21:30-1am 2/11-2/12 right now. thanks. lindsay At 09:39 PM 2/4/2004 -0800, Lindsay Moore wrote: >thanks! From grupp at snowmass.Stanford.EDU Thu Feb 5 11:52:23 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Thu, 5 Feb 2004 11:52:23 -0800 (PST) Subject: filling in your requested time. Message-ID: Gang, I think we need to have a rule about when you need to fill in your time after you request it. It would be great if especially for overnight we don't have to fill it in right away. That is, we still have to be there at 2 am to get the first half hour, and send out an email reserving the slot we want, but it would be nice to be able to go home, and fill it in in the morning. I want to put a limit on this, because sometimes times may be abandonned. Further, ya just gotta fill it in, or we have to scour thru emails to figure out if time is really free. I suggest that by noon that day the times must be entered, or it's fair game. we could use a similar idea for during the day, so we don't have to tend coral. For this is suggest that we fill it in by the end of our requested slot, no following grace period (or not much!). So i make a reservaion, starting at 11, requesting til 4, and i make sure that by 4 i have filled it all in. So i only need to be there (on coral) at the beginning and end, at 11 and 4. your thoughts? Regards, Dan ps - i want to applaud our community for having such a respectful culture! Turns out the STS community is worried about imposing self-regulation, because many feel it wouldn't work, with not enough self-restraint and respect amongst the users. --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From cumings at stanford.edu Thu Feb 5 12:17:30 2004 From: cumings at stanford.edu (John Cumings) Date: Thu, 05 Feb 2004 12:17:30 -0800 Subject: filling in your requested time. In-Reply-To: Your message of "Thu, 05 Feb 2004 11:52:23 PST." Message-ID: <200402052017.i15KHUPl024506@elaine3.Stanford.EDU> All, I agree that given the current system of emailing, it can be annoying to look at coral and sift through emails to figure out what time is open. We all know that this is temporary and that users will soon be allowed to put their whole sessions on Coral, but in the meantime we all need to be considerate about filling out our time and not stealing other people's time. Despite this, I think rules like Dan is proposing are annoying, especially when self-policed in a community setting. I suggest a simple grace period of 24 hrs. Simple. If people forget (even with a 24 hr grace period), they should be politely reminded or otherwise contacted BEFORE their time is stolen. -John ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ In message you write: >Gang, > I think we need to have a rule about when you need to fill in your time >after you request it. It would be great if especially for overnight we >don't have to fill it in right away. That is, we still have to be there at >2 am to get the first half hour, and send out an email reserving the slot >we want, but it would be nice to be able to go home, and fill it in in the >morning. I want to put a limit on this, because sometimes times may be >abandonned. Further, ya just gotta fill it in, or we have to scour thru >emails to figure out if time is really free. I suggest that by noon that >day the times must be entered, or it's fair game. > we could use a similar idea for during the day, so we don't have to >tend coral. For this is suggest that we fill it in by the end of our >requested slot, no following grace period (or not much!). So i make a >reservaion, starting at 11, requesting til 4, and i make sure that by 4 i >have filled it all in. So i only need to be there (on coral) at the >beginning and end, at 11 and 4. > your thoughts? >Regards, >Dan > >ps - i want to applaud our community for having such a respectful culture! >Turns out the STS community is worried about imposing self-regulation, >because many feel it wouldn't work, with not enough self-restraint and >respect amongst the users. > >--------------------------------------------------------------------------- >Dr. Daniel Grupp, Visiting Scholar >Center for Integrated Systems >Stanford University >Stanford, CA 94305 >(650) 724-6911 >FAX: 723-4659 >--------------------------------------------------------------------------- > From mtopinka at stanford.edu Thu Feb 5 16:04:07 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Thu, 05 Feb 2004 16:04:07 -0800 Subject: i will be competing for the slot after Edo at 4pm today. how about you? In-Reply-To: Message-ID: <5.2.0.9.0.20040205160253.00b6fe08@mtopinka.pobox.stanford.edu> Dan- I was planning on trying for the 4:00 slot as well. I'm not militant about it, how long is your planned write? Mine is 3 hours. -Mark At 11:17 AM 2/5/2004 -0800, Dan Grupp wrote: >i am NOT reserving this slot, but i would like to know if i will have (and >who you are!) any competition starting at 4 today. Less stressful if i >know i am not going to face a battle! >THanks, >DAn > >--------------------------------------------------------------------------- >Dr. Daniel Grupp, Visiting Scholar >Center for Integrated Systems >Stanford University >Stanford, CA 94305 >(650) 724-6911 >FAX: 723-4659 >--------------------------------------------------------------------------- From ajavey at stanford.edu Thu Feb 5 16:09:03 2004 From: ajavey at stanford.edu (Ali Javey) Date: Thu, 5 Feb 2004 16:09:03 -0800 (PST) Subject: i will be competing for the slot after Edo at 4pm today. how about you? In-Reply-To: <5.2.0.9.0.20040205160253.00b6fe08@mtopinka.pobox.stanford.edu> Message-ID: I was too going to sign up, but will try later on instead.... I need 3-4 hours. Cheers, Ali On Thu, 5 Feb 2004, Mark Topinka wrote: > Dan- I was planning on trying for the 4:00 slot as well. I'm not militant > about it, how long is your planned write? Mine is 3 hours. -Mark > > At 11:17 AM 2/5/2004 -0800, Dan Grupp wrote: > >i am NOT reserving this slot, but i would like to know if i will have (and > >who you are!) any competition starting at 4 today. Less stressful if i > >know i am not going to face a battle! > >THanks, > >DAn > > > >--------------------------------------------------------------------------- > >Dr. Daniel Grupp, Visiting Scholar > >Center for Integrated Systems > >Stanford University > >Stanford, CA 94305 > >(650) 724-6911 > >FAX: 723-4659 > >--------------------------------------------------------------------------- > From mtopinka at stanford.edu Thu Feb 5 16:29:10 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Thu, 05 Feb 2004 16:29:10 -0800 Subject: i will be competing for the slot after Edo at 4pm today. how about you? In-Reply-To: References: <5.2.0.9.0.20040205160253.00b6fe08@mtopinka.pobox.stanford.edu> Message-ID: <5.2.0.9.0.20040205162651.02950cc8@mtopinka.pobox.stanford.edu> Ali- go ahead if you want. I mean, personally, I do not like setting a precedent of sending out emails to the raith group saying "I'm going to sign up for time X". So let's just not do it anymore, ok everyone? That's my vote atleast. -Mark At 04:09 PM 2/5/2004 -0800, Ali Javey wrote: >I was too going to sign up, but will try later on instead.... I need 3-4 >hours. > >Cheers, >Ali > > >On Thu, 5 Feb 2004, Mark Topinka wrote: > > > Dan- I was planning on trying for the 4:00 slot as well. I'm not militant > > about it, how long is your planned write? Mine is 3 hours. -Mark > > > > At 11:17 AM 2/5/2004 -0800, Dan Grupp wrote: > > >i am NOT reserving this slot, but i would like to know if i will have (and > > >who you are!) any competition starting at 4 today. Less stressful if i > > >know i am not going to face a battle! > > >THanks, > > >DAn > > > > > >----------------------------------------------------------------------- > ---- > > >Dr. Daniel Grupp, Visiting Scholar > > >Center for Integrated Systems > > >Stanford University > > >Stanford, CA 94305 > > >(650) 724-6911 > > >FAX: 723-4659 > > >----------------------------------------------------------------------- > ---- > > From mtopinka at stanford.edu Thu Feb 5 16:57:17 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Thu, 05 Feb 2004 16:57:17 -0800 Subject: 4pm-7pm Thurs 2/12/2002 please thanks! Message-ID: <5.2.0.9.0.20040205165651.0299ac20@mtopinka.pobox.stanford.edu> From grupp at snowmass.Stanford.EDU Thu Feb 5 19:33:33 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Thu, 5 Feb 2004 19:33:33 -0800 (PST) Subject: res 4 hours 7-11, thx. Message-ID: --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From jhemanth at stanford.edu Fri Feb 6 00:19:21 2004 From: jhemanth at stanford.edu (Hemanth Jagannathan) Date: Fri, 6 Feb 2004 00:19:21 -0800 Subject: 11pm-5am Thurs 2/12/2004 - Thanks In-Reply-To: <5.2.0.9.0.20040205165651.0299ac20@mtopinka.pobox.stanford.edu> Message-ID: <000001c3ec89$ecceb3f0$05bb0c80@JAGANNATHANPC> Hi Everyone, I have started my reservation from 11pm on 2/12/04 and will need time till 5am 2/13. Thanks Regards, Hemanth Jagannathan PhD Candidate Department of Electrical Engineering Stanford University, CA -------------- next part -------------- An HTML attachment was scrubbed... URL: From cvenky at stanford.edu Fri Feb 6 06:34:14 2004 From: cvenky at stanford.edu (Venkatesh Hanumant Rao Chembrolu) Date: Fri, 6 Feb 2004 06:34:14 -0800 Subject: Friday, Feb 13 5am-10am Message-ID: <1076078054.4023a5e607224@webmail.stanford.edu> Hi All, I am trying to reserve next friday 5am to 10am. Thanks. Venkatesh From mtopinka at stanford.edu Fri Feb 6 22:51:31 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Fri, 06 Feb 2004 22:51:31 -0800 Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 Message-ID: <5.2.0.9.0.20040206221406.021fa638@mtopinka.pobox.stanford.edu> New Raith Reservation Policy Semi-Final Proposal Going Into Effect 12:01am 2/10/2004 Hi everyone. This email summarizes the consensus that was reached at the end of Raith townhall meeting (on 2/2/2004) about a new Raith reservation policy which will go into effect 12:01am Tuesday, February 10th. James asked me to summarize and send this out to the group since he has been working extremely hard this week on Raith maintenance, training, and other issues and hasn't had time to finish off his Raith-Townhall-meeting-minutes email yet. We are hoping that by sending this email now, people who have questions and/or concerns about these new policies will have enough time to try and talk to somebody who was at the Raith townhall meeting on 2/2/2004 and/or to email the raith at snf list. The basic policy is pretty simple: ============================= At any given moment in time, you may be signed up for no more than 8 total hours on the Raith. (Note please! This is a *reservation* cap, not a *usage* cap- as soon as you finish a given reservation, that time comes off your total and you may sign up for any available block) one exception to the 8 hour cap: if you are somebody who absolutely needs longer than 8 hours per write-session, you may sign up for ONE slot at a time which is up to 10 hours long. (to clarify with some examples: two 4h sessions are ok, one 10h session is ok, but two separate 5h slots are Not ok.) No going over these caps by even a half an hour without talking to James first, please- the entire offending reservation will be removed. ============================= Also: in conjunction to this new reservation cap, we are hoping to open up the coral reservation window to two weeks, but John Shott is still working on that option. The hope is that this will help to eliminate the 7*24hours advance 30-minute slot signup problem. John is also trying to get the coral system to allow us to make reservations which *begin* at 7*24 hours in advance as opposed to *ending* at 7*24 hours in the future- this would eliminate the need for the current practice of sending out emails to the list each time you start a new reservation. (although, hopefully, with the 8 hour cap and a 2-week reservation window, the entire 30-minute pounce problem will no longer be a problem). A side note: I would respectfully suggest that we not snap-judge the success or failure of this new policy right away, because the first week is going to be seriously messed up no matter what we do due to the fact that 4 entire days are being pre-reserved for planned maintenance on the Raith. We're basically thinking of trying this policy at least until the middle of March to see how it works. A final note: we are in the process of assembling a list of "raith experts" which we will post next to the Raith with email addresses and phone numbers so that anybody (beginners OR experts) can call a fellow student Raith user with questions about problems they're having, or also with questions about their gdsII patterns, optimal writing voltages, and aperatures. Thanks for reading this! I for one am optimistic that this will turn out to be a pretty good working solution for a Very popular resource. Have a great weekend! -Mark From vigneshg at stanford.edu Fri Feb 6 23:08:24 2004 From: vigneshg at stanford.edu (Vignesh G) Date: Fri, 06 Feb 2004 23:08:24 -0800 Subject: Sunday reservation removed In-Reply-To: <5.2.0.9.0.20040206221406.021fa638@mtopinka.pobox.stanford. edu> Message-ID: <5.1.1.5.2.20040206230637.00b81518@vigneshg.pobox.stanford.edu> Sunday reservation from 11:00 to 15:30 removed.... just don't kill each other when pouncing for it. - Vignesh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lgx at stanford.edu Fri Feb 6 23:40:24 2004 From: lgx at stanford.edu (Guanxiong Li) Date: Fri, 6 Feb 2004 23:40:24 -0800 Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 References: <5.2.0.9.0.20040206221406.021fa638@mtopinka.pobox.stanford.edu> Message-ID: <001f01c3ed4d$a6131900$27a70c80@stanford.edu> I have a question on the reservation policy. I do not understand the examples in the policy. Why are two seperate 5h slots not allowed? Since they are seperate, the two reservations must be made at two seperate moments in time. Each 5h slot is ok with the 8h cap regulation. Could you explain it? Thanks. -lgx ----- Original Message ----- From: "Mark Topinka" To: Cc: "John Shott" Sent: Friday, February 06, 2004 10:51 PM Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 > New Raith Reservation Policy Semi-Final Proposal Going Into Effect 12:01am > 2/10/2004 > > Hi everyone. > This email summarizes the consensus that was reached at the end of > Raith townhall meeting (on 2/2/2004) about a new Raith reservation policy > which will go into effect 12:01am Tuesday, February 10th. James asked me > to summarize and send this out to the group since he has been working > extremely hard this week on Raith maintenance, training, and other issues > and hasn't had time to finish off his Raith-Townhall-meeting-minutes email > yet. We are hoping that by sending this email now, people who have > questions and/or concerns about these new policies will have enough time to > try and talk to somebody who was at the Raith townhall meeting on 2/2/2004 > and/or to email the raith at snf list. > > The basic policy is pretty simple: > ============================= > At any given moment in time, you may be signed up for no more than 8 total > hours on the Raith. (Note please! This is a *reservation* cap, not a > *usage* cap- as soon as you finish a given reservation, that time comes off > your total and you may sign up for any available block) > one exception to the 8 hour cap: if you are somebody who absolutely needs > longer than 8 hours per write-session, you may sign up for ONE slot at a > time which is up to 10 hours long. (to clarify with some examples: two 4h > sessions are ok, one 10h session is ok, but two separate 5h slots are Not > ok.) No going over these caps by even a half an hour without talking to > James first, please- the entire offending reservation will be removed. > ============================= > > Also: in conjunction to this new reservation cap, we are hoping to open up > the coral reservation window to two weeks, but John Shott is still working > on that option. The hope is that this will help to eliminate the 7*24hours > advance 30-minute slot signup problem. John is also trying to get the > coral system to allow us to make reservations which *begin* at 7*24 hours > in advance as opposed to *ending* at 7*24 hours in the future- this would > eliminate the need for the current practice of sending out emails to the > list each time you start a new reservation. (although, hopefully, with the > 8 hour cap and a 2-week reservation window, the entire 30-minute pounce > problem will no longer be a problem). > > A side note: I would respectfully suggest that we not snap-judge the > success or failure of this new policy right away, because the first week is > going to be seriously messed up no matter what we do due to the fact that 4 > entire days are being pre-reserved for planned maintenance on the > Raith. We're basically thinking of trying this policy at least until the > middle of March to see how it works. > > A final note: we are in the process of assembling a list of "raith experts" > which we will post next to the Raith with email addresses and phone numbers > so that anybody (beginners OR experts) can call a fellow student Raith user > with questions about problems they're having, or also with questions about > their gdsII patterns, optimal writing voltages, and aperatures. > > Thanks for reading this! I for one am optimistic that this will turn out > to be a pretty good working solution for a Very popular resource. Have a > great weekend! -Mark > From sandrew at stanford.edu Sat Feb 7 15:08:53 2004 From: sandrew at stanford.edu (Scott D. Andrews) Date: Sat, 7 Feb 2004 15:08:53 -0800 (PST) Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 In-Reply-To: <001f01c3ed4d$a6131900$27a70c80@stanford.edu> Message-ID: Hi Guanxiong, You are right that each of the two separate 5 hour reservations must be made at separate times and in theory are allowed, but only if you have competed the first before making the second one. For example, if on Sunday I make a 5 hour reservation for Monday and then another 5 hour reservation for Wednesday, my total future time is 10 hours, which exceeds the total allowed reservation limit (8 hours combined for two or more sessions). However, if on Sunday I make a 5 hour reservation for Monday and complete it before making another 5 hour reservation for Wednesday, then this is fine. In both instances, the actual time used is identical. However, in the first instance, there is a point in time, on Sunday, where I have reserved the Raith for more than 8 future hours. However, in the second case, on Sunday I have reserved 5 future hours, and on Tuesday I have also only 5 future hours. At no time have do I have more than 8 hours of reserved time pending. Does this help clarify? If not, please write the list again until we all have the same understanding of the new policy. -Scott From ajavey at stanford.edu Sat Feb 7 15:24:33 2004 From: ajavey at stanford.edu (Ali Javey) Date: Sat, 7 Feb 2004 15:24:33 -0800 (PST) Subject: reservation removed 7-10 pm Message-ID: my last night run did not come out well. i was suppose to do another step on it today... ali From mtopinka at stanford.edu Sat Feb 7 16:38:13 2004 From: mtopinka at stanford.edu (Mark Topinka) Date: Sat, 07 Feb 2004 16:38:13 -0800 Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 In-Reply-To: References: <001f01c3ed4d$a6131900$27a70c80@stanford.edu> Message-ID: <5.2.0.9.0.20040207161050.0215ceb0@mtopinka.pobox.stanford.edu> Thanks to Guanxiong for the question, and thanks to Scott for the answer. I just wanted to follow up Scott's excellent explanation with what is perhaps a clearer statement of the "reservation cap" - it's hard to anticipate all the questions and issues that are going to come up, but we're all doing our best here to come up with a policy that is simple and clear and which the whole community can work with and hopefully be happy with. The goal of the policy is to make sure that all users get a fair chance to use the Raith, while making sure at the same time that the Raith never sits idle simply because an inefficient/broken reservation policy. The basic proposed policy is this: you may have up to a TOTAL of 8 hours reserved (in as many separate blocks as you want) at any given time on coral. The one exception we agreed to make to this rule for users who need longer single-write times: IF you are willing to have ONLY ONE reservation at a time on coral, you may make that reservation for up to 10 hours. Stated again in hopefully clear terms: ~ users who want to have 2 or more future reservations on coral: never more than 8 TOTAL HOURS of coral reservations in the coming 2 weeks ~ users who are willing to have only 1 future reservation on coral: never more than one (and only one) 10 HOUR reservation in the coming 2 weeks. a key thing to remember is that the "2 week" window is always moving, counting from the current time, NOT from Sunday or Monday or some fixed day of the week. this policy is open to discussion and tweaking/improving and changing, of course, but first of all, does everybody understand the proposed reservation policy? -Mark At 03:08 PM 2/7/2004 -0800, Scott D. Andrews wrote: >Hi Guanxiong, > >You are right that each of the two separate 5 hour reservations must be >made at separate times and in theory are allowed, but only if you have >competed the first before making the second one. > >For example, if on Sunday I make a 5 hour reservation for Monday and then >another 5 hour reservation for Wednesday, my total future time is 10 >hours, which exceeds the total allowed reservation limit (8 hours combined >for two or more sessions). However, if on Sunday I make a 5 hour >reservation for Monday and complete it before making another 5 hour >reservation for Wednesday, then this is fine. In both instances, the >actual time used is identical. However, in the first instance, there is a >point in time, on Sunday, where I have reserved the Raith for more than 8 >future hours. However, in the second case, on Sunday I have reserved 5 >future hours, and on Tuesday I have also only 5 future hours. At no time >have do I have more than 8 hours of reserved time pending. Does this help >clarify? If not, please write the list again until we all have the same >understanding of the new policy. > >-Scott From arvisun at stanford.edu Sat Feb 7 16:42:15 2004 From: arvisun at stanford.edu (arvind sundaramurthy) Date: Sat, 7 Feb 2004 16:42:15 -0800 Subject: Reservation Cancelled Message-ID: <05c201c3eddc$661d2540$cd5640ab@arvind> Cancelled the Raith reservation Sun 3:30am-11:00am. Sorry for the late notice. arvind -------------- next part -------------- An HTML attachment was scrubbed... URL: From shott at snf.stanford.edu Sun Feb 8 11:19:31 2004 From: shott at snf.stanford.edu (John Shott) Date: Sun, 08 Feb 2004 11:19:31 -0800 Subject: PLEASE READ: New Raith Reservation Policy Semi-Final Proposal Going Into Effect 2/10/2004 In-Reply-To: <5.2.0.9.0.20040206221406.021fa638@mtopinka.pobox.stanford.edu> References: <5.2.0.9.0.20040206221406.021fa638@mtopinka.pobox.stanford.edu> Message-ID: <40268BC3.7060600@snf.stanford.edu> Mark and the rest of the Raith community: Again, I applaud your efforts to come up with some reservation guidelines that will, hopefully, maximize use of the Raith and avoid hogging problems. I promised that I would see if I could make some changes to Coral after soliciting feedback from the rest of the SNF community. I did receive a certain amount of negative feedback related to the initial proposal of pushing out the reservation horizon to 14 days and changing the rule so that the start time, rather than the end time, has to fall withing the reservation horizon. The primary fear is that these rules with encourage hogging on other machines and could, particularly in the case of the stsetch, result in everything being booked 24x14. The other argument, that does warrant consideration, is the fact that things are sufficiently variable in the research environment, particularly with unscheduled equipment downtime, that it is risky to open up the reservation horizon too far ... it may result in an unacceptably high fraction of cancelled or unused reservations. While I think that some of their fears may be unfounded and, if hogging occurs, they need to come up with community-based guidelines for those machines, I've decided that it is best to make the following compromise in the proposed changes to Coral. (1) I plan to push the reservation horizon to 10 days ... better than the current 7, but less than the initially discussed 14. However, I see no reason that this conflicts seriously with the proposed reservation guidelines ... even though it doesn't allow reservations made in days 11-14. (2) I do plan to change the rule so that the START of a reservation falls within the reservation horizon. This will, I think, be a big benefit for the raith community (and for stsetch) by allowing each reservation to be a usable length. You've already implemented guidelines to avoid hogging ... and I'm hopeful that the ststech community will follow your lead. I've tested these changes in our development environment and set it up so that the production Coral servers will restart with this behavior very close to 12:01 a.m. on Tuesday morning. Thanks to all of you for your inputs on this matter, John From cumings at stanford.edu Tue Feb 10 11:18:44 2004 From: cumings at stanford.edu (John Cumings) Date: Tue, 10 Feb 2004 11:18:44 -0800 Subject: cancel 2/11 10:30-1:00 Message-ID: <200402101918.i1AJIi2G019323@elaine35.Stanford.EDU> All, I had charging problems yesterday that I need to address before my next session. The problems shouldn't affect other users, but I'm forced to cancel my session tomorrow. -John ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ From jwc at snf.stanford.edu Tue Feb 10 19:16:54 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 10 Feb 2004 19:16:54 -0800 Subject: Minutes - Ebeam Town Meeting held on February 2, 2004 Your comments please. Message-ID: <40299EA6.6040009@snf.stanford.edu> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Ebeam_Town_Meeting_Minutes_February_2_2004.doc Type: application/msword Size: 32256 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RAITH EBEAM TEAMS AND CHAMPIONS.doc Type: application/msword Size: 32256 bytes Desc: not available URL: From lsmoore at stanford.edu Wed Feb 11 13:34:57 2004 From: lsmoore at stanford.edu (Lindsay Moore) Date: Wed, 11 Feb 2004 13:34:57 -0800 Subject: cancelled 9-2 tonight In-Reply-To: <200402112045.i1BKjjDp010612@smtp3.Stanford.EDU> Message-ID: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> also, whatever list raith-pcs at snf.stanford.edu is, it does not send email to the whole raith list. here is the info from charis: 1) Beam current low and fluctuating *a lot*. Last user (John Paul) records 30pm at 30 micron aperture (compared to 140 usuall). I got 63 +/- 5. At 120 micron aperture,current was 1.252nA and decreased by 0.01 nA over a five minute period. I noticed from the logbook that the current has been steadily decreasing over the past 2 days. 2) Column not moving. After write, joystick did not move column. Nor did software. I managed to 'fix' this by turning off and and on the laser stage control. I suspect that the column may not have moved at all during the write, i.e. only one writefield was written over and over again. John Paul, have you developed your write? Did it look like (2) hapened for you also? Charis. and james: Greetings: The beam current values (BEAM I) have been falling consistently as the 10 and 30 um apertures are becoming blocked with hydrocarbons during the writes. This is normal and is to be expected especially considering the usage we have on the system. Currently the beam current for the 10 um aperture is 50% of when the aperture disk was new. Currently the beam current for the 30 um aperture is 60 % of when the aperture disk was new. 50 % of new maximum is the breakpoint to trigger the PM request. As planned and previously announced, we will be doing a column clean with aperture replacement PM including a NEW FE-gun tip replacement this next weekend. We will be down Friday 10 AM through late Tuesday afternoon. No access no use during this period. 40 hour bake out has been requested and will be done concurrent with the Monday Holiday. The system will be requalified for performance and imaging resolution before releasing it back to users. Please schedule your work accordingly. The report of the stage freeze is the first reported in some time... we will monitor the situation. If you observe this give time for all macro and other operations to be completed then attempt to move the stage a mm or more using the Stage control. If this still does work press the STOP SIGN in the Stage control window and it will stop all pending operations and release the XYZ axis's. Back to green light mode... writes performed last night by dwshin came ot very nice. Thank you, JWC and hatice: For 30 micron aperture from 11:00 am to 12:30, current changed from from 56pA to 63, 68, 113, 128, 110. It does not stabilize, it inreases and decreases randomly. From shott at snf.stanford.edu Wed Feb 11 13:52:38 2004 From: shott at snf.stanford.edu (John Shott) Date: Wed, 11 Feb 2004 13:52:38 -0800 Subject: cancelled 9-2 tonight In-Reply-To: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> References: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> Message-ID: <402AA426.8040904@snf.stanford.edu> Lindsay: Every piece of equipment has a *-pcs mailing list ... but you are correct that not everyone is subscribed to or receives the traffic on that list. pcs stands for Problems/Comments/Shutdowns and is the mailing list which is used to notify the maintenance staff and engineers on each piece of equipment that there is a problem or shutdown condition. When they clear or resolve a problem or shutdown, their response also goes to the appropriate *-pcs list. Because the content of these lists is viewable ... either on the snf equipment "Mailing list archive" page or in the Coral maintenance client itself (under the tab labelled "Maintenance") if people wish to view it, we concluded that we didn't need to send the e-mail traffic of the *-pcs lists to all qualified users of each piece of equipment. (I'm actually subscribed to all of the lists ... and I can tell you that it is a lot of messages and most of them aren't terribly informative other than they let me know that something is broken or that something is fixes). So, that's the story on the *-pcs at snf.stanford.edu mailing lists ... John From dwshin at stanford.edu Wed Feb 11 13:57:28 2004 From: dwshin at stanford.edu (Dong-Woon Shin) Date: Wed, 11 Feb 2004 13:57:28 -0800 Subject: cancelled 9-2 tonight : Beam current In-Reply-To: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> References: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> Message-ID: <1076536648.402aa5480aefb@webmail.stanford.edu> Hi. I also found beam current fluctuating when I was measuring the faraday cup last night. I think it moved from 0.68-1.02 nA af first. (usu. 1.42) It became stablized after couple of measurements. I moved the stage to other positions, came back to the faraday cup and remeasured. Beam current was staying the same. However the value stayed low. I hope it can be resolved after the bake as James suggested. - Dongwoon ?? Lindsay Moore : > also, whatever list raith-pcs at snf.stanford.edu is, it does not send email > > to the whole raith list. > > > > here is the info from charis: > 1) Beam current low and fluctuating *a lot*. Last user (John Paul) > records > 30pm at 30 micron aperture (compared to 140 usuall). I got 63 +/- 5. At > 120 > micron aperture,current was 1.252nA and decreased by 0.01 nA over a five > > minute period. I noticed from the logbook that the current has been > steadily decreasing over the past 2 days. 2) Column not moving. After > write, joystick did not move column. Nor did software. I managed to 'fix' > > this by turning off and and on the laser stage control. I suspect that > the > column may not have moved at all during the write, i.e. only one > writefield > was written over and over again. > John Paul, have you developed your write? Did it look like (2) hapened > for > you also? Charis. > > > and james: > Greetings: > The beam current values (BEAM I) have been falling consistently as the 10 > > and 30 um apertures are becoming blocked with hydrocarbons during the > writes. This is normal and is to be expected especially considering the > usage we have on the system. > Currently the beam current for the 10 um aperture is 50% of when the > aperture disk was new. > Currently the beam current for the 30 um aperture is 60 % of when the > aperture disk was new. > 50 % of new maximum is the breakpoint to trigger the PM request. As > planned > and previously announced, we will be doing a column clean with aperture > replacement PM including a NEW FE-gun tip replacement this next weekend. > We > will be down Friday 10 AM through late Tuesday afternoon. No access no > use > during this period. 40 hour bake out has been requested and will be done > > concurrent with the Monday Holiday. > The system will be requalified for performance and imaging resolution > before releasing it back to users. Please schedule your work > accordingly. > The report of the stage freeze is the first reported in some time... we > will monitor the situation. If you observe this give time for all macro > and > other operations to be completed then attempt to move the stage a mm or > more using the Stage control. If this still does work press the STOP SIGN > > in the Stage control window and it will stop all pending operations and > release the XYZ axis's. > Back to green light mode... writes performed last night by dwshin came ot > > very nice. > Thank you, > JWC > > and hatice: > For 30 micron aperture from 11:00 am to 12:30, current changed from from > > 56pA to 63, 68, 113, 128, 110. It does not stabilize, it inreases and > decreases randomly. > > From chquay at MtHolyoke.edu Wed Feb 11 14:04:21 2004 From: chquay at MtHolyoke.edu (Charis Quay Huei Li) Date: Wed, 11 Feb 2004 17:04:21 -0500 (EST) Subject: raith res cancelled 2-6am tomorrow In-Reply-To: <1076536648.402aa5480aefb@webmail.stanford.edu> Message-ID: no point trying to write with beam as it is...maybe if we all cancel james can start maintainence early? charis From kcrozier at stanford.edu Wed Feb 11 14:08:45 2004 From: kcrozier at stanford.edu (Kenneth Brian Crozier) Date: Wed, 11 Feb 2004 14:08:45 -0800 Subject: current Raith reservation (13:00-21:00) cancelled Message-ID: <5.2.0.9.2.20040211140556.011feac0@kcrozier.pobox.stanford.edu> hi, due to beam current fluctuations I am cancelling my current reservation (13:00-21:00 today). James mentioned that he might use this time to work on the machine, but given that the time slot is so long, you might like to talk to him if you would like to use the machine. The time slot might be useful if you have some work that will not be affected by strong fluctuations in the current. thanks, Ken From jhemanth at stanford.edu Wed Feb 11 14:17:02 2004 From: jhemanth at stanford.edu (Hemanth Jagannathan) Date: Wed, 11 Feb 2004 14:17:02 -0800 Subject: Raith Reservation cancelled - 11pm to 5am In-Reply-To: Message-ID: <000001c3f0ec$c7788ba0$07b80c80@JAGANNATHANPC> I agree with Charis, no point in writing when the beam is not stable. I too am canceling my reservation on starting Thursday 11pm and ending 5am in the hope that the maintenance can start early. Hemanth Jagannathan PhD Candidate Department of Electrical Engineering Stanford University, CA -----Original Message----- From: Charis Quay Huei Li [mailto:chquay at MtHolyoke.edu] Sent: Wednesday, February 11, 2004 2:04 PM To: raith at snf.stanford.edu Subject: raith res cancelled 2-6am tomorrow no point trying to write with beam as it is...maybe if we all cancel james can start maintainence early? charis From johnpaul at stanford.edu Wed Feb 11 14:50:15 2004 From: johnpaul at stanford.edu (John Paul Strachan) Date: Wed, 11 Feb 2004 14:50:15 -0800 (PST) Subject: cancelled 9-2 tonight In-Reply-To: <5.1.1.5.2.20040211133145.01c0d298@lsmoore.pobox.stanford.edu> Message-ID: Howdy, I think I got lucky and did not have problem 2) reported by Charis, although we did have the fluctuating beam current problem. But we just read the current frequently to get the proper dose. I developed my wafer and it looked very good across the whole wafer - so it did not just write and re-write the same field as may have happened to Charis. If James is agreeable to the idea, I suggest we follow Charis' suggestion and open up time so that maintenance can be performed early. -John Paul On Wed, 11 Feb 2004, Lindsay Moore wrote: > also, whatever list raith-pcs at snf.stanford.edu is, it does not send email > to the whole raith list. > > > > here is the info from charis: > 1) Beam current low and fluctuating *a lot*. Last user (John Paul) records > 30pm at 30 micron aperture (compared to 140 usuall). I got 63 +/- 5. At 120 > micron aperture,current was 1.252nA and decreased by 0.01 nA over a five > minute period. I noticed from the logbook that the current has been > steadily decreasing over the past 2 days. 2) Column not moving. After > write, joystick did not move column. Nor did software. I managed to 'fix' > this by turning off and and on the laser stage control. I suspect that the > column may not have moved at all during the write, i.e. only one writefield > was written over and over again. > John Paul, have you developed your write? Did it look like (2) hapened for > you also? Charis. > > > and james: > Greetings: > The beam current values (BEAM I) have been falling consistently as the 10 > and 30 um apertures are becoming blocked with hydrocarbons during the > writes. This is normal and is to be expected especially considering the > usage we have on the system. > Currently the beam current for the 10 um aperture is 50% of when the > aperture disk was new. > Currently the beam current for the 30 um aperture is 60 % of when the > aperture disk was new. > 50 % of new maximum is the breakpoint to trigger the PM request. As planned > and previously announced, we will be doing a column clean with aperture > replacement PM including a NEW FE-gun tip replacement this next weekend. We > will be down Friday 10 AM through late Tuesday afternoon. No access no use > during this period. 40 hour bake out has been requested and will be done > concurrent with the Monday Holiday. > The system will be requalified for performance and imaging resolution > before releasing it back to users. Please schedule your work accordingly. > The report of the stage freeze is the first reported in some time... we > will monitor the situation. If you observe this give time for all macro and > other operations to be completed then attempt to move the stage a mm or > more using the Stage control. If this still does work press the STOP SIGN > in the Stage control window and it will stop all pending operations and > release the XYZ axis's. > Back to green light mode... writes performed last night by dwshin came ot > very nice. > Thank you, > JWC > > and hatice: > For 30 micron aperture from 11:00 am to 12:30, current changed from from > 56pA to 63, 68, 113, 128, 110. It does not stabilize, it inreases and > decreases randomly. > > From edo at stanford.edu Wed Feb 11 17:15:12 2004 From: edo at stanford.edu (Edo Waks) Date: Wed, 11 Feb 2004 17:15:12 -0800 Subject: cancelled 2-12 8:00 - 4:00 Message-ID: <1076548512.402ad3a00cdd2@webmail.stanford.edu> will wait until RAITH service is complete. Edo Waks From jwc at snf.stanford.edu Thu Feb 12 13:22:02 2004 From: jwc at snf.stanford.edu (James Conway) Date: Thu, 12 Feb 2004 13:22:02 -0800 Subject: Beam Currents observed to be consistent today. PM downtime starts at 12 NOON. Message-ID: <402BEE7A.9030701@snf.stanford.edu> Greetings: I was unable to recreate the circumstances that resulted in the erratic beam currents that were reported by users yesterday. MEASURED IN SPOT MODE ON THE STAGE FARADAY CUP: 30 um aperture == 0.151 nA 30 measurements 10 um aperture == 0.020 na. 10 measurements This was measured repeatable over a two hour period and no changes were observed. All seems good on the system from these test and imaging on the LEO was excellent resolving features to about 12 nm. Tomorrow Michael Santomango from LEO will arrive to perform a complete annual PM on the LEO column about noon. Users are asked to yield access to him upon his arrival and assist him any way you can to complete the PM. We will then bakeout the column for 40 hours and through the entire holiday weekend. Tuesday we will realign the column, mag. amplifiers, stigmator controls and address anything else that surfaces at that time. WE hope that we can hand off the system to the next user (pcatryss:: Peter Catryssee late in the afternoon Tuesday and my reservation after his on coral is to allow him time to write if we extend into his reservation slot. I will be away from the lab from now until Tuesday but available by cell phone. Thank you for your support! James Conway From cumings at stanford.edu Tue Feb 17 12:56:20 2004 From: cumings at stanford.edu (John Cumings) Date: Tue, 17 Feb 2004 12:56:20 -0800 Subject: user grupp overbooked Message-ID: <200402172056.i1HKuKG0025684@elaine35.Stanford.EDU> Just a friendly reminder, of course! ;) I think its good to keep these things in the public. If people think this is in really good/bad taste, please let me know. (privately, if you want) -John ------------------------------------------------------------ John Cumings cumings at stanford.edu Postdoctoral Scholar Physics Department Stanford University office (650) 725-1025 lab (650) 725-2047 fax (650) 724-3681 Geballe Laboratory for Advanced Materials 239 McCullough Building 476 Lomita Mall Stanford, CA 94305-4045 ------------------------------------------------------------ From jwc at snf.stanford.edu Tue Feb 17 15:59:20 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 17 Feb 2004 15:59:20 -0800 Subject: Shutdown raith 2004-02-17 15:42:09: RAITH will continue downtime through THURSDAY NOON. Message-ID: <4032AAD8.5010603@snf.stanford.edu> Greetings: The Raith system will remain down through Thursday Noon, while we effect repairs to the gun section and rebake. The FE-Gun was experiencing arcing on turn on and we had to break vacuum for inspection and repair to the EHT extractor contact pin. Please adjust your reservation schedules accordingly... Yours, James Conway From grupp at snowmass.Stanford.EDU Tue Feb 17 19:49:10 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Tue, 17 Feb 2004 19:49:10 -0800 (PST) Subject: 24 hr rule! Re: user grupp overbooked In-Reply-To: <200402172056.i1HKuKG0025684@elaine35.Stanford.EDU> Message-ID: I booked a lovely spot (around 3 am tomorrow) just today! This was within our 24 hour rule. I suggest putting in the project line of a reservation "24 hr" when booking these in the future to avoid confusion. thanks, dan On Tue, 17 Feb 2004, John Cumings wrote: > Just a friendly reminder, of course! ;) > > I think its good to keep these things in the public. > > If people think this is in really good/bad taste, please let me know. > (privately, if you want) > > -John > > ------------------------------------------------------------ > John Cumings > cumings at stanford.edu > Postdoctoral Scholar > Physics Department > Stanford University > > office (650) 725-1025 > lab (650) 725-2047 > fax (650) 724-3681 > > Geballe Laboratory for Advanced Materials > 239 McCullough Building > 476 Lomita Mall > Stanford, CA 94305-4045 > ------------------------------------------------------------ > --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From jwc at snf.stanford.edu Wed Feb 18 18:22:07 2004 From: jwc at snf.stanford.edu (James Conway) Date: Wed, 18 Feb 2004 18:22:07 -0800 Subject: 24 hr rule! Re: user grupp overbooked In-Reply-To: References: Message-ID: <40341DCF.4080100@snf.stanford.edu> What 24 hour rule?!!!! If the system is not booked or in use I would expect someone to use it. Still need to keep reservations within limits -- but it there is not a reservation you can go an use it anytime it is free. RSVP JWC Dan Grupp wrote: >I booked a lovely spot (around 3 am tomorrow) just today! This was within >our 24 hour rule. I suggest putting in the project line of a reservation >"24 hr" when booking these in the future to avoid confusion. > >thanks, >dan > >On Tue., 17 Feb. 2004, John Cumings wrote: > > > >>Just a friendly reminder, of course! ;) >> >>I think its good to keep these things in the public. >> >>If people think this is in really good/bad taste, please let me know. >>(privately, if you want) >> >>-John >> >>------------------------------------------------------------ >> John Cumings >> cumings at stanford.edu >> Postdoctoral Scholar >> Physics Department >> Stanford University >> >> office (650) 725-1025 >> lab (650) 725-2047 >> fax (650) 724-3681 >> >> Geballe Laboratory for Advanced Materials >> 239 McCullough Building >> 476 Lomita Mall >> Stanford, CA 94305-4045 >>------------------------------------------------------------ >> >> >> > >--------------------------------------------------------------------------- >Dr. Daniel Grupp, Visiting Scholar >Center for Integrated Systems >Stanford University >Stanford, CA 94305 >(650) 724-6911 >FAX: 723-4659 >--------------------------------------------------------------------------- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Thu Feb 19 16:48:18 2004 From: jwc at snf.stanford.edu (James Conway) Date: Thu, 19 Feb 2004 16:48:18 -0800 Subject: Raith is coming back up. Specific limits of operations apply through noon tomorrow. README!!! Message-ID: <40355952.4040109@snf.stanford.edu> Hello Raith Users: The PM has been completed. We just finished adjustments and alignments and LEO will return tomorrow to perform a final checkout with me and do additional alignments. The system is coming back up and on line for users WITH THE FOLLOWING RESTRICTIONS through noon Friday: 1. The FE-GUN is NOT to be run higher than 10 keV -- whatsoever. We have just brought up the new tip and it is being run in. We have optimized the emission and it is set at the factory test bed conditions. Emission is remarkably higher than when we replaced the apertures last April! :-) This is a somewhat fragile state and the run in will allow the tip to gently burn off any asperities on the tip surface and form a nice emissive surface by allowing the ZrO coating to form a uniform film over the tip's surface. 2. All resist and materials placed into the system must be softbaked at temperture greater than 150 degrees Celsius. Several users have had variances from me to use samples that had been baked at 90, 125, and 140 degrees Celsius. Those variances have been hereby revoked and you will have to see me about how to vacuum bake your samples. Why: I noted from data in the logbook that the problems with beam instability occurred after users using lower bake temperatures on their resist have been on the system. This was also evidenced by the very rapid decrease in beam current for specific apertures these users had been using. Likely the materials were still out-gassing solvents and this added to the hydrocarbon load on the system. Now that we have a new clean column we wish to maintain cleanliness of the column and develop appropriate methods to ensure only fully cured resist and materials are introduced into the system. We have a vacuum bake oven that we can bring on-line for your use. 3. Until the return of LEO tomorrow we wish to idle the system with the EHT ON and the acceleration voltage set to 1 keV. After your run and unload you can logon the LEO and raith as user: test_user - passwd: test and set the gun to 1 keV. The beam should be left unblanked and let it expose onto the stage anywhere off a sample. Leo will perform additional fine tuning of the mag amplifiers and recheck all stigmator centering functions and together we will to the final checkout tomorrow. 4. Gloves On for everything you touch going into the system -- of course. 5. Users are requested to report all errors encountered from either the RAITH SW or the windows OS. I will continue efforts to qualify the system this evening and tomorrow. So far the system looks really nice and 'bright' compared to before. 30 um aperture = 0.238 nA 20 um aperture = 0.117 nA. At 10 keV, 13 mm WD, I resolved a 2.5 nm space on a Au on carbon resolution sample. This is superb and we all should strive to maintain cleanliness of our samples and everything we introduce into the RAITH system. All it takes is a fingerprint or some uncured resist and we will loose this nice resolution. This should get us all off to a great start and I look forward to hearing about some nice write results in coming weeks. Thank you for your support! James Conway -------------- next part -------------- An HTML attachment was scrubbed... URL: From hungtao at stanford.edu Thu Feb 19 22:56:19 2004 From: hungtao at stanford.edu (Hung-Tao Chou) Date: Thu, 19 Feb 2004 22:56:19 -0800 Subject: time free tomorrow 6-10am (2/20) Message-ID: <1077260179.4035af93d8d39@webmail.stanford.edu> I used the open slot tonight, though I have problem imaging with the Inlens detector (10keV, 30um aperture). The beam current is low too (0.130nA) -hungtao From jwc at snf.stanford.edu Fri Feb 20 11:20:02 2004 From: jwc at snf.stanford.edu (James Conway) Date: Fri, 20 Feb 2004 11:20:02 -0800 Subject: Shutdown raith: Gun problems -- Bake out likely will be repeated... Message-ID: <40365DE2.4000605@snf.stanford.edu> Greetings, Problems were encountered with the FE-Gun emission almost as soon as we began writing on the system yesterday evening. Beam I was reduced by 50% is just two hours of write time. It may have been a mistake on my part for opening system access to users until the FE-tip had run in for a suitable period of time before running it in write mode. I had wanted to get you all back on the system ASAP. Likely we will need to repeat some of the PM items to eliminate contamination in the gun area, bake the system out over the weekend, and then set up and run in the FE-tip again. I have placed the Raith system into RED light mode and there will likely be no access through next Tuesday afternoon. I will immediately post to the list if this situation changes so leave your reservation in place on CORAL and check for green or yellow light status later today. I am sorry if you were impacted negatively by the current situation. Thank you, James Conway -------- Original Message -------- Subject: Shutdown raith 2004-02-20 09:27:08: Gun problems Bake out likely will be repeated... Date: Fri, 20 Feb 2004 09:27:09 -0800 From: jwc at snf.stanford.edu To: raith-pcs at snf.stanford.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Fri Feb 20 17:41:38 2004 From: jwc at snf.stanford.edu (James Conway) Date: Fri, 20 Feb 2004 17:41:38 -0800 Subject: READ ME: Users are responsible for their enables and disables of equipment on CORAL Message-ID: <4036B752.10900@snf.stanford.edu> Ladies and Gentlemen: This last month I have brought to the attention of a number of lab members working in the Ebeam Lab the necessity of being sure to enable on CORAL your own log in name and account for accesses to all equipment at SNF. This is particularly evident when a user neglects to enable over another persons login as they hand off the system to the next user. Today I was forced to give one lab member a written warning and probation action for a period of one month. There are also two other lab members who have a verbal warning given since the beginning of the year. This behavior is unfair to the others lab users whom are carefully planning their research to stay below or within the monthly caps, and it is against SNF and NSF policies on system access at our facility. Finally it creates more work for SNF staff to clean up after these oversights. Users are individually responsible for their enables and disables of equipment on CORAL and failure to do so will result in a verbal warning on the first event and a written warning with probation on the second event. Failure to enable over other users during this probation period will result in escalation of this probation action up to and including suspension of lab privileges at SNF. Please be sure to enable and disable on CORAL for all of your SNF system accesses. Thank you for your support! James Conway From jwc at snf.stanford.edu Fri Feb 20 18:25:05 2004 From: jwc at snf.stanford.edu (James Conway) Date: Fri, 20 Feb 2004 18:25:05 -0800 Subject: RAITH UPDATE 20-FEB-2004:1830 System off line through Monday afternoon. Message-ID: <4036C181.6020209@snf.stanford.edu> Greetings Raith Users: The Raith150 will be off line and not available for use through Monday afternoon. We hope that adjustments we made today to the FE-gun will result in improved emission values and that the vacuum in the gun section will come down significantly over the weekend. We have the beam up and idling at 1 kV. We are sorry for these inconveniences and the disruption to your work schedule plans. Thank you for your support! James Conway From vigneshg at stanford.edu Sun Feb 22 18:16:48 2004 From: vigneshg at stanford.edu (Vignesh G) Date: Sun, 22 Feb 2004 18:16:48 -0800 Subject: Tue 8:30 pm reservation removed Message-ID: <5.1.1.5.2.20040222181623.022e02a8@vigneshg.pobox.stanford.edu> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Vignesh G. Shankar PhD Candidate in Materials Science and Engineering Stanford University -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From jwc at snf.stanford.edu Mon Feb 23 17:18:45 2004 From: jwc at snf.stanford.edu (James Conway) Date: Mon, 23 Feb 2004 17:18:45 -0800 Subject: RAITH is up and ready for your use! Message-ID: <403AA675.8060404@snf.stanford.edu> Greetings: Beam Current and emission levels have stabilized after running in the FE-gun over the weekend. Gun Vacuum is normal at 1.9 E -009 Torr. System vacuum 1.2 E -006 Torr. Adjustments and calibrations: * We checked and adjusted the three magnification amplifiers and checked the stigmator centering functions for each aperture. * I rehomed and calibrated the X-Y-Z laser controlled stage and reset the positions of the faraday cup holes for 'on holder' and 'on stage'. * I saved the gun alignment and stigmator settings for 10 kEV 30 um aperture at 5.00 mm (4.995 mm). So you can accept these values when you are starting up the system and you will be able to rapidly get to focus and stigmation necessary to write a dot for additional focusing. * This afternoon I wrote several patterns to aid in qualification of this tools for min. feature size and stitching. I will inspect this sample tomorrow -- next user please unload for me. * Please soft bake all materials going into the system. * Through Noon tomorrow lets please keep the Acceleration Voltage to less than 10 keV. The first ramps to 30 keV should be done in 500 Volts steps once above 10 keV. Once we have run in the FE-Gun for the better part of the the week we should be able to operate at any acceleration voltage ramp from ) to 0.3 to 30 keV. Beam I values: 30 um aperture = 0.164 nA. 10 um aperture = 0.020 nA Resolution is excellent and will examine and measure the Prickly Au resolution target the next time I am on the system. Thank you for your support! James Conway -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Mon Feb 23 17:23:16 2004 From: jwc at snf.stanford.edu (James Conway) Date: Mon, 23 Feb 2004 17:23:16 -0800 Subject: Dirk Englund is next on RAITH... please unload my sample after it finishes writing at about 1800 hours Message-ID: <403AA784.5020403@snf.stanford.edu> Greetings: Dirk Englund is scheduled next on RAITH... please unload my sample after it finishes writing at about 1800 hours. I am running the qualification test and it is about half way finished as of now. (1722 hours )Please let the run complete. Expect it to finish sometime between 1800 and 1845 hours. There are about 200 elements to be written in the write. Please unload my 10 X 10 mm sample and place it into the small holder and into my dry box on the upper right hand side. Thank you, JWC From jwc at snf.stanford.edu Tue Feb 24 09:43:21 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 24 Feb 2004 09:43:21 -0800 Subject: Seminar: Resists for nanoimprint lithography and SU-8 by Microresist Technology GmbH. Message-ID: <403B8D39.9050200@snf.stanford.edu> Greetings, Thought you all might be interested in this presentation. JWC -------- Original Message -------- Subject: Seminar: Resists for nanoimprint lithography and SU-8 Date: Mon, 23 Feb 2004 23:47:47 -0800 From: Beth Pruitt To: labmembers at snf.stanford.edu,kennygroup at micromachine.stanford.edu, pruittlab at lists.stanford.edu,santiagogroup at microfluidics.stanford.edu, microheat at lists.Stanford.EDU,Olav Solgaard , Mahnaz Mansourpour , Nick Melosh ,Curt Frank , Stacey Bent SPECIAL SEMINAR on Ultrathick and Ultrathin resists TUESDAY Feb 24 4pm in CISX Auditorium Photoresists for nanoimprint lithography and Processing of thick SU-8 visitor Dr. Freimut Reuther of micro resist technology (mrt) GmbH will discuss the following: Overview on polymers for nanoimprint lithography (NIL) of (characteristics, behaviour, basic processing considerations) Overview on high thickness positive tone photoresists Purpose and benefits of IR baking of high thickness photoresists and baking examples including positive photoresists and SU-8 SNF recently obtained EV nanimprint lithography equipment and several labmembers have been using SU-8 for mixed applications with varying results. If you have questions or are thinking of using these materials, please attend this seminar and discuss with our visitor from mrt in Berlin. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Tue Feb 24 10:01:07 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 24 Feb 2004 10:01:07 -0800 Subject: Please welcome the RAITH Group VIII onto the system. Message-ID: <403B9163.1070801@snf.stanford.edu> An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Tue Feb 24 10:15:39 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 24 Feb 2004 10:15:39 -0800 Subject: PROPOSAL: Please identify your raith discussion by Thread in Subject line. Message-ID: <403B94CB.6000802@snf.stanford.edu> An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Tue Feb 24 13:09:09 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 24 Feb 2004 13:09:09 -0800 Subject: READ ME: CURRENT RAITH RESERVATION AND USAGE POLICY Message-ID: <403BBD75.8050202@snf.stanford.edu> Greetings Raith Community: Thank you for your input and participation in the Ebeam Town Meeting we held February 2, 2004. Here is the final version of the Reservation and System Usage policy based on your inputs. I hope that all users will see this change as an improvement from the past policy that was in place. We all agreed to try out this policy out and discuss further refinements needed at our next Ebeam Town Meeting. This meeting is scheduled for March 15, 2004 at 2 - 4 PM, CIS 101. Current RAITH 150 Reservations Policy: 1. Reservation limit of 8 hours per rolling 10 day reservation window on the Coral Reservation System. The reservation horizon was increased from 7 days to 10 days on Coral to allow you a longer window to make reservations. 2. Minimum of a four hour reservation slot, or you should 'Share the Ride' with other users within your CORAL reservation. i.e., No half hour reservation games allowed or tolerated! Not necessary to petition the Raith list for each of your sessions! 3. Longer reservation needed than the normal 8 hour session: You may have one reservation only of up to 10 hours maximum if you have no other reservations on the RAITH Coral system in a rolling two week period. You must have approval from James Conway if you desire a session longer than 10 hours, and you will then not be able to make an additional reservation for a two week period after that reserved session is completed. This is meant to meet the needs of users with special writing needs or circumstances only. Note: This policy continues to be under review and may be modified in the future as the need presents itself. 4. Reservations start (rather than end) within the reservation horizon. This change in particular, is designed to avoid the "30 minute roulette" that labmembers wishing to reserve the raith and the stsetch have been forced to play. 5. We have abandoned the concept of 'prime time' and 'non-prime time' hours. The Lab operates 24/7... 6. First Come First Serve -- You must use your reservation before making a new reservation on the Coral system. Raith System Usage Policy: 1. No System Usage Limit: While we have specific limits to RAITH Coral reservations, we do not have a limit on the system utilization if there are no other users working on or reserved for the system. I expect the system to be utilized 100% of the time. Users are asked to make the hand off between users as smooth as possible. It is suggested you check in with the previous user a short time before your session to aid in communications and the system hand off to reduce the unload / load exchange interval time. 2. Grace Period: Users are expected to start and end your writing sessions within 15 minutes of the scheduled time slot. If you are having problems, or encountered difficulties during your write, which may require for you to extend into the next user's session you are expected to make an attempt to inform the next user within a hour of the hand off time. You must gain their permission to extend into their session. If you don't get permission or cannot complete the EBL task -- you are expected to cancel the exposure and immediately yield the system to the next user on their request. If you did not start your session on time as scheduled you will not be allowed a grace period to continue into the next person's session. Remember you must gain the next users permission to extend beyond 15 minutes into the next reservation slot. 3. Beginning your writing session -- the '16 minute Rule' applies: If at 'minute 16' of your reservation slot, if you have neither shown up to start your session, nor marked the system with a note saying you are coming, nor communicated with the last user on the system and posted to the raith mailing list; you lose your entire reservation. It is only upon the courtesy of the user available to come onto the system, once he has enabled on CORAL for the session, as to either to return the system to you within your lost reservation time or not. 4. Cancellations: Cancellations and trade off in RAITH sessions should be posted to the Raith mailing list for all to view as soon as possible once you realize that you will not be able to make use of your reservation. It is expected of Users that cancellations be done at least 24 hours before your reserved session to allow other lab members to make use of the opening. You must post a reason for your cancellation, particularly if it was due to a system or machine dependence from within the lab not allowing you to get your work finished. 5. If there is no one on the system and no reservation on CORAL, the system is available to you for your use. This does not affect your reservation limits on the Coral schedule and there is no need to make a reservation on Coral for this session. 6. ALL USERS must enable CORAL in their own account for their writing sessions. At the time of enable Users are to start an entry in the RAITH Operations Logbook and all pertinent information should be recorded. Problems during a run should be reported to CORAL and noted in the Logbook for prompt action by SNF staff. Thank you for your inputs and support of these policies. This should go a long way to create fair and uniform access and utility of the RAITH 150 Ebeam Lithography System. Yours, James Conway -------------- next part -------------- An HTML attachment was scrubbed... URL: From grupp at snowmass.Stanford.EDU Tue Feb 24 16:35:35 2004 From: grupp at snowmass.Stanford.EDU (Dan Grupp) Date: Tue, 24 Feb 2004 16:35:35 -0800 (PST) Subject: res removed tomorrow 2/25 1900-2200 Message-ID: scheduling conflict. --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From jwc at snf.stanford.edu Tue Feb 24 18:21:59 2004 From: jwc at snf.stanford.edu (James Conway) Date: Tue, 24 Feb 2004 18:21:59 -0800 Subject: <4 hr slots? Re: READ ME: CURRENT RAITH RESERVATION AND USAGE POLICY In-Reply-To: References: Message-ID: <403C06C7.7060205@snf.stanford.edu> Hello Dan, Mark, and Raith Users: Good question for clarification: >>Minimum of a four hour reservation slot, or you should 'Share the Ride' with other users within your CORAL reservation. Hence the word "should' versus 'must' ... This is to encourage, gently, the users whom just need an hour or two for an inspection or short write, and in order to reduce the number of unload/load transfers on the system as it eats up a large amount of time within a short session period. These group users could then hand off and retrieve their samples later. The entire goal is to increase throughput on the system. Thank you, James Conway Dan Grupp wrote: >Hi James, > Thanks for putting that together and managing this! I wish we had such >powerful voices on other pieces of eqpt in the fab. > One clarification: no slots lees than 4 hours? Many people have >resrevatoins of 2 or 3 hours. The rule appears to include the caveat of >loading with someone else. this is not practical in many instances, so >makes rule difficult. Seems rules that are not always used are just >culture, courtesies and practices we should try to follow for the good of >the community. >Thanks, >Dan > >On Tue, 24 Feb 2004, James Conway wrote: > > > >>Greetings Raith Community: >> >>Thank you for your input and participation in the Ebeam Town Meeting we >>held February 2, 2004. >>Here is the final version of the Reservation and System Usage policy >>based on your inputs. I hope that all users will see this change as an >>improvement from the past policy that was in place. We all agreed to try >>out this policy out and discuss further refinements needed at our next >>Ebeam Town Meeting. This meeting is scheduled for March 15, 2004 at 2 - >>4 PM, CIS 101. >> >>Current RAITH 150 Reservations Policy: >> >>1. Reservation limit of 8 hours per rolling 10 day reservation window on >>the Coral Reservation System. >>The reservation horizon was increased from 7 days to 10 days on Coral to >>allow you a longer window to make reservations. >> >>2. Minimum of a four hour reservation slot, or you should 'Share the >>Ride' with other users within your CORAL reservation. i.e., No half hour >>reservation games allowed or tolerated! Not necessary to petition the >>Raith list for each of your sessions! >> >>3. Longer reservation needed than the normal 8 hour session: >>You may have one reservation only of up to 10 hours maximum if you have >>no other reservations on the RAITH Coral system in a rolling two week >>period. You must have approval from James Conway if you desire a >>session longer than 10 hours, and you will then not be able to make an >>additional reservation for a two week period after that reserved session >>is completed. This is meant to meet the needs of users with special >>writing needs or circumstances only. >>Note: This policy continues to be under review and may be modified in >>the future as the need presents itself. >> >>4. Reservations start (rather than end) within the reservation horizon. >>This change in particular, is designed to avoid the "30 minute roulette" >>that labmembers wishing to reserve the raith and the stsetch have been >>forced to play. >> >>5. We have abandoned the concept of 'prime time' and 'non-prime time' >>hours. The Lab operates 24/7... >> >>6. First Come First Serve -- You must use your reservation before making >>a new reservation on the Coral system. >> >>Raith System Usage Policy: >> >>1. No System Usage Limit: >>While we have specific limits to RAITH Coral reservations, we do not >>have a limit on the system utilization if there are no other users >>working on or reserved for the system. I expect the system to be >>utilized 100% of the time. Users are asked to make the hand off between >>users as smooth as possible. It is suggested you check in with the >>previous user a short time before your session to aid in communications >>and the system hand off to reduce the unload / load exchange interval time. >> >>2. Grace Period: Users are expected to start and end your writing >>sessions within 15 minutes of the scheduled time slot. >>If you are having problems, or encountered difficulties during your >>write, which may require for you to extend into the next user's session >>you are expected to make an attempt to inform the next user within a >>hour of the hand off time. You must gain their permission to extend into >>their session. If you don't get permission or cannot complete the EBL >>task -- you are expected to cancel the exposure and immediately yield >>the system to the next user on their request. If you did not start your >>session on time as scheduled you will not be allowed a grace period to >>continue into the next person's session. >>Remember you must gain the next users permission to extend beyond 15 >>minutes into the next reservation slot. >> >>3. Beginning your writing session -- the '16 minute Rule' applies: >>If at 'minute 16' of your reservation slot, if you have neither shown up >>to start your session, nor marked the system with a note saying you are >>coming, nor communicated with the last user on the system and posted to >>the raith mailing list; you lose your entire reservation. It is only >>upon the courtesy of the user available to come onto the system, once he >>has enabled on CORAL for the session, as to either to return the system >>to you within your lost reservation time or not. >> >>4. Cancellations: >>Cancellations and trade off in RAITH sessions should be posted to the >>Raith mailing list for all to view as soon as possible once you realize >>that you will not be able to make use of your reservation. It is >>expected of Users that cancellations be done at least 24 hours before >>your reserved session to allow other lab members to make use of the >>opening. You must post a reason for your cancellation, particularly if >>it was due to a system or machine dependence from within the lab not >>allowing you to get your work finished. >> >>5. If there is no one on the system and no reservation on CORAL, the >>system is available to you for your use. >> This does not affect your reservation limits on the Coral schedule and >>there is no need to make a reservation on Coral for this session. >> >>6. ALL USERS must enable CORAL in their own account for their writing >>sessions. At the time of enable Users are to start an entry in the RAITH >>Operations Logbook and all pertinent information should be recorded. >>Problems during a run should be reported to CORAL and noted in the >>Logbook for prompt action by SNF staff. >> >>Thank you for your inputs and support of these policies. This should go >>a long way to create fair and uniform access and utility of the RAITH >>150 Ebeam Lithography System. >> >>Yours, >> >>James Conway >> >> >> >> >> >> >> >> >> >> > >--------------------------------------------------------------------------- >Dr. Daniel Grupp, Visiting Scholar >Center for Integrated Systems >Stanford University >Stanford, CA 94305 >(650) 724-6911 >FAX: 723-4659 >--------------------------------------------------------------------------- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fatih at stanford.edu Wed Feb 25 00:54:54 2004 From: fatih at stanford.edu (Mehmet Fatih Yanik) Date: Wed, 25 Feb 2004 00:54:54 -0800 Subject: Reservation cancelled In-Reply-To: <403BBD75.8050202@snf.stanford.edu> Message-ID: Tonight's reservation cancelled due to problem with RAITH. Even at Chessy, with mag>13.8K, the image on LEO is extremely distorted and drifts a lot. More experienced Raith users could not also identify the problem tonight fatih -----Original Message----- From: James Conway [mailto:jwc at snf.stanford.edu] Sent: Tuesday, February 24, 2004 1:09 PM To: Raith SNF Mailing list Cc: John Shott; Mary Tang Subject: READ ME: CURRENT RAITH RESERVATION AND USAGE POLICY Greetings Raith Community: Thank you for your input and participation in the Ebeam Town Meeting we held February 2, 2004. Here is the final version of the Reservation and System Usage policy based on your inputs. I hope that all users will see this change as an improvement from the past policy that was in place. We all agreed to try out this policy out and discuss further refinements needed at our next Ebeam Town Meeting. This meeting is scheduled for March 15, 2004 at 2 - 4 PM, CIS 101. Current RAITH 150 Reservations Policy: 1. Reservation limit of 8 hours per rolling 10 day reservation window on the Coral Reservation System. The reservation horizon was increased from 7 days to 10 days on Coral to allow you a longer window to make reservations. 2. Minimum of a four hour reservation slot, or you should 'Share the Ride' with other users within your CORAL reservation. i.e., No half hour reservation games allowed or tolerated! Not necessary to petition the Raith list for each of your sessions! 3. Longer reservation needed than the normal 8 hour session: You may have one reservation only of up to 10 hours maximum if you have no other reservations on the RAITH Coral system in a rolling two week period. You must have approval from James Conway if you desire a session longer than 10 hours, and you will then not be able to make an additional reservation for a two week period after that reserved session is completed. This is meant to meet the needs of users with special writing needs or circumstances only. Note: This policy continues to be under review and may be modified in the future as the need presents itself. 4. Reservations start (rather than end) within the reservation horizon. This change in particular, is designed to avoid the "30 minute roulette" that labmembers wishing to reserve the raith and the stsetch have been forced to play. 5. We have abandoned the concept of 'prime time' and 'non-prime time' hours. The Lab operates 24/7. 6. First Come First Serve -- You must use your reservation before making a new reservation on the Coral system. Raith System Usage Policy: 1. No System Usage Limit: While we have specific limits to RAITH Coral reservations, we do not have a limit on the system utilization if there are no other users working on or reserved for the system. I expect the system to be utilized 100% of the time. Users are asked to make the hand off between users as smooth as possible. It is suggested you check in with the previous user a short time before your session to aid in communications and the system hand off to reduce the unload / load exchange interval time. 2. Grace Period: Users are expected to start and end your writing sessions within 15 minutes of the scheduled time slot. If you are having problems, or encountered difficulties during your write, which may require for you to extend into the next user's session you are expected to make an attempt to inform the next user within a hour of the hand off time. You must gain their permission to extend into their session. If you don't get permission or cannot complete the EBL task -- you are expected to cancel the exposure and immediately yield the system to the next user on their request. If you did not start your session on time as scheduled you will not be allowed a grace period to continue into the next person's session. Remember you must gain the next users permission to extend beyond 15 minutes into the next reservation slot. 3. Beginning your writing session -- the '16 minute Rule' applies: If at 'minute 16' of your reservation slot, if you have neither shown up to start your session, nor marked the system with a note saying you are coming, nor communicated with the last user on the system and posted to the raith mailing list; you lose your entire reservation. It is only upon the courtesy of the user available to come onto the system, once he has enabled on CORAL for the session, as to either to return the system to you within your lost reservation time or not. 4. Cancellations: Cancellations and trade off in RAITH sessions should be posted to the Raith mailing list for all to view as soon as possible once you realize that you will not be able to make use of your reservation. It is expected of Users that cancellations be done at least 24 hours before your reserved session to allow other lab members to make use of the opening. You must post a reason for your cancellation, particularly if it was due to a system or machine dependence from within the lab not allowing you to get your work finished. 5. If there is no one on the system and no reservation on CORAL, the system is available to you for your use. This does not affect your reservation limits on the Coral schedule and there is no need to make a reservation on Coral for this session. 6. ALL USERS must enable CORAL in their own account for their writing sessions. At the time of enable Users are to start an entry in the RAITH Operations Logbook and all pertinent information should be recorded. Problems during a run should be reported to CORAL and noted in the Logbook for prompt action by SNF staff. Thank you for your inputs and support of these policies. This should go a long way to create fair and uniform access and utility of the RAITH 150 Ebeam Lithography System. Yours, James Conway -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtopinka at stanford.edu Wed Feb 25 07:46:51 2004 From: mtopinka at stanford.edu (Mark Allen Topinka) Date: Wed, 25 Feb 2004 07:46:51 -0800 Subject: high mag problems In-Reply-To: References: Message-ID: <1077724011.403cc36b7f470@webmail.stanford.edu> Yep, problem is still there. It happens when you go to the high-mag amplifiers (when you hear that click) for me it's WD=6.808mm and mag=11.87KX. At that mag, the image seems to stretch by like a factor of 2 in the x direction and starts drifting. I'm going to go ahead and write some coarse features, but as it stands it would be harder than usual to try and focus/stigmate the beam on high-mag. (Note: it might still work, since even most high-res writing is done at 1200X max, but I wouldn't bet my prize wafer on it). -Mark From jwc at snf.stanford.edu Wed Feb 25 11:50:50 2004 From: jwc at snf.stanford.edu (James Conway) Date: Wed, 25 Feb 2004 11:50:50 -0800 Subject: high mag problems In-Reply-To: <1077724011.403cc36b7f470@webmail.stanford.edu> References: <1077724011.403cc36b7f470@webmail.stanford.edu> Message-ID: <403CFC9A.5020308@snf.stanford.edu> Good Morning Raith Users: I have put the system into 'red light' mode == SHUTDOWN. The EHT trips that were experienced by John Cummings were unusual events. I was very surprised to learn upon arriving today that users had several different problems overnight. Note that we had run the system slowly up to 20 and 30 keV without problems before releasing the system to users yesterday. The root of the problem: arcing events in the gun section. The Magnification Amplifier No. 3 in the Electron Optics section (E/O) which switches at about 13.6 kX was found to have failed during my troubleshooting this morning. I am currently testing out the gun section again. LEO USA and RAITH USA have been informed of the problem, and we are trying to locate a E/O board here in America to replace the blown board as soon as possible. Please adjust your schedules accordingly -- likely down through Friday Noon. I will post to this list when I have more information. Thank you, James Conway Mark Allen Topinka wrote: >Yep, problem is still there. It happens when you go to the high-mag >amplifiers (when you hear that click) for me it's WD=6.808mm and >mag=11.87KX. At that mag, the image seems to stretch by like a factor of 2 >in the x direction and starts drifting. I'm going to go ahead and write >some coarse features, but as it stands it would be harder than usual to try >and focus/stigmate the beam on high-mag. (Note: it might still work, since >even most high-res writing is done at 1200X max, but I wouldn't bet my >prize wafer on it). -Mark > > From jwson at stanford.edu Wed Feb 25 13:22:40 2004 From: jwson at stanford.edu (Ji-Won Son) Date: Wed, 25 Feb 2004 13:22:40 -0800 Subject: Raith 10am-7pm Friday reservation cancelled Message-ID: <000001c3fbe5$7fc5ae10$416140ab@stanford.edu> Hi, Since I need a long session for the experimental consistency, and the system is likely to be down until Fri. Noon, I cancelled my Fri. daytime reservation. Thank you. ==================== Sincerely, Ji-Won Son (Office) 650-723-4940 (Fax) 650-725-3459 ==================== -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Wed Feb 25 19:45:50 2004 From: jwc at snf.stanford.edu (James Conway) Date: Wed, 25 Feb 2004 19:45:50 -0800 Subject: Raith down through 4 PM tomorrow. Message-ID: <403D6BEE.80009@snf.stanford.edu> Greetings, To effect repairs to the Gun section to eliminate the arcing events we encountered we had to break vacuum, clean the bore and FE-Gun assembly. We found a rather shocking carbon deposit on the side of the insulator possibly from an arc in this area. We are now starting to bake out the gun section of the column and hope to bring the platform back up on line tomorrow afternoon for users access about 4 PM. If this doesn't eliminate all problems we must them replace the tip and could be down through early next week. Only after this problem has been addressed will we replace the Electron Optics board that was damaged by the arc event last night. Please stand by for further updates as the situation progresses. Thank you for your support! James Conway From jwc at snf.stanford.edu Thu Feb 26 17:25:57 2004 From: jwc at snf.stanford.edu (James Conway) Date: Thu, 26 Feb 2004 17:25:57 -0800 Subject: RAITH Status as of 17:15 hours Thursday February 26, 2004 -- System down... Message-ID: <403E9CA5.3040401@snf.stanford.edu> Hello Raith Users: RAITH SYSTEM CONTINUES IN RED LIGHT MODE. Despite a best effort by all parties involved we were unable to return the system to operational status and we remain down for users access for E-beam Lithography. The gun emission is more stable than before and we have been able to ramp up to 30 keV repeatedly. We are now conditioning the tip and allowing gun vacuum levels to come down by running in the tip at 20 keV. 2.4 E -9 Torr. The imaging resolution is very poor at this point but will improve with time (hours to day) The E/O board that was received yesterday is not compatible with our platform (LEO 1530 uniplinth) so we are still down for magnification level three (~15 KX and higher.) LEO is trying their best to locate a suitable E/O board to replace ours and get us up and running ASAP. The raith computer is available for users whom wish to use it to prepare designs or position list. Please no commands over the REMCON serial interface. If you access the system: Leave the gun at EHT ON. It will not ramp down at logout. KEEP THE BEAM UNBLANKED. Be sure to unblank the beam if you start your user session and your profile loads and blanks the beam. (normal default for most logins.) Thank you for your support! James Conway From jwc at snf.stanford.edu Fri Feb 27 10:16:23 2004 From: jwc at snf.stanford.edu (James Conway) Date: Fri, 27 Feb 2004 10:16:23 -0800 Subject: Fwd: Electron-beam lithography research summer student opportunity at Hitachi. Message-ID: <403F8977.4000403@snf.stanford.edu> Greetings, This is a great opportunity to gain more experience and 'get your foot in the door' with a main player in Electron Beam Technologies. They have a very strong research team at Hitachi, and I am sure it would be very exciting to pursue research at this Company. If you are interested I would not delay in applying and expressing your interest in working at Hitachi. James Conway Ebeam Technology Group Stanford Nanofabrication Facility. 650-725-7075 -------- Original Message -------- Subject: Electron-beam lithography research summer student opportunity Date: Wed, 25 Feb 2004 21:57:05 -0800 From: Zvonimir.Bandic at hgst.com To: pease at cis.stanford.edu, harris at snowmass.stanford.edu, brongersma at stanford.edu CC: James Conway Dear Prof. Pease, Prof. Harris and Prof. Brongersma, We are actively looking for a summer student (at graduate level) for a research project in electron-beam lithography. Prior experience in electron beam lithography and device fabrication is highly desired. Student would gain hands on experience using Leica VB6 electron beam lithography tool, and would also work on interesting and important novel system-level problems in electron beam lithography. This is an excellent opportunity since we are looking for the candidates that one day could be potential hires on a research staff member level. I would appreciate if you could forward this information to interested students, or propose several names. Thank you very much! Best regards, Zvonimir Bandic Hitachi Research 650 Harry Rd. C2-438 San Jose, CA 95120 ph: (408) 323-7206 fax: (408) 323-7010 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwc at snf.stanford.edu Fri Feb 27 17:25:41 2004 From: jwc at snf.stanford.edu (James Conway) Date: Fri, 27 Feb 2004 17:25:41 -0800 Subject: Raith will remain off line -- likely through Tuesday Noon. UPDATE Monday afternoon . Message-ID: <403FEE15.9060103@snf.stanford.edu> Hello Raith Users: The Raith system will remain off line through next Tuesday Noon at the earliest -- please adjust your schedules accordingly. The Raith computer can be used for pattern editing and preparing position list. Please be careful the when you login that the beam is kept unblanked, as the normal default for most user logins is to blank on login. If you encounter difficulties call me immediately. NO ACCESS OR COMMUNICATIONS TO THE LEO COLUMN. PLEASE LET THE SYSTEM IDLE ALONG AND PLEASE DO NOT LOGOUT OF THE SERVICE WINDOWS AND GUN MONITORS AS WE ARE COLLECTING DATA. Currently we are idling at 20 keV, BEAM ON, EHT ON, 10000 kX mag. Beam I = 0.212 nA Beam emission has stabilized nicely but the vacuum levels and imaging resolution are very poor. Several sections of the LEO electron optics board were damaged when the system arced during user write early Wed. evening. This was not the fault of any user, just the luck of the draw... LEO and RAITH have provided excellent support and we all worked hard to efficiently coordinate and ship out E/O boards and parts needed to effect repairs. Best efforts were made by all parties involved. This situation will improve early next week. Thank you for your support, James Conway I will be traveling and 'off the cell grid' intermittently through the weekend. 415-412-4825 -------------- next part -------------- An HTML attachment was scrubbed... URL: