Test Files Upload

There are two ways to upload the 13 test files for each chamber to the alice machine at PI-Heidelberg (the machine that hosts the gateDB database and accompanying interfaces):


Files Format: please make our lives easier by following the requiered format for these files - any format change likely implies modifications in our scripts that extract and commit your data to the gateDB database. The data content is described in the ''TRD chamber testing'' manual. Also, the actual test results files for chamber L1C1-025 can be downloaded as format examples: For questions please write me: Paul Constantin
Bulk file transfer via scp: we created on host alice.physi.uni-heidelberg.de a directory tree to hold the ROC test data and its general format is /alice1/trd/TestROC/XXXX/YYY where XXXX stands for the ROC type (for eg. XXXX='L1C1') and YYY stands for the ROC number from '000' to '099' (for eg., YYY='025' for chamber number 25). Hence, on any machine that runs scp, do:
scp * user@alice.physi.uni-heidelberg.de:/alice1/trd/TestROC/L5C1/037
to transfer all 13 files of chamber L5C1 number 37. Note that you have all rights in those directories, hence you can do anything you want, after an ssh followed by a cd to them. Usernames and passwords will be granted via e-mail upon request. There are many ways to install (free of charge) ssh/scp on your Windows machine (Linux already has it), putty is one of them.
Again, for questions please write me: Paul Constantin
Individual file upload: please use the form below to upload individual test files. Choose the chamber type, type in its number, choose the test type of the particular file, and click ''Browse...'' to browse your local filesystem for your file; finally, when all these parameters are set, click ''Upload'' to submit your file.

   '; print '   '; print '   '; print '   '; print ''; print '   '; print ''; print '

Note: due to the lack of portability of multi-files HTML uploads (different behaviour in different web browsers and even operating systems), we prefer not to offer this possibility as it could lead to impredictable behaviour of our server-side scripts - we consider the scp transfer described above to be much safer.

'; ?>