Difference between revisions of "Icommands"
| Line 25: | Line 25: | ||
<!--Modules--> | <!--Modules--> | ||
| − | == | + | ==Environment Modules== |
| − | + | Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application. | |
| − | |||
| − | < | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==System Variables== | ==System Variables== | ||
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory | * HPC_{{uc:{{#var:app}}}}_DIR - installation directory | ||
Revision as of 13:36, 13 June 2022
Description
iCommands is a collection of commands for Unix and Windows that are used in the iRODS system to interact with the CyVerse Data Store. Many commands are very similar to Unix utilities. For example, to list files and directories, you use ls in Linux, but in iCommands you use ils.
While iCommands are great for all transfers and for automating tasks via scripts, they are the best choice for large files (2-100 GB each) and for bulk file transfers (many small files). For a comparison of the different methods of uploading and downloading data items, see Downloading and Uploading Data.
Using iCommands with your CyVerse username and password allows you access to all files that have been shared by other users; however, you can download data sets that have been made public without a CyVerse account.
Environment Modules
Run module spider icommands to find out what environment modules are available for this application.
System Variables
- HPC_ICOMMANDS_DIR - installation directory
Additional Information
Since iCommands binaries are not compatible with our system iCommands binaries have to be launched with the 'launch_icommands' command.
For example:
$ module load icommands $ launch_icommands ienv -h