Custom Query (432 matches)
Results (286 - 288 of 432)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #84 | fixed | GB2007/06, flight day 192a/2007, Dorchester | mggr | mggr |
| Description |
Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_06-2007_192a_Dorchester Data arrived from ARSF via second SATA disk transfer at the start of Sept. Scientific details: See ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007/GB07-06_* Initially this was thought to be a lidar only flight due to a permissions problem with transferring the CASI datasets. Created as a job in Nov. PI: Doreen Boyd Sensors:
|
|||
| #85 | fixed | GB2007/03, flight day 233/2007, "Four Welsh sites" | mggr | mggr |
| Description |
Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_03-2007_233_Four_Welsh_sites Data arrived from ARSF via second SATA disk transfer at the start of Sept. Scientific details: See ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007/GB07-03_* Initially this was thought to be a lidar only flight due to a permissions problem with transferring the CASI datasets. Created as a job in Nov. |
|||
| #88 | fixed | Restricting level 1 processing by scan line causes error | mggr | anee |
| Description |
The use of -l in azspec produces a blank image if anything than a start line of 0 is used. The end line number does seem to produce the correct effect however. Same problem also occurs in azatm (causes errors saying "scan jump from: 0 to 191119 scan : 191119 rejected"). Same option in azcas2 seems to work correctly. |
|||