Test+Problem+Uploads

=Test Problem Data Upload= Pages: Workshop, Overview, CADAC, **Data Access**, Work Area Setup, Path Setup, Utilities, Grid Data, SPH Data, Running, Reporting, LOG

You need a CADAC account to upload results and access the analysis software. See also the information about data access.

Normal scp
For smaller amounts of data (up to 256^3, say), use normal **scp** commands. Use files containing single snapshots, or pieces of single snapshots. If your MPI data format is split into CPU-local files it may be advantageous to keep this split while transferring the data, since you can then start a (possibly large) number of scp's in parallel! A typical command would be (assuming you have the same login name on your own system as on **datastar**): code scp snapshot.dat snapshot.dim $user@dslogin.sdsc.edu:/dsgpfs/$user & code You may want to use a script to start many such commands in parallel.

TeraGrid or similar protocols
It may be advantageous to use standard [|TeraGrid data transfer procedures], or some similar method. This may require compiling client software on your local system, if the software is not already available there. We will look into this in more detail -- **//please add useful information or experience that you may have in this respect!//**

Saving your files under the Storage Resource Broker system
Please note that you are not supposed to put large data files under your home directory on **datastar**, and that files under **/dsgpfs/$user** and **/gpfs-wan/scratch**/$user are scrubbed regularly by SDSC procedures. So, please make sure to save the files you upload, by using **Scd+Sput** to put them under your SRB home. Example: code Sinit                       # initialize your access to the SRB system Smkdir KITPcompare07        # make a directory there (if not there already) Scd KITPcompare07           # use that as the current working dir on the SDR side cd /dsgpfs/$user            # change directory on the UNIX side to where you uploaded the files to Sput -a mydata.dim           # Sput the small .dim file Sput -a mydata.dat          # Sput the large .dat file code

Maintaing consistency between UNIX and the Storage Resource Broker system
If your remove files from the SRB system with **Srm** you need to run **Srmtrash** to ensure that the files are actually removed also from the UNIX view of the SRB system. Example: code Sput -a test.txt                                                                    # a small test file ls -l /gpfs-wan/projects/cadac/srbVault/$user.cadac/home/$user.cadac/KITPcompare07  # check that it can be seen from UNIX Srm -a test.txt                                                                     # remove it from the SRB system ls -l /gpfs-wan/projects/cadac/srbVault/$user.cadac/home/$user.cadac/KITPcompare07  # it may still be visible under UNIX Srmtrash                                                                            # enforce consistency ls -l /gpfs-wan/projects/cadac/srbVault/$user.cadac/home/$user.cadac/KITPcompare07  # check that it cannot be seen from UNIX code