Opened 3 months ago

Last modified 3 days ago

#653 new flight processing

HyTES/19, flight day 169/2019, Grosseto

Reported by: wja Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: dac@… Other processors:


Data location: /users/rsg/arsf/arsf_data/2019/flight_data/italy/HyTES19-2019_169_Grosseto

Data arrived from Kings College London via hardisk on July 15 2019.

Scientific objective: Joint NASA and ESA campaign flying JPL’s HyTES thermal instrument over sites in Europe with a focus on crops and soil. Aim is to inform the future Land Surface Temperature Monitoring (LSTM) satellite mission. The NCEO Fenix instrument was flown alongside HyTES to provide visible – SWIR hyperspectral data.

PI: Martin Wooster


Fenix (requested, flown)

Change History (10)

comment:1 Changed 3 months ago by wja

Navigation Processing
Basestation data converted to RINEX. Of the three RINEX files (which contain multiple days of data), a file for this date has been created with the following command:

teqc -st 2019_06_18:06:58:00.770 -e 2019_06_18:11:25:33.840 +nav Default_9488_1806_065800.19n Default_9488_0509_114526.m00 > Default_9488_1806_065800.19o

comment:2 Changed 7 weeks ago by wja

Navigation Processing
PPP processing in IPAS-TC hung at 57% of the reverse process step. Will return to processing this.

comment:3 Changed 7 weeks ago by wja

Navigation Processing
PPP processing completed using IPAS-TC. SOL file generated.

comment:4 Changed 7 weeks ago by wja

  • Cc dac@… added

comment:5 Changed 6 weeks ago by seg

Fenix Processing
Started processing
GPS end time had to be changed for

  • FENIX-169-12.hdr
  • FENIX-169-14.hdr
  • FENIX-169-3hdr
  • FENIX-169-4hdr
  • FENIX-169-6hdr

This was because the start time was the same as the end time. Minute was added to end time for these files to allow generation of config file

Last edited 6 weeks ago by seg (previous) (diff)

comment:6 Changed 4 weeks ago by seg

Fenix Processing

SCT values identified

Flightline FENIX
1 .00 4
1.01 4.4
1.02 5.1
2 3.2
3 79.7
4 12.4
5 15.7
6 67
7 3.2
8 2.7
10 3.2
11 2.6
13.00 4.4
13.01 5
13.02 5.7
14 159.9
15 4
16 2.9
17 3.4

Flight Lines 9 and 12 were broken flightlines so will not be processed

comment:7 Changed 9 days ago by seg

Fenix Processing

Possible FPS issues, requires other opinion

comment:8 Changed 9 days ago by wja

Fenix Prcoessing

comment:9 Changed 9 days ago by wja

Fenix Processing
I reprocessed 3-band lines and found:

  • Flightlines 1, 13 & 14 look like there is a Frames per Second (FPS) error.
  • It is hard to initially tell if lines 7, 8, 10, 11, 15, 16 & 17 have FPS errors.
  • Lines that look fine: 2, 3, 4, 5 & 6.

Probably best to manually determine a suitable FPS value (can be changed in the Fenix header files grep *hdr -e 'fps =').
Lines 1 & 13 have FPS values of 79.000.
All other lines have values of 27.000.
Perhaps it is worth see if FPS values of 27.000 works well with lines 1 & 13 (two of the three immediately visible FPS errors).
Also note that if a line is split (e.g lines 1 & 13), all parts should have the same SCT values.

Last edited 9 days ago by wja (previous) (diff)

comment:10 Changed 3 days ago by wja

Hyperspectral Process
I have changed the FPS of lines 1 & 13 from 79.000 to 27.000 and processed all lines.
The new FPS for lines 1 & 13 is clearly worse. However, the reprocessed lines 14, 15, 16 & 17 also show significant SCT (and/or possible FPS errors).
Will continue to investigate.

Note: See TracTickets for help on using tickets.