Opened 7 months ago

Last modified 4 months ago

#738 new flight processing

CarbonARA25, flight day 289/2025, Brazil

Reported by: petwa Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description

/users/rsg/arsf/arsf_data/2025/flight_data/brazil/CarbonARA25-2025_289_Brazil/

Data arrived on 01/04/2026
PI: Martin Wooster
Sensors:
-Owl
-Fenix1k
-IBIS

Change History (26)

comment:1 Changed 7 months ago by petwa

Project unpacking

Fenix1k:
All OK.

Owl:
All OK.

Ibis:
There is missing calibration file in dir i25289_0006
There is missing calibration file in dir i25289_0009
Moved to not-working

run_unpacked_checks.py found nav file errors in all Fenix1k flightlines.

comment:2 Changed 7 months ago by mark1

Looking at Ibis data, there are missing dark frames for some lines:
IBIS289-25-2
IBIS289-25-3
IBIS289-25-5
IBIS289-25-6
IBIS289-25-9
IBIS289-25-21
IBIS289-25-28
IBIS289-25-31
IBIS289-25-40
IBIS289-25-43
IBIS289-25-44

It would be possible to process using dark frames from neighbouring files but with increase in uncertainty of radiometric calibration.

comment:3 Changed 7 months ago by mark1

Last edited 7 months ago by mark1 (previous) (diff)

comment:4 Changed 7 months ago by mark1

Doesn't seem to be a logsheet for this flight to check against any details.

comment:5 Changed 7 months ago by mark1

Have sent the Owl data calibration processing to the grid.

comment:6 Changed 7 months ago by mark1

Sent the Ibis and Owl mapping to the grid.

comment:7 Changed 5 months ago by mark1

Renamed wavelengths for Ibis to match the new calibration file.

comment:8 Changed 5 months ago by mark1

Ibis SCTs are mostly 0 except for the below, some of which are due to misrecording of dropped frames:

Line 5: sct = -2.08
Line 8: sct = 0.12
Line 12:sct = 0.05
Line 32 sct = -2.12

comment:9 Changed 5 months ago by mark1

Ibis ready for delivery check

comment:10 Changed 4 months ago by petwa

Owl SCTs set to 0.0

Flightline 13 was at a lower altitude and showed saturation in the higher bands so removed from the delivery.

The area covered by the flightlines was very large and this broke the readme processing when run on pmpc1766. Imagemagick policies had to be updated to increase allowed image size and cache.

  <policy domain="resource" name="width" value="32KP"/>
  <policy domain="resource" name="height" value="32KP"/>
  <policy domain="resource" name="disk" value="8GiB"/>

comment:11 Changed 4 months ago by petwa

Owl delivery, CarbonARA25-289-owl-20260701, ready for checking.

comment:12 Changed 4 months ago by asm

OWL Delivery Check
Started

comment:13 follow-up: Changed 4 months ago by asm

OWL Delivery Check

No readme, started one. From the 12 flightlines included, only 2 lines are in zone UTM22S and the 10 in UTM21S. Furthermore, all CarbonARA projects have been delivered with UTM21S. Therefore files need to be remapped to UTM21S.

As this is an OWL processing (which different structure for processing level1b), the simplest way would be to get from the logs the apltran and aplmap and do a loop.

comment:14 Changed 4 months ago by asm

Fenix processing

Flightlines 1 - 10 have the best alignment with SCT +0.02, the rest with SCT +0.10.

Last edited 4 months ago by asm (previous) (diff)

comment:15 in reply to: ↑ 13 Changed 4 months ago by petwa

Replying to asm:

OWL Delivery Check

No readme, started one. From the 12 flightlines included, only 2 lines are in zone UTM22S and the 10 in UTM21S. Furthermore, all CarbonARA projects have been delivered with UTM21S. Therefore files need to be remapped to UTM21S.

As this is an OWL processing (which different structure for processing level1b), the simplest way would be to get from the logs the apltran and aplmap and do a loop.

Sorry Aser. I had done a readme but not copied it to the correct place. It is there now.

comment:16 Changed 4 months ago by asm

OWL Delivery Check

Apologies, I made a mistake looking for the location online. This flight is all UTM22S so will continue with DC.

comment:17 Changed 4 months ago by asm

OWL Delivery Check

-The logsheet margins are a bit off but this is fine
-The DEM was symlinked and have been replaced with the files
All other checks have been run and passed. I have zipped the owl files and will mark this project as ready to be delivered.

comment:18 Changed 4 months ago by asm

Fenix1k Delivery

This dataset is ready for DC. I zipped the mapped files by mistake, those are unzipped now but the zip files are also there. Once the DC is done, you don't need to map the files again and simply need to delete the unzipped files.

comment:19 Changed 4 months ago by asm

Ibis DC

Started

comment:20 Changed 4 months ago by asm

Ibis DC

Removed ASCII file and ASCII section in readme. Added mosaic screenshot in readme. For the files with overflows, all lines were overflowing (the script missed a few) so adjusted the table. When there were no overflows raised, there was indeed no overflows.

All other checks have been carried out and passed.

I am currently zipping mapped files. Once those have been zipped successfully, will deliver.

comment:21 Changed 4 months ago by asm

Ibis DC

All mapped files have been zipped successfully. I will start upload.

comment:22 Changed 4 months ago by asm

IBIS
Data has been delivered to PI via S3 bucket and notified - Sunday 12th July 2026.

comment:23 Changed 4 months ago by petwa

Fenix1k DC

Started

comment:24 Changed 4 months ago by petwa

Fenix1k DC

Readme:
Flightline mosaic does not look right. It is different to the screenshots and l1b/l3b.
Some flightlines target fires (Eg 21/22). It look like they have decreased the sensitivity so the normal vegetation is very noisy -still saturates over fire. Should this be flagged in the quality section?

comment:25 Changed 4 months ago by asm

Fenix1k Delivery

Fixed mosaic in readme. I copied wrong mosaic into /tmp/ dir to reduce size. Fixed now.

If you want, please add a sentence in your own words about the issue you raised in the data quality report. Please note the zipped files are already in the mapped directory so simply need to delete the unzipped files and upload to S3 bucket once you are happy with the delivery.

comment:26 Changed 4 months ago by petwa

Fenix1k Delivery

Delivery uploaded to S3 and email sent.

Note: See TracTickets for help on using tickets.