|
Size: 984
Comment:
|
Size: 1417
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| * {{{SENSOR/LEVEL/HEMISPHERE/YEAR/MONTH/DAY}}} for the incoming satellite data (radiances) | * {{{SENSOR/LEVEL/HEMISPHERE/YEAR/MONTH/DAY}}} for the incoming satellite data (radiances). |
| Line 15: | Line 15: |
{{{HEMISPHERE}}} should be set to {{{NORTH}}} or {{{SOUTH}}} if applicable. For example, this is not the case for AMSR-E L1A swath data but for gridded data (L3) === Data Level === * Level 0 (L0) are the raw observational data. * Level 1 (L1) are the calibrated radiances on a swath basis. * Level 2 (L2) are the derived products on a swath basis. * Level 3 (L3) are the derived gridded products. === Backup === |
Linux Server snow
- 3 nodes each with 32 AMD Opterons (2.3 GHz) and 128 GB RAM
- snow1 and snow2 for interactive use, snow3 for batch processing
Directory structure
The following structure under /scratch/clisap/seaice shall be used if applicable:
SENSOR/LEVEL/HEMISPHERE/YEAR/MONTH/DAY for the incoming satellite data (radiances).
OWN_PRODUCTS/PRODUCT_NAME/HEMISPHERE/YEAR/MONTH/DAY for the own derived products (final results)
TMP/uxxxxx/ for intermediate (temporary) data
HEMISPHERE should be set to NORTH or SOUTH if applicable. For example, this is not the case for AMSR-E L1A swath data but for gridded data (L3)
Data Level
- Level 0 (L0) are the raw observational data.
- Level 1 (L1) are the calibrated radiances on a swath basis.
- Level 2 (L2) are the derived products on a swath basis.
- Level 3 (L3) are the derived gridded products.
Backup
Please note that there is no backup. Original data shall be stored elsewhere.
Permissions
As the data are used by the whole seaice group the permissions should be granted. You can use chmod -R g+rw DIRECTORY/ to set the permissions recursively for a directory.
Python
module load R/2.7.0 module load Python/2.6.2