DaveG @ PhUSE

UploadLog

Thu, 09 Nov 2006 18:27:22 GMT

| !date | !user | !location | !storeUrl | !uploadDir | !toFilename | !backupdir | !origin |
| 22/6/2006 10:52:43 | DaveGarbutt | [[/|http://tiddlyspot.com/stestphuk/]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 22/6/2006 10:52:57 | DaveGarbutt | [[/|http://tiddlyspot.com/stestphuk/]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 17:23:3 | DaveGarbutt | [[/|http://tiddlyspot.com/stestphuk/]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 18:25:13 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 18:26:31 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 18:26:48 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 18:27:5 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 23/6/2006 18:27:42 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . | Ok |
| 23/6/2006 18:37:28 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 27/6/2006 10:56:27 | DaveGarbutt | [[DaveG-tiddlyspot.html|file:///E:/DaveG-tiddlyspot.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 10/7/2006 19:28:53 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 10/7/2006 19:32:0 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/7/2006 19:38:58 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 10/7/2006 19:39:8 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 10/7/2006 20:20:3 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 11/7/2006 10:44:14 | DaveGarbutt | [[DaveG.html|file:///E:/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 16/7/2006 17:40:46 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 16/7/2006 17:41:38 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 16/7/2006 22:33:16 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 20/8/2006 14:10:33 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 20/8/2006 15:8:59 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 20/8/2006 23:33:24 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/stestphuk/store.php]] | . | index.html | . |
| 20/8/2006 23:39:52 | DaveGarbutt | [[DaveG.html|file:///Volumes/DAVEGARBUTT/DaveG.html]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 23/8/2006 20:25:32 | YourName | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 23/8/2006 20:27:48 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 23/8/2006 20:38:47 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 23/8/2006 20:46:39 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 23/8/2006 21:51:59 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 23/8/2006 22:14:1 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 23/8/2006 22:27:54 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 26/8/2006 19:35:27 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 27/8/2006 11:42:10 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 27/8/2006 15:38:32 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 27/8/2006 17:19:48 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 27/8/2006 18:33:28 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 29/8/2006 16:54:45 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 29/8/2006 18:29:45 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 9:24:6 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 10:6:57 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 10:57:31 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 11:15:15 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 11:30:16 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 11:46:43 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 14:16:26 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 14:54:23 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 15:12:0 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 15:28:38 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 30/8/2006 16:10:1 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 17:16:3 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 18:46:7 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 19:52:34 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 19:57:30 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 30/8/2006 22:38:37 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 1/9/2006 12:25:50 | DaveGarbutt | [[/|http://tiddlyspot.com/daveg/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 5/9/2006 17:34:14 | DaveGarbutt | [[/|http://tiddlyspot.com/DaveG/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 8/9/2006 10:30:57 | DaveGarbutt | [[/|http://tiddlyspot.com/DaveG/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/9/2006 18:27:43 | DaveGarbutt | [[/|http://tiddlyspot.com/DaveG/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/9/2006 18:57:46 | DaveGarbutt | [[/|http://tiddlyspot.com/DaveG/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . | Ok |
| 10/9/2006 19:1:7 | DaveGarbutt | [[/|http://tiddlyspot.com/DaveG/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/9/2006 23:32:57 | DaveGarbutt | [[/|http://daveg.tiddlyspot.com/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/9/2006 23:35:42 | DaveGarbutt | [[/|http://daveg.tiddlyspot.com/]] | [[store.php|http://tiddlyspot.com/DaveG/store.php]] | . | index.html | . |
| 10/9/2006 23:36:56 | DaveGarbutt | [[/|http://daveg.tiddlyspot.com/]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 10/9/2006 23:37:34 | DaveGarbutt | [[/|http://daveg.tiddlyspot.com/]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 10/9/2006 23:47:49 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://tiddlyspot.com/DaveG/store.cgi]] | . | index.html | . | Ok |
| 10/9/2006 23:50:28 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 11/9/2006 1:52:38 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 11/9/2006 3:5:57 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 11/9/2006 3:29:35 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 11/9/2006 22:31:32 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 15/9/2006 22:59:30 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 15/9/2006 23:57:45 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 16/9/2006 17:59:44 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 16/9/2006 18:2:21 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 16/9/2006 18:25:4 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 17/9/2006 12:1:17 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 17/9/2006 12:13:45 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 17/9/2006 13:10:6 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 17/9/2006 14:12:16 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 17/9/2006 18:28:53 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 18/9/2006 0:17:55 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 18/9/2006 1:14:53 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 18/9/2006 2:16:16 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 20/9/2006 19:16:6 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 4/10/2006 9:10:28 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 4/10/2006 9:10:42 | DaveGarbutt | [[index.html|file:///Users/dave/Documents/BSI/PhUSE%20Papers%202006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 26/10/2006 10:48:6 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 26/10/2006 10:52:14 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 26/10/2006 10:52:33 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 26/10/2006 10:52:58 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 26/10/2006 10:53:54 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 26/10/2006 11:3:36 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 26/10/2006 11:9:57 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 26/10/2006 11:22:35 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 26/10/2006 11:28:11 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 26/10/2006 11:59:44 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 11:49:24 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 12:51:48 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 12:54:28 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 15:9:22 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 15:18:5 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 27/10/2006 19:21:50 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 6/11/2006 15:18:29 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 6/11/2006 15:46:4 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 6/11/2006 19:3:42 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 7/11/2006 11:52:40 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 8/11/2006 0:34:38 | DaveGarbutt | [[index.html|file:///Volumes/DAVEGARBUTT/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 8/11/2006 1:15:8 | DaveGarbutt | [[index.html|file:///Volumes/DAVEGARBUTT/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 8/11/2006 15:30:39 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |
| 9/11/2006 16:20:57 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 9/11/2006 16:31:7 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . | Ok |
| 9/11/2006 19:27:22 | DaveGarbutt | [[index.html|file:///E:/PhUSE%20Dublin%2006/index.html]] | [[store.cgi|http://DaveG.tiddlyspot.com/store.cgi]] | . | index.html | . |

Gnit Your Own - final

Thu, 09 Nov 2006 15:30:39 GMT

This text is copied out of the presentation file, I will gradually unify it with the draft version in [[Gnit your own]], adding the untransferred text and making the commands and results into popups.

<>
--s--
!Gnit your own - creative uses of Unix Text Tools for everyday problems
!Dave Garbutt

TU04 @ PhUSE 2006, Dublin
--s--
!Introduction
# What commands are available, and
# Which problems they solve, with
# Relevant examples of
# How you can put them together to solve problems.
# And lastly introduce you to
# !the power of regular expressions (RE).
*This is a little different from programming in SAS -
* but learning a new way to think about, and solve problems
* is only going to help your programming in SAS, or out of it.
--s--
! These Examples
*I have written the following examples during my everyday work as a SAS programmer. They have already helped me. I hope they will help you too.
*Experiment!
* Find an example that tackles a problem you have (or near to it at least) and copy it to your system. With command pipelines it is very easy to take them apart and see what each step does.
*Then modify the steps and see the effect.
*I have added a > character at the start of lines that are commands, this is to separate the commands from their output better.
* Do not paste this character!
*Other shells might start the line with a different character
--s--
! In short...
*Quick solutions for problems where writing a SAS program is not worthwhile.
* The ability to process text files before reading them into SAS by using the pipe facility of Filename can also save you a lot of SAS programming.
*Practice with regular expressions outside of SAS
--s--
!Unix text commands
*What they operations do they do?
*Commands on the whole file
*tr, iconv, wc, expand, cat, tee, split, sort, spell
*Commands (only) selecting observations
*comm, join, uniq, grep
*Commands selecting variables
*cut -c, cut -f, colrm
*Commands that can select obs, vars or derive new variables
*sed,awk,shells (eg korn), perl,ruby
--s--
!How do they fit together?
*Unix commands can all be fitted together in long sequences
*| Separated by the vertical bar character.
*The output of each program becomes the input of the next
{{{
command 1 -options files | command2 -options | command3 -options [>redirect to file]
}}}
*These sequences are known as pipes.
*By combining a few text commands very flexible and powerful processing can be written quickly
*So quickly that all kinds of tasks not worth automating become available for solution
*Fast
--s--
!Regular expressions- wild, wild cards
* Like: *.sas
*Extended… but different rules from file matching
*Normally we control an action (keep, drop) with the RE, but
*We can also extract the exact matched text
*Confusion points
*Dot(.) means *, I.e. any character
*labl*.sas --> lablllzsas!
*labl.*\.sas
*Much less coding than typical with SAS character functions
--s--
!Build up bit by bit
*No match = silence ''means //always// test'' on data with some known matches in

--s--
!RE syntax
*Rules:
*Patterns are applied line-by-line
*Matches are found anywhere on the line unless there is an anchor
*Expressions to be matched have these components (all optional)

{{{ ^Abc.+[abc]*\ (big|small)present{2,3}$ }}}

--s--
!Characters, ranges,alternatives repetitions, anchors, escapes

--s--
!Simple RE examples:
*[_A-Za-z][_A-Za-z0-9]{0,7}
*matches a V6 SAS variable identifier

*.*\.sas7b[cd]at
*matches the file names of SAS catalogues and datasets

*population
*matches the string 'population', anywhere on the line
--s--
!RE example: Searching SAS logs
*Your boss asks you to check Wiley T. Programmers' logs because he has gone home…
*They haven't even finished printing yet!
1.{{{> grep ERROR wtpsas.log}}}
2.{{{> grep -E `^ERROR:` wtpsas.log}}}
3.{{{> grep -E '^ERROR[ ]*:' wtpsas.log}}}
4.{{{> grep -E '^[Ee][Rr]+[Oo][Rr][ ]*:' wtpsas.log}}}
5.{{{> grep -i -E '^ERROR[ ]*:' wtpsas.log}}}
6.{{{> grep -i -E '^ERROR[ ]*:' *.log}}}
*No output!
*"Yes, that fast ☺". 17:18 - out of the door.

--s--
!Frequently Posed Worries
*Do I have to learn all these commands before I can get anything done?
*Are your tips only for one kind of Unix, or one kind of shell?
*What about Windows?
*Won't this take a long time, (my log files are taking up about 500KB) to run on my 200 listings?
*It looks like Chinese, how can I ever understand that gobbledygook?

--s--
!So with the worries gone, let's look at examples
*These are hard to show well in PowerPoint
*So read the text paper
*And see them online at [[here|http://daveg.tiddlyspot.com/]]
*More text is in the slide notes
--s--
! EG 1: Can I see who has access to my studies?
*On my home system a clinical project has a single group. So if we check the group membership we will get the answer.
{{{> lsgroup MYPROJ}}}
{{{MYPROJ id=8996 admin=false users=scott,ccadmin,flopsy,mopsy,cottontailo
,peter registry=files}}}
*But it isn't exactly easy to read. To just get the list of users:
{{{> lsgroup -a users meproj}}}
{{{MYPROJ users=scott,ccadmin,flopsy,mopsy,cottontailo ,peter}}}
----
* These examples are all fictionalised, and you can tell from this one because a
Unix user name must be 8 characters or less.
--s--
!Eg1 page 2
*Let us drop scott and sort by user id, but first we have to get every user on a separate line.
* The octal for line-feed is '\012', using tr we can translate commas to line
ends.
* We delete the first line with the sed program, 1d means for line 1, do a delete.
{{{> lsgroup -a users MYPROJ | tr ',' '\012' |sed '1d' | sort }}}
*gives:
{{{
ccadmin
cottontailo
!flopsy
!mopsy
peter
}}}
*Much more readable!
--s--
!A file I copied from Windows gives me strange messages

*All text files are not equal.
!Windows uses two characters to mark the end-of-line and Unix only one.
This extra ^M (control+M, ASCII 15 (octal)) character is a legal character in a
file name so it causes all sorts of issues.
*There are various ways to fix it perhaps the simplest is:
{{{
!tr -d '\015' cleaned_file ; mv -f cleaned_file inputfile
}}}
--s--
!I am programming the flagging of lab values…
*how can I see just the lines with flags?
*The file is 12,000 lines long!
*We want to select rows that have at least once the pattern:
{{{'numberflagchar'}}}
*no lines with only {{{numbernumber}}} should show
{{{
grep -E '[0-9]+[ ]*[#$^+]+' labl*.lst
}}}
* labl_23.lst:
{{{
Week 64 22MAY2006/378 09:12 404# 465# 443# 755 88 137
labl_23.lst:
Week -2 09NOV2004/-105 08:42 467 551 $ 521 $ 717 130 154
}}}
--s--
!Did I remember to run the formats program?
# {{{> ls ../../report/pgm_a/format* ../../report/pgm_s/format*
../../report/data_a/format*
-r--r----- 1 CCadmin this-study 507904 Feb 4 09:04 /vob/myproj/this..sas
-r--r----- 1 CCadmin this-study 507904 Feb 1 07:34 /vob/myproj/this…cat
}}}
# {{{> ls ../../report/*/format*}}}
# {{{> ls -l /vob/this-study/report/@(data|pgm)_[sa]/formats.@(sas|sas7bcat)}}}
* {{{@(data|pgm)}}} means {{{data}}} or {{{pgm}}},
*{{{[sa]}}} means an {{{s}}} or an {{{a}}}, but no other character at this position,
*{{{@(sas|sas7bcat){{{ means one of {{{sas}}} and {{{sas7bcat}}}
!The directories searched are
{{{
!report/data_a,report/data_s,report/pgm_a,report/pgm_s
}}}

--s--
!Did I remember…?
*Another approach would be to use compound (shell) commands.
{{{
cd /vob/myproj/this-study/report/data_a/

[[formats.sas -nt formats.sas7bcat ]] &&
print "run the program!"
}}}
*{{{[[}}} and {{{]]}}} surround a logical test, meaning the command is evaluated
as a true/false expression.
*{{{-nt}}} is true if the left hand file is newer than the right hand file,
* {{{&&}}} means that if the command is true the second command is run, else, it
is not.
--s--
!Have I run all the SAS programs in the current directory?
*We could check if there is a log for every program:-
{{{
> ls *.sas | wc -l
200
> ls *.log | wc -l
200
}}}
*That's all very well, but what if there are some old listings left?
*Let's just look at the dates of the listings.
*Then, if they are not all today we obviously have a problem.
--s--
!Have I run all the SAS programs in a directory?
*We can use ls to get lists of files and information about them.
{{{
ls -l *.sas
120 -rwxr-xr-x 1 dave unknown 55380 6 Dec 1999 A55219.sas
40 -rwxr-xr-x 1 dave unknown 18798 27 Mar 2001 clin_stats.sas
144 -rwxr-xr-x 1 dave unknown 71352 18 Apr 2001 basic_ods.sas
}}}
*Let us just get the dates, just to get a feel for how many are today or last week…
{{{
> ls -l -H -t *.sas | cut -c 38-49
6 Dec 1999
18 Apr 2001
27 Mar 2001
}}}
--s--
!Histogram of file dates
*Count how many files were modified on each date in the current directory
{{{
ls -l -H -t |
# list all the files , with date details -l and no header -H, sorted by time . -t
sed 1d | # delete the first line (total )
cut -c 44-51 |
# keep only columns 44 to 51 (where the date is)
uniq -c |
# delete duplicate dates (list is already sorted
}}}
--s--
!How do I run every SAS program in a directory?
*Strategy:
*Generate a list of all the programs
*Pass this list to a command to execute the passed names
1.{{{> apply 'sas -noterminal -noovp %1 &' *.sas }}}
2.{{{apply 'sas -noterminal -noovp %1 ' *.sas &}}}
3.{{{sas -noovp -noterminal *.sas &}}

* The {{{&}}} means 'run in background'
* Note where the {{{&}}} is:
# runs a separate SAS job for each, but at the same time,
# runs the whole apply command in the background, it runs one SAS at a time.
# does this too but calls SAS once, and writes only one log file

--s--
!How many patients in each lab listing? Consistent?
*Extract from a lab listing:
*Every patient is identified like this, so
*If we count how many patient ids there are
* we are home.
*How?
*The classic : select, sort, de-duplicate
--s--
!How many patients in each lab listing? Consistent?
*Great - but this is the whole line
*Select a field with awk or cut
--s--
!How many patients in each lab listing? Consistent?
*Great - but there are duplicates
--s--
!How many patients in each lab listing? Consistent?
*Now we just count how many lines…
*Add wc -l at end of pipe:
{{{
> grep -E '[A-Za-z]+/[0-9]+/.+/' llab_21.lst |
awk '{print $1}'| sort | uniq |
wc -l
200
}}}
--s--
!Could we get a count for all the lab listing files?
*Add a wild card, and scan all lab files:
{{{
> grep -E '[A-Za-z]+/[0-9]+/.+/' labl1_2?.lst | head
llab_21.lst: ROW/0001/00001 49/F/Ca…
llab_21.lst: ROW/0001/00001 49/F/Ca…
llab_21.lst: ROW/0002/00010 55/M/Ca…
}}}
*This adds the file name at the start of the line
*Extract the pat id plus file name
*Sort | uniq
*Drop the patid and
*Sort uniq again…
--s--
!Could we get a count for all the lab listing files?
*Two step scan and count
{{{
> grep -E '[A-Za-z]+/[0-9]+/.+/' llab_2?.lst | awk '{print $1, $2}' | sort | uniq |
awk '{print $1}' | uniq -c
200 llab_21.lst:
200 llab_22.lst:
200 llab_23.lst:
8 llab_24.lst:
}}}
--s--
!Can I extract the population used from all the listings?
{{{
> grep 'population' llab_2[1-9].lst | sort | uniq | head -20
llab_21.lst: Extension Safety population
llab_22.lst: Extension Safety population
llab_23.lst: Safety population
llab_24.lst: Efficacy population
llab_25.lst: Extension Safety population
}}}
--s--
!Hmmm, interesting, can I match it up with the patient counts?
*Save the pops list and the counts in files
* then list the files to remind ourselves of the layout
{{{
> cat file-count.txt
200 llab_21.lst:
200 llab_22.lst:
200 llab_23.lst:
8 llab_24.lst:
155 llab_25.lst:
> cat labpops.txt
llab_21.lst: Extension Safety population
llab_22.lst: Extension Safety population
llab_23.lst: Extension Safety population
llab_24.lst: Extension Safety population
llab_25.lst: Extension Safety population
}}}
* join on file name - in different columns in each file
{{{
> join -1 2 -2 1 file-count.txt labpops.txt
llab_21.lst: 200 Extension Safety population
llab_22.lst: 200 Extension Safety population
llab_23.lst: 200 Extension Safety population
;lab_24.lst: 8 Extension Safety population
llab_25.lst: 155 Extension Safety population
}}}
--s--
!Could we extend this to count patients per treatments per per file?
*Here is a solution to this problem. It does a two level summary by using the
{{{ sort}}} {{{ | }}} {{{uniq}}} sequence twice.
1.get the lines from top of each page giving the Treatment: and save the treatment label in a variable.
2.get the lines with a patient id and print just the patient id from that line, but add the filename and treatment label first.
3.run uniq to get one line per patients (per file and treatment). This is because patients are more than once in a listing if the program has split parameters into two sections
4.run uniq again with -c to count how many pats per file and treatment
5.add an awk to end of pipe to print filename once and tabs to lay output out ''NICELY''

--s--
!Could we extend this to count patients per treatments per per file?
{{{
gawk '/^[tT]reatment:/ {sub("Treatment[ ]*:",""); trt = $0 } # store the
treatment /[A-Za-z]+[/][0-9]+[/].+/ {print "|"FILENAME"|"trt"|"$1 }
# print file & treat for every line with an id
' app9l1_12?.lst | sort | uniq |
awk -F"|" '{ print $2": "$3} ' |
# select just two fields
uniq -c |
# and count
awk '{ if ( oldfile != $2 ) {print "\nFile ",$2" :";
oldfile = $2}}
# pattern1 :print file name once, when it changes
{print "\t"$1"\t" $3,$4,$5,$6,$7,$8} # print for all lines:
# add tabs (\t) for first two fields but not others '
}}}
--s--
!Could we extend this to count patients per treatments per per file?
*It might output:
{{{
File app9l1_121.lst: :
35 Bio 30mg qd (core) + combination
87 Draino 50mg bid (core) + combination
78 Draino 50mg qd (core) + combination

File app9l1_124.lst: :
2 Bio 30mg qd (core) + combination
4 Draino 50mg bid (core) + combination
2 Draino 50mg qd (core) + combination

File app9l1_125.lst: :
27 Bio 30mg qd (core) + combination
67 Draino 50mg bid (core) + combination
61 Draino 50mg qd (core) + combination
}}}
--s--
!I need to make a last check of all the titles to ensure they match the specifications
*Is it possible to list the titles, when there are different numbers of title lines in each output?
*Some versions of grep have the -p option that prints the paragraph (set of lines delimited by a blank lines) around the matched text.
*If there is text that is on every first page title then
{{{> grep -ip '(Page 1 of' *.lst}}}

--s--
!I need to make a last check of all the titles to ensure they match the specifications - no grep -p?
*The key to this trick is to set he
*field separator to \n (line end) and the
*record separator to null
(awk interprets this as a blank line).
*The awk program has two clauses
*the string to be matched in /…/ followed by the
*program to be executed when a match is found enclosed in {…}.
*FILENAME is an awk system variable
*$0 is the whole record (i.e. a paragraph in this case)
*BEGIN is a program executed before the scanning of input starts.
{{{
> gawk 'BEGIN { FS= "\n" ; RS = ""}
/Page 1 of/ { print FILENAME":\n" $0 } ' *.lst
}}}
--s--
!How can I check for issues that reappear?
*How about getting the first page?
*Saving in a date stamped file name
*Using diff later
*If we set the RS to page feed and line end as field separator we get one (logical) record per page. Then we can extract all first pages to keep track of changes. "\014 is ^L, ctrl+L, or page feed.
{{{ >gawk 'BEGIN { FS= "\n" ; RS = "\014"} /Page 1 of/ { print "\014"FILENAME": " $0 } ' *.lst }}}
*To save the first 9 pages change {{{/Page 1 0f/}}} to {{{/Page [1-9] of/}}}
--s--
!How can I check my RTF files were all re-created today?
*This example is very interesting for me. When I saw this problem (and not all the RTF files had listings so using the lst files was not an option) I thought there would be no way without learning a lot of RTF and writing a parser (this has already been done for perl, incidentally). But, one day I looked at an RTF file and thought - all I need is the matching string out of the file. The markup doesn't matter.
*So looked for a way to extract the matching text and there is an awk function to do it.
--s--
!How can I check my RTF files were all re-created today?
I wrote an awk program:
* It assumes the date the file was written is in a line containing the program file path, which begins with /report/ (the path is report/key or report/tier1, or report/tier2, perhaps)
* On these lines there is a date - which is the file write date
* We need to find the lines with a date (why not match on lines containing any date?).
* Then extract the date from the line...
* This is done with the match function: it returns 1 if it found a matching string, and then
* It puts the location into awk system variables that we can plug in to the substring function to get the date into a variable.
* Then if we found a date on the line the print statement prints the file & date

--s--
!How can I check my RTF files were all re-created today?
{{{
> gawk '/report\// {
match($0,"report[/].*\sas");
file=substr($0,RSTART,RLENGTH);
ok=match($0,"[0-9]+[A-Z]+[0-9]+");
date=substr($0,RSTART,RLENGTH);
if (ok) print date, file } ' *.rtf|
sort -t" " |
uniq
}}}
--s--
!Just one more thing…

*Checks performed like this are measuring directly what is in the deliverable;
*They make no assumptions about the datasets, variable names etc.
*They can be applied to many reporting systems if they use the same output conventions
*And they can be scripted and run automatically so you can keep an up to date summary table or document and perhaps compare it to a version printed from SAS.
*This adds up to a uniquely powerful way to tackle output validation and testing

--s--
!Visual Summary
* see paper version :-)
--s--
!Conclusions
*Gnit your own:
*Complementary skills to SAS
*Ideal for restricted, focussed, specific, one-off needs because of speed and readability
*Good place to learn regular expressions (very interactive) for SAS V9
*And hashed arrays - also in V9
*Can be Fun too
* http://www.tiddlyspot.com

--s--
!Questions?

<<<
It is not because things are difficult that we do not dare,
it is because we do not dare that they are difficult.
--Seneca
<<<
--s--
!Contact Information
I would value your comments and questions on this paper. Please contact me
at: DaveG
--s--

PhUSE-Talks2006

Thu, 09 Nov 2006 15:19:26 GMT

# [[TiddlyWiki - the software I wish I had written]]
# [[Gnit your own]] - creative uses of Unix Tools in Safety Programming
** [[Gnit Your Own - final]] (developed version of above but without tables)
# [[Why Safety Reporting IS like Rocket Science]]

Gnit your own

Thu, 09 Nov 2006 14:33:49 GMT

<>

--s--
! Creative Unix solutions for SAS programmer

Dave Garbutt

[[TU04|http://www.lexjansen.com/phuse/2006/tu/tu04.pdf]] @ PhUSE 2006, Dublin
+++^30em^[Abstract]<>
Unix text tools are perhaps partly responsible for its reputation as a system only for experts. I aim to show you how a little knowledge can go a long way to solving your everyday testing and validation problems. These are not tools for developing big user-friendly systems with, they are for getting fast answers for specific questions that will most likely never recur. The Unix one-liner is the epitome of a fast and light programming system and it is a perfect fit as a second skill for SAS programmers. This tutorial will work up from simple beginnings to show you how to gknit your own, but also give you some canned examples that will be useful today. Incidentally, Windows users should still come along because these tools are now available for Windows XP free from Microsoft.
===
--s--
! INTRODUCTION:
The hardest thing learning a new system is that lost feeling when you are faced with a problem you have no idea how to tackle.
!! This talk will
My idea in this talk is to give you a fast overview of
# what commands are available, and
# which problems they solve, and to
# how you can put them together to solve problems they cannot do alone.
# the power of [[regular expressions]]
--s--
!! Plumbing with pipes
Because [[Unix commands]] all can be fitted together in long sequences it is becomes easy to break complex tasks into sub-problems you know how to solve.
Perhaps you then find one step you cannot solve, then you can revisit the key tables here to get clues about how to tackle the problem.
--s--
!! Examples
I plan to take some examples, all starting from simple everyday questions,
* mainly to do with validating your work, and by
* building them up piece by piece illustrate
* how you can quickly learn to make fast one-line programs that will really help your everyday work.
--s--
!! In short...
* Quick solutions where writing a SAS program is not worthwhile.
* Any examples we don't cover here are available from the [[website|http://daveg.tiddlyspot.com/#Gnit your own]] for this talk and in the paper. The web site is hyperlinked and is recommended for browsing and copy&paste to a terminal session for experimenting.
--s--
! WHAT ARE UNIX TEXT TOOLS?
* a group of commands (i.e programs provided with the system) concentrated on reading, writing and selecting text.
* they are found on pretty well all systems
* although they fit together well, they are not totally integrated, but
* they are fast and easy to use after you have some familiarity
--s--
! WHAT OPERATIONS DO THEY DO?
* They do what you can do with SAS, //selecting// ''variables'' and or ''observations''
* and some tools
** can transform (edit) the values
** and calculate totals and other simple statistics
* and reformat the output
* and even do sorting and merging
--s--
! Classifying the operations Unix Text commands do
!! Commands that work on the whole file:
|Change content, by character|send content to pipe or commands|rearrange rows|h
| [[tr]], [[iconv]], [[wc]], [[expand]], [[unexpand]] | [[print]], [[echo]], [[cat]], [[tee]], $(--s--
! Classifying the operations Unix Text commands do
!! Commands that can //only// select observations
|by observation number|by content of whole line| by [[RE]]|by content of key fields|h
| [[head]], [[tail]], [[split]] | [[comm]], [[uniq]], [[sort]] -u | [[grep]], [[csplit]] | [[join]], [[comm]], [[sort]] -m |
--s--
! Classifying the operations Unix Text commands do
!! Commands selecting only columns
|keep by column number|drop by column number|keep by field|h
| [[cut]], [[col]] | [[colrm]] | [[cut]] |
--s--
! Commands able to select columns or observations
# Pipes constructed using previous commands
# Commands that are also scripting languages:
** [[awk]]
** [[sed]]
** [[perl]]
** [[ruby]]
--s--
! Classifying the operations Unix Text commands do
!! for detailed table see [[Capabilities of Unix Text commands]] or [[UnixTextTools table]]
> <>
+++^30em^[UnixTextTools table]<>
<>
===
!! Note on terms
* observations is approx = to rows
* but columns are not = to variables,
!! Unix text commands:
In <> check the section on text commands.

--s--
! HOW DO THEY FIT TOGETHER?
//Piper at the gates of dawn…//
> [[The pipe of piece]]
+++^30em^[The pipe of piece] <>
> <>
===
>
--s--
! REGULAR EXPRESSIONS – WILD WILD CARDS
Build up piece by piece testing as you go...

+++^30em^[Getting started with Regular Expressions] <>
> <>
===
--s--
! COMMONEST UNIX COMMANDS
> <>

--s--
! HOW DO PATTERNS OF USE OF UNIX TEXT TOOLS COMPARE TO SAS PROGRAMS?
!! Actually they are very similar!
** read data with set; add variable, drop variables, derive variables
** reformat data and print //nicely//
** sort data
** select unique observations
** count observations according to their content to make simple tables
** Join up datasets with merge
** Fit nonlinear models
* ...well it must be said the last is out of scope, but the others are not.
* although joining files is easier in SAS but
** for some small problems the text tools will see you through
** see example : of log checking
--s--
! HOW DO PATTERNS OF USE OF UNIX TEXT TOOLS COMPARE TO SAS PROGRAMS?
!! What is different from SAS about this way?
* + very fast and light to write and run
* + easy to test and develop (no compiling)
** (run, look at result, , edit line, ,...)
* + easy to read
* + easy to adapt
* - Not so readable when more than a few lines
* + program small enough to be self documenting
* + fast enough to run on significant amounts of data
--s--
! What is the Same?
* just like a complicated data manipulation in SAS
* you build it bit by bit by
## checking the output (dataset) as you go
## analysing what (observations, or variables) you still need to remove
## this is where the creativity of Gnitting lies, knowing (or guessing) where to start and
## when to stop cutting...

--s--
! EXAMPLE PROBLEMS - ILLUSTRATING THE BUILD IT BIT-BY-BIT METHOD:
List all examples:
<>

--s--
! CONVERTING ONE-LINERS TO SCRIPTS
#When?
#How?
--s--
! FPW (FREQUENTLY POSED WORRIES)
* [[Are your tips only for one kind of Unix, or one kind of shell?]]
* [[What about Windows?]]
* [[Won’t this take a long time, (taking up about 500KB) to run on my 200 listings?]]
* [[It looks like Chinese, how can I ever understand that gobbledegook?]]
--s--
! CONCLUSION
<<<
I hope I have convinced you it is worth learning to use Unix text tools for helping in your daily work.
Yes, it does take some effort: but they are light weight and once you have attained a certain level of familiarity you can use them for //ad hoc// problems that would not be worth writing a bigger SAS program for.
And, after getting what you need ''now'' in a few minutes, after a bit of head scratching and typing, and you'll be going home tonight with a bit grin, like the day you first..., well, you get the idea ;-)
<<<
* Unix text tools occupy a space complimentary to your SAS skills
* The rewards are worth the learning effort
--s--
! FURTHER READING
* Unix documentation for your system
* [[Unix Power Tools]] (OReilly)
* A shell programming guide
> <>

perl

Thu, 09 Nov 2006 14:29:47 GMT

<>

See also this introduction to Perl [[one-liners|http://www.builderau.com.au/program/unix/print.htm?TYPE=story&AT=320266188-339024638t-320000993c]]

UnixTextTools table

Thu, 09 Nov 2006 11:56:40 GMT

! UNIX TEXT COMMANDS:
* This table classifies the commands that can process text (files, or pipes) by the type of operations they can do.
* This enables you to easily find a command to do what you need.
* The next step is to refer to the man page, or try the defaults to see if that is enough.
* If the column marked edit is YES it means there is a way to change the values either of one field, or the whole record. In [[awk]] and [[sed]] this is done with the sub(stitute) functions.
* Although I have included perl here it is not much used for one-liners, but is a good basis for developing general programs.

!!!! Note:
* this table is sortable - click the link on the column to re-sort on that column. (one at a time :-)
* the column type is allocated as follows:
0 - operates on whole file
1 - operates on rows only
2 - operates on columns only
3 - operates on rows and/or columns

|Program|Type|Select Rows?|Select Cols?|Default field separator|Edit?|Multiple files?|Comments|h
|[[cut]]|2|NO|YES, by col number or field |-d"\t"|NO|YES||
|[[join]]|2|NO|YES,by field content |-t"\t"|YES, select any non-key columns|TWO files only|Print the common lines. Files must be sorted on the fields used|
|[[head]]|1|YES, first -n|NO|-|NO|YES|top of file or pipe|
|[[tail]]|1|YES, last -n|NO|-|NO|NO (some versions, YES)|bottom of file or pipe, -f option keeps dynamic watch|
|[[sort]]|1|YES|NO|-t"\t"|NO|YES|Sorts on entire record by default, can drop records with duplicate keys (-u) and merge files (-m)|
|[[fold]]|0|NO|NO|col number||NO|Wraps long lines|
|[[paste]]|2|NO|YES|-d"\t"|NO|YES|merges content of files in to one column by column|
|[[wc]]|0|NO|NO|||YES|Counts characters, words and lines|
|[[diff]]|0|NO|NO|-|NO|TWO files|prints differences between files|
|[[comm]]|3|YES|NO whole line is matched|-|NO|TWO files|list lines in common, or in only one of the files|
|[[col]]|2|NO|YES|||YES|processes reverse line feeds. Does not do what you think! Try [[cut]]|
|[[colrm]]|2|NO|YES|startcol - endcol|||copy only the given columns to std output|
|[[print]] [[echo]]|0|NO|NO||||Print the input (KSH Shells) |
|[[sed]]|4|YES|YES|none|||editing, line selection and substitution|
|[[spell]]|0|NO|NO|||YES|prints mis-spelled words|
|[[awk]]|4|YES|YES|-F" "|YES|YES|print matching records; select fields as $1,$2..., programmable|
|[[perl]]|4|YES|YES|||YES|Power string and data processing tool. OO programming|
|[[fmt]]|0|NO|NO|-|NO|YES|fill lines to the same length|
|[[look]]|3|YES|NO|-|NO|YES|Returns lines where start of line matches the sring given. File must be sorted|
|[[locate]]|3|YES|NO|-|NO|Finds file names|
|[[diff]]|0|NO|NO|-|NO|TWO|locates differences in the files|
| The separator is given with the option used to set it. \t means tab. Many awk versions allow a regular expression to be the separator. The separator can also be a non-printable character (e.g. \015, or ^L, page feed)|c
----

Colophon

Wed, 08 Nov 2006 14:28:00 GMT

This Tiddlywiki was built at tiddlyspot using the MPTW version.

The Extensions used are listed in the Extensions control Centre:
<>

* There are some stylesheet changes
** the main font is Trebuchet Ms
** long names in the side bar tabs are indented after the first line
** the sidebar tab is wider by default (20 vs 16em)
* the hove menu and related plugins allow easy navigation and also switching of focus by hiding the title bar and sidebars
* main extra is the plugin for running a slide show
* the tiddlerExcerpt is used to give the first line of a tiddler as tooltip rather than the default time & author info.
* the timeline is removed from tabs menu
* the author & time info is taken out of ViewTemplate because it is not needed
* the sortable table plugin is used for the [[UnixtextTools table]]. this means it is easy to focus on alphabetical reference //or// processing type as wished.
* QUOTD plugin is used to display a tip from [[BrianEno]]'s ObliqueStrategies. Often more cryptic than Unix :-)

Why Safety Reporting IS like Rocket Science

Wed, 08 Nov 2006 00:14:00 GMT

<>

--s--
! Why Safety Reporting IS like Rocket Science
[[Dave Garbutt|DaveG]]

[[AD13|http://www.lexjansen.com/phuse/2006/ad/ad13.pdf]] @ PhUSE 2006, Dublin
--s--
! Introduction
*I am going to explore ways in which safety reporting (SR)
IS
Like,
Rocket Science
*Along the way we will meet the SEL,
*Learn what 30 years research on software development has taught
*Make comparisons to SR
*And think about where we go next…
--s--
! Normal Software development
1. Requirements
2. Design
3. Code
4.Build
5.Test (? Go to 3)
6.Beta release
7.Final Push
8.Sales Push , Web Site
9.Money comes in
10.Minimal maintenance , given competition
--s--
! Software Development for Safety Reporting
9. Specs made according to 'standards', extended or modified by whim
8. Coding and checking by programmer
7. Database changes, additional tables
6. Modified headers, footers, subset, formatting
5. Dry run and test (lots of eyeballing and cross checking with specifications)
4. Checks of code or by re-programming by independent programmer
3. Data Base Lock
2. N days for validation and rework.
1.Ignition -
0. Lift OFF

--s--
! Rocket Science?
*YES, it is , because:
*No software patches up in Space
*10,9,8,7….0
*Bang!
*Everything has to work

* see [[this|http://today.reuters.com/news/articlenews.aspx?storyID=2006-11-06T191457Z_01_N06275670_RTRUKOC_0_US-SPACE-SHUTTLE.xml]]
for a different viewpoint.
* this 1996 article by [[Charles fishman:|http://www.fastcompany.com/online/06/writestuff_Printer_Friendly.html]]
--s--
! SR What is Different?
*Write once, use once
*We will run our programs on one set of actual data
*WE cannot test with exactly that set of data
*Data Checking or Program Validation?
*Do we Validate Programs?
*Or Check Listings?
*The answer is BOTH
*This is what makes SR software development different and more like Rocket Science
--s--
! The Software Engineering laboratory - it was Rocket Science
*Existed 1976 till 2001
*Actually measured performance of many software projects
*An amazing record of improvement of software quality
*Compared methodologies by experimentation and by results
*Defects per thousand lines of code
The SEL at NASA
<<<
The SEL has achieved productivity comparable to the average MIS or IT system, at the same time achieving quality levels that are at least 10 to 20 times better.
To put it a little differently, the average MIS shop would need about 14 calendar months and 110 staff-months to deliver a 100,000 line-of-code MIS system, and it would typically contain about 850 defects when delivered.
The NASA SEL would deliver a system of that size with about the same amount of time and effort, but it would contain only about 50 defects.
<<<

Source: [[http://www.stevemcconnell.com/sgcrib.htm]]

--s--
! What has / is SE telling us?
*Software Engineering has been a discipline for over 30 years
*Methodology matters
*Select correct methodology for situation
*Plan, Architect, Test
*Test:
*Units
*Integration
*Regression
*Review code
*Failure rates do not sum together
--s--
! SEL's Top Ten ways to reduce defects
1.Finding and fixing a software problem after delivery is often 100 times more expensive than finding and fixing it during the requirements and design phase.
2.About 40-50% of the effort on current software projects is spent on avoidable rework.
3.About 80% of the avoidable rework comes from 20% of the defects.
4.About 80% of the defects come from 20% of the modules and about half the modules are defect free.
5.About 90% of the downtime comes from at most 10% of the defects.
6.Peer reviews catch 60% of the defects.
7.Perspective-based reviews catch 35% more defects than non-directed reviews.
8.Disciplined personal practices can reduce defect introduction rates by up to 75%.
9.All other things being equal, it costs 50% more per source instruction to develop high-dependability software products than to develop low-dependability software products.
However, the investment is more than worth it if significant operations and maintenance costs are involved.
10.About 40-50% of user programs enter use with nontrivial defects.

--s--
! Waterfall If
*- The requirements are knowable in advance,
*- The requirements have no unresolved, high-risk implications,
*- The requirements satisfy all the key stakeholders' expectations,
*- A viable architecture for implementing the requirements is known,
*- The requirements will be stable during development,
*- There is enough calendar time to proceed sequentially. (USC)
--s--
! Incremental If-
*- The initial release is good enough to keep the key stakeholders involved,
*- The architecture is scalable to accommodate needed system growth,
*- The operational user organizations can adapt to the pace of evolution,
*- The evolution dimensions are compatible with legacy system replacement,
*- appropriate management, financial, and incentive structures are in place. (USC)

--s--
! Measurement and process improvement -SEL Don'ts
*Don't let team members work in an unsystematic way.
*Don't set unreasonable goals.
*Don't implement changes without assessing their impacts and obtaining approval of the change board
*Don't assume that a schedule slip in the middle of a phase will be made up later.
*Don't assume that a large amount of documentation ensures success.
*Don't overstaff, especially early in the project.
*Don't "gold-plate."

--s--
! Measurement and process improvement -SEL Do's
*Create and follow a Software Development Plan.
*Empower project personnel.
*Minimize the bureaucracy.
*Define the requirements baseline and manage changes to it.
*Take periodic snapshots of project health and progress,
*RE-plan, Re-estimate system size, effort, and schedules periodically
*Define and manage phase transitions.
*Start the project with a small senior staff.

--s--
! Recent trends in methodology
* The limitations of waterfall development have been widely recognized and
* Agile development has been born
* Xtreme programming, pair programming
* Test-driven Development
--s--
! Waterfallen - gather, design, do
*'Our process begins with requirements' says IT
*Expecting the user to know their development guidelines and bring a neat set of points and features.
*Which, with luck exactly fits the latest whizzpopper technology the developers all want to try…
--s--
! Waterfallen - blame the requirements
*This will NEVER happen.
*Why?
*Imagine asking a DOS user ca. 1982 for their system requirements for the new faster PCs
*Would they ask for Norton Commander integration or,
*Would they sketch this?

--s--
! The desktop….
* screenshot of Mac version 1 desktop
* and the grouch
--s--
! Software begins with NEEDS:
*To do your job more efficiently,
*More accurately
*Faster
*With less tedium
*In a new way that enables any or all of the above
*It is always easier to
*Critique, Suggest based on, or Tweak
*something than already exists
*Than it is to create.
*For this reason building bit by bit with feedback can get you further
--s--
! Methodology: test driven development
*It is becoming more and more accepted that test should be written with the code they test
*All trivial and other test cases should be done
*When you are putting software on a Rocket
*It better be tested before the button is pushed
*And my perception is that in SR we do not operate like this…
--s--
! Test, TEST, and test again
*When the data changes under the program and
*The only data that really matters arrives at the critical moment of blast-off
*Then if…
*you have validated programs (peer- reviewed, tested)
*And know they will run on standard testing data - still (to catch unexpected changes) and
*You can run independent checks on the output
*You will be a Rocket Scientist, my son!
--s--
! Test Oriented Development (I)
*Independent suite of checks on the output text
*- Goal - eliminate eyeballing
*Like Nature and Nurture the quality of deliverables is jointly the data and the transforms
*Goal - less in-fighting
*Tools to make individual tailored checking easier
*Goal - exploit people's brilliance
*Share code - share tests
*Goal- re-use of pre validated work
--s--
! TOD (II)
*Measure error and issue rates as well as deadlines
*Goal - reward accuracy and speed
*Use process control plots for error rates
*And for assessing data issues, and programming quality
*Goal: give statisticians an active QC role
*Publish the rates on the intranet
*Reward people that find errors! Do not solely praise staff that deliver on time.
*Always plot your data. Develop QC plots. Run as data arrives.
--s--
! TOD ( III )
*Make comparisons vs previous versions a routine
*Goal-> timing of when errors appear is vital for diagnosis
*If outputs have too much date & time identifiers produce also versions without or build filters
*Use metadata created from the listings to automate checks of patient counts
--s--
! IN SHORT:
*Integrate testing and quality control into the production process
--s--
! Conclusions
*We need a conversation in the industry about how to move quality forward in SR
*Comparing ourselves to Rocket Scientists makes more sense than comparing ourselves to Microsoft
*Goal-> feel good about our craft
*The combination of our unique needs:
*Data plus program is the delivery unit
*No beta phase allowed, no tests after ignition
*Immense pressure to shorten ignition to lift-off and orbit times
*Means we need a different methodology & testing strategy from the rest of the software industry
*TOD or death!

--s--
! Questions?
<<<
It is not because things are difficult that we do not dare,
it is because we do not dare that they are difficult.
<<<
--Seneca
--s--
! Further Reading:
* this 1996 article by [[Charles fishman:|http://www.fastcompany.com/online/06/writestuff_Printer_Friendly.html]]
* and [[this|http://today.reuters.com/news/articlenews.aspx?storyID=2006-11-06T191457Z_01_N06275670_RTRUKOC_0_US-SPACE-SHUTTLE.xml]]
for a different viewpoint and a slight oversight.

--s--
! Contact Me
* I would value your comments and questions on this paper.
* Please contact me via: DaveG
* A pdf version of this paper is available at [[Lex Jansen's web site|http://www.lexjansen.com/phuse/2006/ad/ad13.pdf]]

SideBarOptions

Tue, 07 Nov 2006 10:50:00 GMT

<><><><><><><><>

Creative Commons .

CheckSASLogs - Original Many Greps Approach

Mon, 06 Nov 2006 18:02:00 GMT

{{{
grep ^ERROR: *.log | grep -v "limit set by errors" | grep -v "errors printed on pages" >| _check.error.txt
grep ^STLERROR: *.log >| _check.stlerror.txt
grep ^WARNING: *.log | grep -v compression >| _check.warning.txt
grep ^NOTE: *.log | grep uninit >| _check.uninit.txt
grep ^NOTE: *.log | grep invalid >| _check.invalid.txt
grep ^NOTE: *.log | grep repeat >| _check.repeat.txt
grep ^DEVELOPER_WARNING: *.log >| _check.developer_warning.txt
}}}

Original from StevePike

See also [[chklogs]] which has a summary printing code added, and faster searching by using [[regular expressions]] to replace the pipelines and many checks shown here.

TiddlyWiki - the software I wish I had written

Mon, 06 Nov 2006 14:42:00 GMT

<>

--s--
!TiddlyWiki and MicroContent
Dave Garbutt

[[PD02|http://www.lexjansen.com/phuse/2006/pd/pd02.pdf]] @ PhUSE 2006, Dublin
--s--
!Introduction
*Follow this application up!
*What is a TiddlyWiki?
*What can I do with it?
*Why is it important?
*Find out more!
*The WIKIWikiWeb editable web sites
*A new niche in the paperless office is filled
--s--
!MicroContent?
*A TiddlyWiki keeps 'pages' and visible until you exit or close one. Each 'page' can be opened independently. This piece of genius - to change what seems 'normal' and 'the obvious way to do things'
*A document that is a single page application
*Free the paragraph from the prison of context
*The unit is the called a tiddler
--s--
!Problems with MacroContent
*Documents gets their structure from the closeness of paragraphs
*Therefore we have to have a reader in mind - an audience
>> It is an axiom well regarded that a document possessed of an author must be in search of a reader…
*But MicroContent can break this mould forever
*By allowing a combination of many audiences (and shared material) in one document
*Without dazzling the beginner or boring the expert

--s--
!Personal, nonlinear.extensible, web notebook
*Personal
*A single file
*No server needed
*Free, open source
*Web Notebook
*A TiddlyWiki is a single HTML file containing about 300k of JavaScript
*which manages the display and addition of tiddlers
--s--
!Non-linear
*there is no fixed order to the tiddlers
*You determine the order and
*What is visible
*Individualized document
*Structured with
*Links
*Tags
*Lists and summary tables or tabs of tiddlers
*Grouping tiddlers for opening as a unit

--s--
!Extensible and customisable
*CSS dynamic styling
*Plugin architecture e.g. In-line JavaScript:
{{{
config.macros.man = {};
config.macros.man.handler= function(place,macroName,params) {
var key=params[0];
wikify("[["+key+"|http://unixhelp.ed.ac.uk/CGI/man-cgi?"+key+"]]",place)
}
}}}
1.Copy it in a new tiddler,
2.tag the tiddler systemConfig,
3.save the TiddlyWiki,
4.reload into the browser.
5.Add this to your tiddler about the awk command: <>
--s--
!Using TiddlyWiki
*Adding information
*Formatting
*Tables, block quotes, preformatted, headers
--s--
!Structuring your information
*Linking, auto linking
*AutoLink WikiWords,
*Tagging
*Add keywords or phrases to label tiddlers
*Tagging can create structure content 'free'.
>For example consider tiddlers with Unix programming tips.
>> Tag each tip as you create it with the Unix commands used in it.
>> Then you can look at the autogenerated awk tiddler and see everywhere it is tagging,
>>> ie all the pages you thought were relevant to awk.
>> This can include tiddlers where awk is not mentioned in the text
--s--
!Structuring your Document
* Aggregating tiddlers
* Disaggregating
* Sequences
* Adding tags
* Authoring tools
--s--
!Sharing your TiddlyWiki
* Put on a web server
* A disk share
* A USB stick
* Use a server version
* Get a hosted TiddlyWiki
* Automatic sharing and updating is planned : to compete with portals costing millions
--s--
!Uses
* Journal, Diary and Day planner
* Technical notes
* Presentations
* Generating validation reports
* Construct from custom text files
* Delivering Documentation
--s--
!Creating a Validation document
{{{
find $PWD -type f -print | sort |
awk -v pwd=$PWD -v date="`date `" '
{if (NR == 1 ) print "|No.|File | OK? | Notes and comments | re-done OK? |h\n|>|>|All files in:|" pwd"|"date"|" }
{sub(pwd,".",$1); print "| "NR"|"$1" | | | |"}'
}}}
*prints plain text on the terminal like this:
{{{
|No.|File | OK? | Notes and comments | re-done OK? |h
|>|>|/vob/CMyPROJ/CMyPROJ0103/report|>|Thu Apr 6 17:14:11 DFT 2006|
| 1|./pgm_a/autoexec.sas | | | |
| 2|./pgm_a/pops.sas | | | |
| 3|./pgm_a/subpops.sas | | | |
| 4|./pgm_a/ds_aevs.sas | | | |
|>|>|>| and so on...|
| 21|./pgm_a/mk_trtm.sas | | | |
}}}
--s--
!Validation form…
*Giving a rendered table like this:
|No.|File | OK? | Notes and comments | re-done OK? |h
|>|>|/vob/CMyPROJ/CMyPROJ0103/report|>|Thu Apr 6 17:14:11 DFT 2006|
| 1|./pgm_a/autoexec.sas | | | |
| 2|./pgm_a/pops.sas | | | |
| 3|./pgm_a/subpops.sas | | | |
| 4|./pgm_a/ds_aevs.sas | | | |
|>|>|>|>| and so on...|
| 21|./pgm_a/mk_trtm.sas | | | |
--s--
!Demonstration
*Demo
*Look and feel
*Navigating around
*Adding text
*Tagging
*Journals
*Dcubed
*My tiddlyspot
--s--
!Frequently Posed Worries
*Scalability
*Above 2MB response slows down
*Privacy
*Not private
*Encryption available (but big plugin)
*Safety of typing investment
*OK
*Conversion to WORD
*Not much fun
*Till someone writes a WORD macro that converts Wiki text to styles / markup

--s--
!Conclusions
*For many of the examples I have given it is currently the best solution.
*Try it yourself:
*http://mptw.tiddlyspot.com
*Gnit your own:
* http://www.tiddlyspot.com

--s--
!Acknowledgements and thanks
*Jeremy Ruston for creating it
*and building a great community of developers
--s--
!Further Reading
*See the TiddlyWiki web site http://www.tiddlywiki.com
*The google groups
*The public tutorials
*The plug-in repositories
*All linked from the main site
! My [[PhUSE|http://www.lexjansen.com/phuse/2006/pd/pd02.pdf]] 2006 Presentations at Lex Jansen's website
--s--
!Questions?
<<<
It is not because things are difficult that we do not dare,
it is because we do not dare that they are difficult.
<<<
>--Seneca
--s--
!Contact Information
* I would value your comments and questions on this paper.
Contact details [[here|DaveG]]

WordCountMacro

Thu, 02 Nov 2006 09:55:00 GMT

/***
(Almost) as posted by BradleyMeck on the mailing list, 21-Oct-2006. To use put this somewhere in your ViewTemplate:
{{{

( words)

}}}
***/
//{{{
merge(config.macros,{
wordCount: {
handler: function(place,macroName,params,wikifier,paramString,tiddler) {
createTiddlyText(place,tiddler&&tiddler.text?tiddler.text.match(/\w+/g).length:"0");
}
}
});
//}}}

CheckSpaceOnSASTmp

Fri, 27 Oct 2006 17:20:00 GMT

!!! print space on sastmp as GB total & GB free
* For rows with a /dev. at start convert the 3rd & 4th field by dividing by 1024^^2^^
{{{
gbl df -k /proj/sastmp | awk '{ if ( $1 ~ /\// ) { print $1"\t" $2 / 1024 /1024 , "\t"$3 /1024 / 1024 ,"\t" $4 " " $5 " "$6, $7} else print }'

gbl running on the all my hosts : h1 h2 h3 h4 h5

Executing command on h1 -----------------------------------------------------------------------
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv_sastmp 12.75 7.92882 38% 5344 1% /proj/sastmp

Executing command on h2 -----------------------------------------------------------------------
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv_sastmp 64 59.67 7% 12915 1% /proj/sastmp

Executing command on h3 -----------------------------------------------------------------------
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv05 65 59.9316 8% 27023 1% /proj/sastmp

Executing command on h4 -----------------------------------------------------------------------
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv_proj 4 1.96415 51% 6497 2% /proj

Executing command on h5 -----------------------------------------------------------------------
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/lv03 15 11.8174 22% 10146 1% /proj/sastmp
>
}}}

* convert titles from 1024-k blovks
{{{
gbl df -k /proj/sastmp | awk '/^File/ {sub("1024-blocks"," - GB") } { if ( $1 ~ /\// && ! /^File/ ) { print $1"\t" $2 / 1024 /1024 , "\t"$3 /1024 / 1024 ,"\t" $4 " " $5 " "$6, $7} e
lse print }
}}}

SideBarTabs

Thu, 26 Oct 2006 09:58:00 GMT

Are your tips only for one kind of Unix, or one kind of shell?

Thu, 26 Oct 2006 09:29:00 GMT

<<<
No.
I have tried to use Unix commands available on all versions of Unix, and actually this is not hard to do, because the common, most-useful, commands came in to the Unix world early on and are universally available.

It is not true to say that all their options are the same (or mean the same across versions). So, if you see examples from this talk failing first check your systems man pages <>.
An obvious place where you may see this is in commands using cut because it is dependent on output being in fixed columns and the output of {{{ls -l}}} and {{{ps}}} for example are system dependent.

The few shell examples are run on [[Korn shell|http://en.wikipedia.org/wiki/Korn_shell]] which is becoming more widely available since it the source was opened by Lucent. The [[Bash shell|http://en.wikipedia.org/wiki/Bash_shell]] is widely available and is pretty compatible with Korn. Both of these shells descend from the Bourne Shell (sh), and can run Bourne shell scripts without change.
They have significant advantages over it for programming and interactive use.
<<<

GettingStarted

Thu, 26 Oct 2006 09:11:00 GMT

* Welcome to a Tiddly wiki contianing my talks from the PhUSE conference this year.
* For more about the ~TiddlyWiki hosting service ~TiddlySpot see [[http://www.tiddlyspot.com/]]
* For more about ~TiddlyWiki see my talk under the PhUSE-talks2006 and accessible from the menu. And also:
!Learn more about ~TiddlyWiki
Find out more about ~TiddlyWiki at [[TiddlyWiki.com|http://tiddlywiki.com]]. Also visit [[TiddlyWiki Guides|http://tiddlywikiguides.org]] for documentation on learning and using ~TiddlyWiki.

* the talks run as slideshows - click the slideshow button.

> for information on how this site is constructed, what [[TiddlyWiki|http://www.tiddlywiki.com]] plugins are used (and why) see [[Colophon]]

For internal info : [[GettingStarted at TiddlySpot]]

! [[Contact Me|DaveG]]

GettingStarted at TiddlySpot

Thu, 26 Oct 2006 08:56:00 GMT

Welcome to your brand new [[MonkeyPirateTiddlyWiki|http://simonbaird.com/mptw/]]. This is the standard empty [[TiddlyWiki|http://www.tiddlywiki.com/]] (version <>) preconfigured with a few bits and pieces from MPTW, in particular the layout, the colours, and the popular [[TagglyTagging|http://simonbaird.com/mptw/#TagglyTagging]]. If you're new to ~TagglyTagging then try the (slightly out-of-date) [[FAQ|http://simonbaird.com/mptw/#TagglyTaggingFAQ]] and [[Tutorial|http://simonbaird.com/mptw/#TagglyTaggingTutorial]].

To get started with this blank TiddlyWiki, you'll need to modify the following tiddlers:
* SiteTitle & SiteSubtitle: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* MainMenu: The menu (usually on the left)
* DefaultTiddlers: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <

AboutTiddlySpot

Thu, 26 Oct 2006 08:53:00 GMT

!Welcome to your ''tiddlyspot.com'' ~TiddlyWiki!
''[[tiddlyspot.com|http://tiddlyspot.com]]'' gives you an instant [[TiddlyWiki|http://tiddlywiki.com]] hosted on our ''tiddlyspot.com'' servers.

Want to work online? No problem, you can go to your ''tiddlyspot.com'' URL (which is http://DaveG.tiddlyspot.com/index.html ) and start editing. Click "save to web" and your changes are saved directly to your ''tiddlyspot.com'' home -- no messing about with local files or ftp.

Want to work offline? No problem, your ''tiddlyspot.com'' ~TiddlyWiki is a real, fully functioning ~TiddlyWiki that you can save onto your hard drive or USB stick. Use the link below to save to your local computer. As you make changes, use the "save to disk" button to save to your local file. Whenever you're ready to sync up again, just click "save to web".

!To save online
Enter the upload password provided when you created your ~TiddlyWiki. Then click the "save to web" button below (or in the right side column) to save your ~TiddlyWiki.
Upload Password: <

DaveG

Thu, 26 Oct 2006 08:45:00 GMT

David J Garbutt
BSI AG
Täfernstrasse 16A
CH - 5405 Baden-Dättwil
Work Phone: +41 56 484 1920
Fax: +41 56 484 1930
Email: [[=djg|http://public.xdi.org/=djg]]
Web: www.bsiag.com

sample table

Wed, 11 Oct 2006 10:41:00 GMT

|No.|File | OK? | Notes and comments | re-done OK? |h
|>|>|/vob/CMyPROJ/CMyPROJ0103/report|>|Thu Apr 6 17:14:11 DFT 2006|
| 1|./pgm_a/autoexec.sas | | | |
| 2|./pgm_a/pops.sas | | | |
| 3|./pgm_a/subpops.sas | | | |
| 4|./pgm_a/ds_aevs.sas | | | |
…
| 21|./pgm_a/mk_trtm.sas | | | |