Skip to main content

Synthetic Data Server

Info on Synthetic Data Server (SDS):

Access to ECCO

The Economics Compute Cluster (ECCO) has migrated to the BioHPC environment, and accounts are not handled on this website anymore. See the BioHPC User Guide.

Latest Tweets

VirtualRDC
@VirtualRDC

Using Globus Online

Print Friendly, PDF & Email

Globus Online is a (primarily) web-based interface to GridFTP that has been designed to be much more user-friendly. The basic principle is the same as for GridFTP: you initiate transfers between points X and E (XSEDE and ECCO) from a third location (for instance, your browser), at high speeds. You can also use it to transfer data from your local computer to ECCO. Instructions for all operating systems can be found here: https://support.globus.org/entries/23583857-Sign-Up-and-Transfer-Files-with-Globus-Online (as of 2014-08-13).

The ECCO endpoints start with 'ecco#', and there are two:

  • ecco#home - your home directory, as well as the project space (/home/ssgprojects), allowing for most transfers at the highest speed.
  • ecco#scratch-0-2 - corresponds to compute-0-2:/scratch (i.e., the scratch space on compute node 2) [not yet active]
When prompted for ECCO or CAC credentials, simply enter your ECCO login and password (do NOT enter your NetID campus-wide password!).

Transferring files between ECCO and your laptop or workstation

Globus Online can be used to transfer data to and from your workstation or laptop. Windows and OS X users will want to use the installers on the Globus Online site. Linux users (RedHat, openSUSE, Ubuntu, Debian) may want to use the following re-packaged installer, which provides for desktop integration otherwise missing from the Globus Online instructions:

You should be able to find the Globus Connect application in your menus or app launcher.

Transferring files between ECCO and XSEDE resources

For XSEDE credentials, use the credentials for the resources that you are transferring data to and from (you can look them up on your XSEDE User Portal). You will need to know the name of your XSEDE endpoint.