Skip to content

Miscellaneous

How does the Pipeline determine which days to process?

The general philosophy of this pipeline is that “it populates output directories, with minimal internal queuing logic”. This means it does not track which processes it has already run. If you point it to some input and output directories, it will produce any output that is not there and use the output directories as a source of truth, “which processes have already been run”.

If it finds an output directory for a sensor-day combination (and selected retrieval algorithm and atmospheric profile model), it will not re-retrieve it. If you want to re-retrieve something because the inputs have changed (which should usually not happen), you have to delete the respective output directory or point the pipeline to a new output path.

How to interpret the preprocessing error flags in Proffast 2.X?

The error flags are added up in the following way:

  • errflag  = 0: no error
  • errflag += 0.000.000.001 or 0.000.000.002: solar elevation below 1 deg
  • errflag += 0.000.000.010 or 0.000.000.020: DC mean too low (below DCmin)
  • errflag += 0.000.000.100 or 0.000.000.200: DC variance too high (above DCvar)
  • errflag += 0.000.001.000 or 0.000.002.000: DC correction failed
  • errflag += 0.000.010.000 or 0.000.020.000: Not enough ifg points available on any side of the ifg for requested resolution
  • errflag += 0.000.100.000 or 0.000.200.000: Out-of-band artefacts are too strong
  • errflag += 0.001.000.000 or 0.002.000.000: Not enough points available for calculating phase spectrum
  • errflag += 0.010.000.000 or 0.020.000.000: Invalid spectral calibration
  • errflag += 0.100.000.000 or 0.200.000.000: Check consistency of fwd and bwd pair of spectra
  • errflag += 1.000.000.000 or 2.000.000.000: Phase error > 0.005

The numeric values are the same for errflag_CO, but some of the steps/checks are not performed on the CO band.

What are the Units in the output files

VariableUnit
gndPhPa
gndTK
latdegdegrees
londegdegrees
altimmeters
appSZAdegrees
azimuthdegrees
XH2Oppm
XAIRno unit (ratio)
XCO2ppm
XCH4ppm
XCOppm
XCH4_S5Pppm
H2Ono unit (number of molecules)
O2no unit (number of molecules)
CO2no unit (number of molecules)
CH4no unit (number of molecules)
COno unit (number of molecules)
CH4_S5Pno unit (number of molecules)

Preprocess 5 in Proffast 2.3 fails with “Warning: inconsistent dualifg!”

We observed that Preprocess 5 (when using Proffast 2.3) cannot handle our old interferograms. The preprocess stops with the error message “Warning: inconsistent dualifg!”. However, we can still process the interferograms with Preprocess 4 (using Proffast 2.2).

The log of the preprocess for these days looks like this:

================= Task 0 ================
/home/moritz-makowski/Documents/pipelines/erp-new-pressure/data/containers/retrieval-container-angry-benz/prf/preprocess/preprocess5 preprocess5ma_161102.inp
Return code: 1
Output:
Reading input file...
Done!
Number of raw measurements to be processed: 3131
Reading file names
/home/moritz-makowski/Documents/pipelines/erp-on-demand/data/containers/retrieval-container-angry-benz-inputs/ifg/161102/161102SN.2853
/home/moritz-makowski/Documents/pipelines/erp-on-demand/data/containers/retrieval-container-angry-benz-inputs/ifg/161102/161102SN.891
...
/home/moritz-makowski/Documents/pipelines/erp-on-demand/data/containers/retrieval-container-angry-benz-inputs/ifg/161102/161102SN.3016
Done!
Read OPUS parms: 1
/home/moritz-makowski/Documents/pipelines/erp-on-demand/data/containers/retrieval-container-angry-benz-inputs/ifg/161102/161102SN.2853
Warning:
inconsistent dualifg!
This is a critical error. Quiet run option selected: End Programm
Errors:
inconsistent dualifg!
============================================
============================================

Can I use the PyPy interpreter to make the Pipeline faster?

Maybe, but this is not tested. Since the pipeline spends almost the entire time on IO or running Fortran programs, using a faster Python interpreter will not have a measurable impact on the runtime.

What do the parameters in the OPUS files mean?

The list below was blatantly stolen from the TCCON wiki (https://tccon-wiki.caltech.edu/Main/I2SAndOPUSHeaders).

Parameter IDDescription
Instrument Parameter
DURScan time [seconds]
PKAPeak Amplitude
PKLPeak Location
PRABackward Peak Amplitude
PRLBackward Peak Location
HFLHigh Folding Limit
LFLLow Folding Limit
LWNLaser Wavenumber
SSPSample Spacing Divisor
SSMSample Spacing Multiplicator
INSInstrument Type
FOCFocal Length
ASSNumber of Sample Scans
GFWNumber of Good FW Scans
GBWNumber of Good BW Scans
BFWNumber of Bad FW Scans
BBWNumber of Bad BW Scans
RSNRunning Sample Number
HFFDigital Filter HFL
LFFDigital Filter LFL
HUMHumidity Interferometer
TLPIFSSrcT
PIMPressure Interferometer
TSCScanner Temperature
SRNSlice request number???
Acquisition Parameter
AQMAcquisition Mode
SGNSignal Gain, Sample
RESResolution
OPLOptical path difference, long side [cm]
OPSOptical path difference, short side [cm]
NSSSample Scans
FT Parameters
APFApodization Function
PHRPhase Resolution
SVFSIV correction frequency
PCLPhase Corr Operator Length
PCTPhase Correction Thresh
ZFFZero Filling Factor
ZPLZPD Location
SCF
DCL
ZPA
VERVersion Number
VDCvariability in the DC level
LSTlaser sampling type [0: none; 1: InGaAs; 2: Si; 3: Dohe et al.; 4: other]
LSElaser sampling error [the shift]
LSUlaser sampling uncertainty
Optic Parameters
SRCSource Setting
APTAperture Setting
FOVField of view in mrad
BMSBeamsplitter Setting
VELScanner Velocity
DTCDetector Setting
HPFHigh Pass Filter
LPFLow Pass Filter
CHNMeasurement Channel
PGNPreamplifier Gain
RDX
SONExternal Synchronisation
Sample Parameters
SFMSample Form
LATLatitude
LONLongitude
ALTAltitude [m a.s.l.]
TOUAverage temperature [outside, °C]
POUAverage pressure [outside, hPa]
HOUAverage humidity [outside, %]
SIAAverage solar intensity
SISStandard deviation of solar intensity
WSAAverage wind speed [m/s]
WDAAverage wind direction
EXPExperiment [filename]
Data Parameters
DPFData Point Format
NPTNumber of Data Points
FXVFrequency of First Point
LXVFrequency of Last Point
CSFY - Scaling Factor
MXYY - Maximum
MNYY - Minimum
DXUX Units
DATDate of Measurement
TIMTime of Measurement