| 75 | | 1. Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...) |
| 76 | | * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc |
| 77 | | |
| 78 | | ** IMPORTANT ** [[BR]] |
| 79 | | If there is no space in the repository then it will need to go into archive-over-flow temporarily (~arsf/arsf_data/YYYY/flight_data/archive-overflow). Make a note in ticket (once you've created it!) saying that this project is in non-backed up space. |
| 80 | | |
| 81 | | 2. Copy project structure with sym links to ~arsf/workspace. You can either do this manually or with: |
| 82 | | |
| 83 | | fastcopy_arsf_proj_dir.sh <source project directory> <target project directory> |
| 84 | | |
| 85 | | Note: Be logged in airborne when you create the directory and the initial files in the workspace or you won't have write permission. |
| 86 | | * '''Obsolete: Only do this to generate old-style scripts.''' For each project directory run 'generate_qsub.py -d <project directory>' |
| 87 | | * This will generate a qsub command script for use to submit processing of all eagle, hawk, atm and casi flight lines to the grid nodes. |
| | 75 | Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...) |
| | 76 | * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc |