Micro and Nano Mechanics Group - User contributions [en]

Computing Clusters

2011-07-08T18:28:24Z

Swlee49:

==Computing Clusters==
The Micro and Nano Mechanics Group primarily uses two clusters here at Stanford. They are [http://hpcc.stanford.edu/clusters/mc-cc.html MC-CC] and WCR (or Glacial). MC-CC is a cluster supported by the Mechanics and Computation Group in the Mechanical Engineering Department and whose name means "Mechanics and Computation Computing Cluster". WCR, or alternatively Glacial, is a computer cluster hosted the the Mechanical Engineering Department and is the initials of the late William Reynolds (Not the Reynolds number Reynolds, but a Professor at Stanford who did research in thermodynamics). To use either cluster, you must be working with a faculty affiliated with the cluster. MC-CC has 45 nodes, each with 2 processors and WCR has 221 nodes with 8 processors per node.

==Hints For working with the clusters==
Below you will find information regarding nuances of working with these computing clusters. This is not meant to be a exhaustive list nor a tutorial, but a collection of advice and tools. They may not follow and order and we will update them as we remember.

===Semaphores===
A [http://searchenterpriselinux.techtarget.com/sDefinition/0,,sid39_gci212959,00.html semaphore] is a type of shared resource on the clusters, that can lead to communication problems in parallel runs if left on the nodes since there is a limit of number of semaphores. If any job you run terminates abnormally, you may leave Semaphore Arrays on the computer. If you run the job on the head node, then the Semaphore Array is left with the head node, otherwise it will be associated with the compute node you were working on. This can lead to problems with future parallel jobs run by you or other users. Therefore, it is good manners to frequently clean up your Semaphores.

'''How do I clean up Semahpores, you ask?''' Easy! You need to run the cleanipcs script to clean semaphores from your the computer. To do this, first you must find cleanipcs in the cluster using the locate command. Then, copy it over to you home directory and chmod it so that you have execute privileges. Now, you can run the program by typing
$ ./cleanipcs
This will clean all of your Semaphores from the computer. However, if you are on a cluster, then this will only clean the Semaphores from the head node. Generally, the problem usually lies with Semapahores on the compute nodes, which can be cleaned using the '''cluster-fork''' command. The command '''cluster-fork''' runs a following command(''e.g.'' ./cleanipcs) on all nodes or a subset of nodes. To clean the compute nodes, use
$ cluster-fork ./cleanipcs

In some of clusters, the command '''cluster-fork''' has been replaced with '''rocks run host'''. In this case, use
$ rocks run host "./cleanipcs"

'''How do I know if I have a Semaphore problem?''' Ok, thats easy too. Just run the command
$/usr/bin/ipcs -s
This will list all of the Semaphore Arrays used on the head node. Basically, the command '''ipcs''' lists all the active [http://en.wikipedia.org/wiki/Inter-process_communication interprocess communication] objects (shared memory, message queues and semaphores). With option '''-s''', it will show only semaphore sets. For the compute nodes, just use the cluster-fork prefix. The aforementioned script '''cleanipcs''' internally uses the command '''ipcrm''' to remove interprocess communication objects.

'''Finally, how do I know if this is crashing my parallel job?''' Well, likely your job will crash with the following error:
$ p4_error: semget failed for setnum:0
If you see this error in your parallel job, you may have a problem with Semaphore Arrays. Run the ipcs command to see which nodes have Semaphore Arrays and clean up yours. You cannot clean up Semapahores owned by other users, so you may have to contact them to free all Semaphores.

===Use Intel compiler in MC2===
MC2 has an intel compiler in the folder "/opt/intel", but it would not be active at your home directory. In this case, you need to activate an intel compiler at your home directory to compile somthing with icc (C compiler) and icpc (C++ compiler). You can do this simply by adding a line in your .bashrc file:

source /opt/intel/Compiler/11.1/064/bin/iccvars.sh intel64

Because MC2 is a 64 bit machine, you need intel64. (If the machine is 32 bit, you need ia32). Then, log out of a machine and reconnect. Then, you can use the intel compiler at your home folder. This is needed to compile ParaDiS 2.5.1.

Computing Clusters

2011-07-08T14:19:04Z

Swlee49:

==Computing Clusters==
The Micro and Nano Mechanics Group primarily uses two clusters here at Stanford. They are [http://hpcc.stanford.edu/clusters/mc-cc.html MC-CC] and WCR (or Glacial). MC-CC is a cluster supported by the Mechanics and Computation Group in the Mechanical Engineering Department and whose name means "Mechanics and Computation Computing Cluster". WCR, or alternatively Glacial, is a computer cluster hosted the the Mechanical Engineering Department and is the initials of the late William Reynolds (Not the Reynolds number Reynolds, but a Professor at Stanford who did research in thermodynamics). To use either cluster, you must be working with a faculty affiliated with the cluster. MC-CC has 45 nodes, each with 2 processors and WCR has 221 nodes with 8 processors per node.

==Hints For working with the clusters==
Below you will find information regarding nuances of working with these computing clusters. This is not meant to be a exhaustive list nor a tutorial, but a collection of advice and tools. They may not follow and order and we will update them as we remember.

===Semaphores===
A [http://searchenterpriselinux.techtarget.com/sDefinition/0,,sid39_gci212959,00.html semaphore] is a type of shared resource on the clusters, that can lead to communication problems in parallel runs if left on the nodes since there is a limit of number of semaphores. If any job you run terminates abnormally, you may leave Semaphore Arrays on the computer. If you run the job on the head node, then the Semaphore Array is left with the head node, otherwise it will be associated with the compute node you were working on. This can lead to problems with future parallel jobs run by you or other users. Therefore, it is good manners to frequently clean up your Semaphores.

'''How do I clean up Semahpores, you ask?''' Easy! You need to run the cleanipcs script to clean semaphores from your the computer. To do this, first you must find cleanipcs in the cluster using the locate command. Then, copy it over to you home directory and chmod it so that you have execute privileges. Now, you can run the program by typing
$ ./cleanipcs
This will clean all of your Semaphores from the computer. However, if you are on a cluster, then this will only clean the Semaphores from the head node. Generally, the problem usually lies with Semapahores on the compute nodes, which can be cleaned using the '''cluster-fork''' command. The command '''cluster-fork''' runs a following command(''e.g.'' ./cleanipcs) on all nodes or a subset of nodes. To clean the compute nodes, use
$ cluster-fork ./cleanipcs

In some of clusters, the command '''cluster-fork''' has been replaced with '''rocks run host'''. In this case, use
$ rocks run host "./cleanipcs"

'''How do I know if I have a Semaphore problem?''' Ok, thats easy too. Just run the command
$/usr/bin/ipcs -s
This will list all of the Semaphore Arrays used on the head node. Basically, the command '''ipcs''' lists all the active [http://en.wikipedia.org/wiki/Inter-process_communication interprocess communication] objects (shared memory, message queues and semaphores). With option '''-s''', it will show only semaphore sets. For the compute nodes, just use the cluster-fork prefix. The aforementioned script '''cleanipcs''' internally uses the command '''ipcrm''' to remove interprocess communication objects.

'''Finally, how do I know if this is crashing my parallel job?''' Well, likely your job will crash with the following error:
$ p4_error: semget failed for setnum:0
If you see this error in your parallel job, you may have a problem with Semaphore Arrays. Run the ipcs command to see which nodes have Semaphore Arrays and clean up yours. You cannot clean up Semapahores owned by other users, so you may have to contact them to free all Semaphores.

===Use Intel compiler in MC2===
MC2 has an intel compiler in the folder "/opt/intel", but it would not be active at your home directory. In this case, you need to activate an intel compiler at your home directory to compile somthing with icc (C compiler) and icpc (C++ compiler). You can do this simply by adding a line in your .bashrc file:

$source /opt/intel/Compiler/11.1/064/bin/iccvars.sh intel64

Because MC2 is a 64 bit machine, you need intel64. (If the machine is 32 bit, you need ia32). Then, log out of a machine and reconnect. Then, you can use the intel compiler at your home folder. This is needed to compile ParaDiS 2.5.1.

Before You Start: Known Bugs in ParaDiS

2011-05-19T13:57:59Z

Swlee49: /* Bug 5 */

== Bug 1 ==

If you download the standard distribution of ParaDiS <tt>pub-dd3d.v2.0.tar.gz</tt>, you will not be able to compile and run it in SERIAL mode. The fix to this problem is described below.

You need to download these three files (available on [http://paradis.stanford.edu/downloads ParaDiS download site]):

makefile.sys
makefile.setup
ReadConfig.c

This will allow you to use <tt>SYS = i386</tt> or <tt>SYS = cygwin</tt> and <tt>MODE = SERIAL</tt> in <tt>makefile.setup</tt>.

The <tt>SYS = i386</tt> option requires intel compiler <tt>icc</tt>. If you do not have this compiler, you can modify the <tt>makefile.sys</tt> file to use a different compiler.

We are working to enable the <tt>SYS = mac</tt> option. Please come back soon.

If your computer does not allow opening of X-window, then you need to set <tt>enable_window = 0</tt> in your <tt>win.script</tt> file. This is also necessary if you submit your job to a queue in a cluster, because you won't be able to open an interactive window there.

== Bug 2 ==
As the numbers of
cells and numbers of processors are changed, ownership or nodes/segments can
alter which may result in segments changing the cells into which they
are accounted... and hence alter results. So for a small test case, forces may be perfectly correct in serial but slightly off in parallel using cells (option FULL_N2Forces turned off).

On a large simulation the
results should be insignificant, but on small simulations with very few
dislocations, differences are more noticable.

== Bug 3 ==
Segmentation fault occurs with v2.3.5s and v.2.3.5.1 when compiling with GCC on Ubuntu and running codes with FMM. The error when compiling using <tt>-03</tt> optimization in serial or parallel (<tt>cc -O3</tt> or <tt>mpicc -03</tt>). Appears to be specific to <tt>-03</tt> and doesn't occur for <tt>-02</tt> or <tt>-g</tt>, for example. <tt>-03</tt> works properly when using Rijm tables.

This doesn't occur with the older version of ParaDiS in the subversion (~2.2.3 or 2.2.6?).

Details of error:
<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
Initialize: Control file parsing complete
Generating uniform domain decomposition.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff732896d in ?? () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff732896d in ?? () from /lib/libc.so.6
#1 0x00007ffff732b424 in calloc () from /lib/libc.so.6
#2 0x0000000000448911 in ReadNodeDataFile ()
#3 0x000000000042dcd4 in Initialize ()
#4 0x000000000040e321 in ParadisInit ()
#5 0x000000000040185a in main ()
</pre></blockquote>

== Bug 4 ==
Not really a bug, but a suggestion. When an X-window cannot be opened sucessfully the code exits with a segmentation fault. Should be able to add a descriptive message and a break instead.

== Bug 5. Errors of input files created in a DOS system ==
When ParaDiS input files (control and data files) are created in a DOS system (MS-DOS or Windows), the input files sometimes cannot be executed even though the files look okay in your editor of your linux system. For example, when you create input files using 'create_dislocation.f' in your DOS (or Windows) system, the hidden character, which is ^M, is embedded at the end of each line in your files. This character is sometimes shown or not shown in your editor. If it is shown, the input files look as the following.

<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
### ParaDis nodal file (create_dislocation.f)^M
### S.A. (10/29/07)###^M
^M
#File version number^M
2^M
^M
#Number of data file segments^M
1^M
#Minimum coordinate values (x, y, z)^M
-18348.6238532110 -18348.6238532110 -18348.6238532110^M
#Maximum coordinate values (x, y, z)^M
18348.6238532110 18348.6238532110 18348.6238532110^M
^M
#Node count^M
54^M
#Domain geometry (x, y, z)^M
1 1 1^M
...
...
</pre></blockquote>

When the character ^M is not shown, it is frustrating because the input files look perfect, ParaDiS canot execute these inputs with ^Ms and shows the errors such as

<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
...
Error: Expected '=' in parameter assignment
Fatal: Error obtaining values for parameter ) is produced.
...
</pre></blockquote>

We can remove this hidden character ^Ms simply using the command "<tt>dos2unix</tt>". This command erase all ^Ms in your files. Just run <tt>dos2unix (your-input-file-name)</tt>, Then, the input files can be executed.

Before You Start: Known Bugs in ParaDiS

2011-05-19T13:55:51Z

Swlee49:

== Bug 1 ==

If you download the standard distribution of ParaDiS <tt>pub-dd3d.v2.0.tar.gz</tt>, you will not be able to compile and run it in SERIAL mode. The fix to this problem is described below.

You need to download these three files (available on [http://paradis.stanford.edu/downloads ParaDiS download site]):

makefile.sys
makefile.setup
ReadConfig.c

This will allow you to use <tt>SYS = i386</tt> or <tt>SYS = cygwin</tt> and <tt>MODE = SERIAL</tt> in <tt>makefile.setup</tt>.

The <tt>SYS = i386</tt> option requires intel compiler <tt>icc</tt>. If you do not have this compiler, you can modify the <tt>makefile.sys</tt> file to use a different compiler.

We are working to enable the <tt>SYS = mac</tt> option. Please come back soon.

If your computer does not allow opening of X-window, then you need to set <tt>enable_window = 0</tt> in your <tt>win.script</tt> file. This is also necessary if you submit your job to a queue in a cluster, because you won't be able to open an interactive window there.

== Bug 2 ==
As the numbers of
cells and numbers of processors are changed, ownership or nodes/segments can
alter which may result in segments changing the cells into which they
are accounted... and hence alter results. So for a small test case, forces may be perfectly correct in serial but slightly off in parallel using cells (option FULL_N2Forces turned off).

On a large simulation the
results should be insignificant, but on small simulations with very few
dislocations, differences are more noticable.

== Bug 3 ==
Segmentation fault occurs with v2.3.5s and v.2.3.5.1 when compiling with GCC on Ubuntu and running codes with FMM. The error when compiling using <tt>-03</tt> optimization in serial or parallel (<tt>cc -O3</tt> or <tt>mpicc -03</tt>). Appears to be specific to <tt>-03</tt> and doesn't occur for <tt>-02</tt> or <tt>-g</tt>, for example. <tt>-03</tt> works properly when using Rijm tables.

This doesn't occur with the older version of ParaDiS in the subversion (~2.2.3 or 2.2.6?).

Details of error:
<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
Initialize: Control file parsing complete
Generating uniform domain decomposition.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff732896d in ?? () from /lib/libc.so.6
(gdb) backtrace
#0 0x00007ffff732896d in ?? () from /lib/libc.so.6
#1 0x00007ffff732b424 in calloc () from /lib/libc.so.6
#2 0x0000000000448911 in ReadNodeDataFile ()
#3 0x000000000042dcd4 in Initialize ()
#4 0x000000000040e321 in ParadisInit ()
#5 0x000000000040185a in main ()
</pre></blockquote>

== Bug 4 ==
Not really a bug, but a suggestion. When an X-window cannot be opened sucessfully the code exits with a segmentation fault. Should be able to add a descriptive message and a break instead.

== Bug 5 ==
When ParaDiS input files (control and data files) are created in a DOS system (MS-DOS or Windows), the input files sometimes cannot be executed even though the files look okay in your editor of your linux system. For example, when you create input files using 'create_dislocation.f' in your DOS (or Windows) system, the hidden character, which is ^M, is embedded at the end of each line in your files. This character is sometimes shown or not shown in your editor. If it is shown, the input files look as the following.

<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
### ParaDis nodal file (create_dislocation.f)^M
### S.A. (10/29/07)###^M
^M
#File version number^M
2^M
^M
#Number of data file segments^M
1^M
#Minimum coordinate values (x, y, z)^M
-18348.6238532110 -18348.6238532110 -18348.6238532110^M
#Maximum coordinate values (x, y, z)^M
18348.6238532110 18348.6238532110 18348.6238532110^M
^M
#Node count^M
54^M
#Domain geometry (x, y, z)^M
1 1 1^M
...
...
</pre></blockquote>

When the character ^M is not shown, it is frustrating because the input files look perfect, ParaDiS canot execute these inputs with ^Ms and shows the errors such as

<blockquote style="background: white; border: 0; padding: rem; width: 625px;"><pre>
...
Error: Expected '=' in parameter assignment
Fatal: Error obtaining values for parameter ) is produced.
...
</pre></blockquote>

We can remove this hidden character ^Ms simply using the command "<tt>dos2unix</tt>". This command erase all ^Ms in your files. Just run <tt>dos2unix (your-input-file-name)</tt>, Then, the input files can be executed.

Research Meeting Schedule

2009-10-06T17:04:15Z

Swlee49: /* Autumn 2009 */

===Autumn 2009===

Prof. Wei Cai's weekly schedule.

{| class="wikitable" style="text-align:center;"
!width="150pt" | Time
!width="200pt" | Monday
!width="200pt" | Tuesday
!width="200pt" | Wednesday
!width="250pt" | Thursday
!width="220pt" | Friday
|-
|9:00-10:00 || ''work'' || ''work'' || ''work'' || ''work'' || ''work''
|-
|10:00-10:30|| lecture prep || (meeting) || lecture prep || Seok-Woo
| rowspan="2" | '''ME80 office hour'''
|-
|10:30-11:00|| lecture prep || rowspan="2" | '''Group Meeting''' || lecture prep || ILL Ryu
|-
|11:00-11:30|| rowspan="2" | bi-weekly Eunseok, Hark, Prof. Prinz|| ''work'' || ''work'' || ''work''
|-
|11:30-12:00|| ''work'' || bi-weekly Hark || ''work'' || ''work''
|-
|12:30-1:15 || colspan="5" align="center" bgcolor="lightgrey" | lunch break
|-
|1:30-2:05 || rowspan="3" | '''ME80''' || rowspan="2" | '''ME80 office hour'''
| rowspan="3" | '''ME80''' || Jie (w. Prof. Barnett bi-weekly) || ''work''
|-
|2:10-2:45 || Keonwook || ''work''
|-
|2:50-3:25 || (meeting) || Sylvie || ''work''
|-
|3:30-4:00 || colspan="5" align="center" bgcolor="lightgrey" | coffee break
|-
|4:00-4:35 || Seunghwa Ryu || Haneesh || Eunseok || rowspan="2" | '''MC seminar''' || ''work''
|-
|4:40-6:00 || ''work'' || ''work'' || ''work'' || ''work''
|}

Meetings to sign-up

{| class="wikitable" style="text-align:center;"
|-
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" | Billy
|-
| colspan="3" |
| colspan="2" |
| colspan="2" | Seminar speaker
|}

Research Meeting Schedule

2009-09-24T02:14:48Z

Swlee49: /* Autumn 2009 */

===Autumn 2009===

Prof. Wei Cai's weekly schedule.

{| class="wikitable" style="text-align:center;"
!width="150pt" | Time
!width="200pt" | Monday
!width="200pt" | Tuesday
!width="200pt" | Wednesday
!width="200pt" | Thursday
!width="220pt" | Friday
|-
|9:00-10:00 || ''work'' || ''work'' || ''work'' || ''work'' || ''work''
|-
|10:00-10:30|| lecture prep || (meeting) || lecture prep || (meeting)
| rowspan="2" | '''ME80 office hour'''
|-
|10:30-11:00|| lecture prep || rowspan="2" | '''Group Meeting''' || lecture prep || (meeting)
|-
|11:00-12:00|| bi-weekly Eunseok, Hark, Prof. Prinz|| ''work'' || ''work'' || ''work''
|-
|12:30-1:15 || colspan="5" align="center" bgcolor="lightgrey" | lunch break
|-
|1:30-2:05 || rowspan="3" | '''ME80''' || rowspan="2" | '''ME80 office hour'''
| rowspan="3" | '''ME80''' || (meeting) || ''work''
|-
|2:10-2:45 || (meeting) || ''work''
|-
|2:50-3:25 || Seok-Woo || (meeting) || ''work''
|-
|3:30-4:00 || colspan="5" align="center" bgcolor="lightgrey" | coffee break
|-
|4:00-4:35 || Seunghwa Ryu || (meeting) || (meeting) || rowspan="2" | '''MC seminar''' || ''work''
|-
|4:40-6:00 || ''work'' || ''work'' || ''work'' || ''work''
|}

Meetings to sign-up

{| class="wikitable" style="text-align:center;"
|-
| width="120pt" | Eunseok
| width="120pt" | ILL Ryu
| width="120pt" | Seokwoo
| width="120pt" | Haneesh
| width="120pt" | Jie
| width="120pt" | Sylvie
| width="120pt" | Keonwook
| width="120pt" | Billy
|-
| colspan="2" | Hark (bi-weekly)
| colspan="3" | Jie, Prof. Barnett (bi-weekly)
| colspan="2" | Ibrahim (bi-weekly)
| colspan="2" | Seminar speaker
|}

Research Meeting Schedule

2009-01-11T02:02:14Z

Swlee49: /* Winter 2009 */

===Winter 2009===

Prof. Wei Cai's weekly schedule.

{| class="wikitable" style="text-align:center;"
!width="150pt" | Time
!width="200pt" | Monday
!width="200pt" | Tuesday
!width="200pt" | Wednesday
!width="200pt" | Thursday
!width="200pt" | Friday
|-
|9:00-10:00|| bi-weekly Eunseok, Hark, Prof. Prinz
| rowspan="3" | ''work''
| ''work''
| rowspan="3" | ''work''
| ''work''
|-
|10:00-10:45|| lecture prep. || lecture prep. || lecture prep.
|-
|11:00-12:15||'''ME346A'''||'''ME346A'''||'''ME346A''' (make-up lecture)
|-
|12:30-1:15 || colspan="5" align="center" bgcolor="lightgrey" | lunch break
|-
|1:30-2:05 ||Billy ||Keonwook ||Group Meeting ||Eunseok Lee
| rowspan="5" align="center" | ''work''
|-
|2:10-2:45 ||research meeting ||Seok-Woo ||Chris || Sylvie
|-
|2:50-3:25 ||research meeting || research meeting ||Jie || Seunghwa
|-
|3:30-4:00 || colspan="3" align="center" bgcolor="lightgrey" | coffee break
| ''work''
|-
|4:00-6:00 || ''work'' || ''work'' || ''work'' || '''MC seminar'''
|}

Meetings to sign-up

{| class="wikitable" style="text-align:center;"
|-
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" |
| width="120pt" | Seunghwa
|-

| width="120pt" | Alfredo
| width="120pt" |
| width="120pt" | Hark
| width="120pt" | Haneesh
| width="120pt" |
|-
| colspan="2" | '''Group lunch'''
| colspan="2" | '''ME346A Office hour'''
| colspan="2" | Seminar speaker
|}

Research Meeting Schedule

2009-01-04T06:38:06Z

Swlee49: /* Winter 2009 */

===Winter 2009===

Prof. Wei Cai's weekly schedule.

{| class="wikitable" style="text-align:center;"
!width="150pt" | Time
!width="200pt" | Monday
!width="200pt" | Tuesday
!width="200pt" | Wednesday
!width="200pt" | Thursday
!width="200pt" | Friday
|-
|9:00-10:00|| bi-weekly Eunseok, Hark, Prof. Prinz
| rowspan="3" | ''work''
| ''work''
| rowspan="3" | ''work''
| ''work''
|-
|10:00-10:45|| lecture prep. || lecture prep. || lecture prep.
|-
|11:00-12:15||'''ME346A'''||'''ME346A'''||'''ME346A''' (make-up lecture)
|-
|12:30-1:15 || colspan="5" align="center" bgcolor="lightgrey" | lunch break
|-
|1:30-2:05 ||research meeting ||Keonwook ||Seok-Woo ||research meeting
| rowspan="5" align="center" | ''work''
|-
|2:10-2:45 ||research meeting ||research meeting ||Chris ||research meeting
|-
|2:50-3:25 ||research meeting || research meeting ||Jie ||research meeting
|-
|3:30-4:00 || colspan="3" align="center" bgcolor="lightgrey" | coffee break
| ''work''
|-
|4:00-6:00 || ''work'' || ''work'' || ''work'' || '''MC seminar'''
|}

Meetings to sign-up

{| class="wikitable" style="text-align:center;"
|-
| width="120pt" | Eunseok
| width="120pt" |
| width="120pt" |
| width="120pt" | Billy
| width="120pt" |
| width="120pt" | Seunghwa
|-
| width="120pt" | Sylvie
| width="120pt" | Alfredo
| width="120pt" |
| width="120pt" | Hark
| width="120pt" | Haneesh
| width="120pt" |
|-
| colspan="2" | '''Group lunch'''
| colspan="2" | '''ME346A Office hour'''
| colspan="2" | Seminar speaker
|}

Seokwoo Lee

2008-01-23T23:39:29Z

Swlee49:

==Seok-Woo Lee==
Title: Ph.D candidate 
Department: Materials Science and Enigneering 
Location: Building 550, rm 554G, 416 Escondido mall, Stanford, CA, 94305 
Phone: 650 799 1566 
E-mail: swlee49@stanford.edu 
homepage : http://www.stanford.edu/~swlee49

Seokwoo Lee

2008-01-23T23:34:57Z

Swlee49: New page: Seok-Woo Lee Title: Ph.D candidate Department: Materials Science and Enigneering Location: Building 550, rm 554G, 416 Escondido mall, Stanford, CA, 94305 Phone: 650 799 1566 ...

Seok-Woo Lee
Title: Ph.D candidate
Department: Materials Science and Enigneering
Location: Building 550, rm 554G, 416 Escondido mall, Stanford, CA, 94305
Phone: 650 799 1566
E-mail: swlee49@stanford.edu

M01 How to Obtain and Run DDLab

2007-11-30T21:49:38Z

Swlee49: New page: Seokwoo Lee and Wei Cai ==What is DDLab== DDLab is ... ==Download from the Web== You can download DDLab from [http://micro.stanford.edu/~caiwei/Forum/2005-12-05-DDLab here] You can a...

Seokwoo Lee and Wei Cai

==What is DDLab==

DDLab is ...

==Download from the Web==

You can download DDLab from
[http://micro.stanford.edu/~caiwei/Forum/2005-12-05-DDLab here]

You can also download ParaDiS and DDLab together from
[http://paradis.stanford.edu here]

DDLab Manuals

2007-11-30T21:49:24Z

Swlee49:

<UL>

<LI> [[M01 How to Obtain and Run DDLab]]

<LI> [[M02 Frank-Read Source]]

<LI> [[M02 Binary Junction]]

</UL>

DDLab Manuals

2007-11-30T21:49:05Z

Swlee49:

<UL>

<LI> [[M01 How Obtain and Run DDLab]]

<LI> [[M02 Frank-Read Source]]

<LI> [[M02 Binary Junction]]

</UL>

DDLab Manuals

2007-11-30T21:48:28Z

Swlee49:

<UL>

<LI> [[M01 How to Obtain and Run DDLab]]

<LI> [[M02 Frank-Read Source]]

<LI> [[M02 Binary Junction]]

</UL>

M01 How Obtain and Run DDLab

2007-11-30T21:47:54Z

Swlee49:

M01 How Obtain and Run DDLab

2007-11-30T21:46:39Z

Swlee49: /* Download from the Web */

How to Obtain and Run DDLab

Seokwoo Lee and Wei Cai

==What is DDLab==

==Download from the Web==

You can download DDLab from
[http://micro.stanford.edu/~caiwei/Forum/2005-12-05-DDLab here]

You can also download ParaDiS and DDLab together from
[http://paradis.stanford.edu here]

M01 How Obtain and Run DDLab

2007-11-30T21:44:54Z

Swlee49: New page: How to Obtain and Run DDLab Seokwoo Lee and Wei Cai ==What is DDLab== ==Download from the Web== You can download DDLab from [http://micro.stanford.edu/~caiwei/Forum/2005-12-05-DDLab|he...

How to Obtain and Run DDLab

Seokwoo Lee and Wei Cai

==What is DDLab==

==Download from the Web==

You can download DDLab from
[http://micro.stanford.edu/~caiwei/Forum/2005-12-05-DDLab|here]

You can also download ParaDiS and DDLab together from
[http://paradis.stanford.edu|here]

DDLab Manuals

2007-11-30T21:41:18Z

Swlee49: New page: <UL> <LI> M01 How Obtain and Run DDLab <LI> M02 Frank-Read Source <LI> M02 Binary Junction </UL>

<UL>

<LI> [[M01 How Obtain and Run DDLab]]

<LI> [[M02 Frank-Read Source]]

<LI> [[M02 Binary Junction]]

</UL>

Main Page

2007-11-30T21:36:43Z

Swlee49: /* Tutorials */

Welcome to the Micro and Nano Mechanics Group at Stanford

==Group Members==

[[Wei Cai]]

[[Sylvie Aubry]]

[[Keonwook Kang]]

[[Seunghwa Ryu]]

[[Yongxing Shen]] (auditor)

[[Chris Weinberger]]

[[Jie YIN]]

[[Seokwoo Lee]]

==Research Projects==

[[Nanowire Mechanics]]

[[Dislocation Core]]

==Tutorials==
[[Dislocations]]

[[Atomistic Calculations]]

[[Unix Basics]]

[[Computer Setup]]

[[MD++ Manuals]]

[[DDLab Manuals]]

==Fun==

[[Local Restaurants]]

Main Page

2007-11-29T22:52:24Z

Swlee49: /* Group Members */