documents:100922imagej_cluster
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| documents:100922imagej_cluster [2010/10/05 09:58] – kota | documents:100922imagej_cluster [2010/10/05 10:28] – kota | ||
|---|---|---|---|
| Line 160: | Line 160: | ||
| ===== Automated Script (Only from within EMBL network) ===== | ===== Automated Script (Only from within EMBL network) ===== | ||
| - | Automated Script is available in ALMF server (clust5fullp.sh). With this script, you only need to invoke the script with two arguments. | + | Automated Script is available in the ALMF server (clust5fullp.sh). With this script, you only need to invoke the script with two arguments. |
| * arg[0]: full path to the directory containing image/stack files | * arg[0]: full path to the directory containing image/stack files | ||
| * arg[1]: name of the imageJ macro you want to apply. | * arg[1]: name of the imageJ macro you want to apply. | ||
| Line 177: | Line 177: | ||
| </ | </ | ||
| - | The script could be vied in the link below: [[http:// | + | This script will create two new folders in the directory same as where the image directory is (*_job and *_proc). Processed images or stacks will be saved under *_proc. \\ |
| + | Besides, so-called job reports (text files containing output messages) will appear in your current directory where you executed the command. | ||
| + | |||
| + | The script could be viewed | ||
| ===== Example Scripts ===== | ===== Example Scripts ===== | ||
documents/100922imagej_cluster.txt · Last modified: 2016/05/24 12:46 by 127.0.0.1