| 24 | | == Authentication, access control, and quotas == |
| 25 | | |
| 26 | | Users (that is, job submitters) must create an account on the BOINC project; |
| 27 | | this is done using a form on the project web site. |
| 28 | | A project administrator |
| 29 | | must then grant the user the right to submit jobs for LAMMPS |
| 30 | | (and potentially for other applications). |
| 31 | | Optionally, a designated user may be given the ability to |
| 32 | | grant access rights to other users. |
| 33 | | Each user has an associated "quota" that determines their |
| 34 | | share of processing power. |
| 35 | | |
| 36 | | == Per-user file sandbox == |
| 37 | | |
| 38 | | LAMMPS input files can be large, |
| 39 | | and it would be inconvenient to upload these files each time jobs are submitted. |
| 40 | | Instead, we allow users to maintain a set of files on the project server; |
| 41 | | this is called the user's "file sandbox". |
| 42 | | |
| 43 | | Using a web interface, users can |
| 44 | | |
| 45 | | * upload files from PC to sandbox |
| 46 | | * view the files in their sandbox, including size and MD5. |
| 47 | | * download files from sandbox to PC |
| 48 | | * delete files from the sandbox |
| 49 | | |
| 50 | | Files in the sandbox can be modified, |
| 51 | | and all old versions are retained on the server. |
| 52 | | When a batch of jobs is submitted, |
| 53 | | it uses the input file versions at the moment of submission, |
| 54 | | even if the files are then modified while the batch is in progress. |
| | 24 | The system uses BOINC's [FileSandbox file sandbox] for managing input files. |