PRO_CROSSGRAN_FAIL Required input not available

Issues related to the CrIS SDR algorithm and data

PRO_CROSSGRAN_FAIL Required input not available

Postby benesplin » Fri May 17, 2013 5:00 pm

I have not been able to run any CrIS data through the latest version of ADL compiled from source. Every time I run it it gives a required input not available error, no matter what inputs I add from ADL/data or which granules I run.

ProSdrCrisController failed to get cross granule inputs
ProCmnAlgorithm[ProSdrCris]::handleInputQuery(NPP000494865921) [0x2af922211010] ROOT PRO_CROSSGRAN_FAIL Required input not available for Shortname: CRIS-SCIENCE-RDR , Granule ID: NPP000494864962 Failure(s): (CRIS-SCIENCE-RDR, NPP000494864962) from file ProCmnAlgorithm.cpp, line 7895

Granule ID NPP000494864962 is not in the xml files and is not a granule I am trying to process.



Has the algorithm changed so that 22 four scanline RDR granules are no longer enough to process SDRs?
Here is a cleaned up list of the inputs I included in CRIS_INPUTPATH. See the attachment for the complete list.

off_Planet-Eph-ANC_Static_JPL_000f_20000101_200001010000Z_20000101000000Z_ee00000000000000Z_np.dat

off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20120420_201204201200Z_20120420001002Z_ee20120427120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20120112_201201121200Z_20120112120036Z_ee20120119120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20111110_201111101200Z_20111110120018Z_ee20111117120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20111229_201112291200Z_20111229120015Z_ee20120105120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20121102_201211020000Z_20121102000003Z_ee20121109120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20130111_201301110000Z_20130111000003Z_ee20130118120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20111222_201112221200Z_20111222120018Z_ee20111229120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20130118_201301180000Z_20130118000002Z_ee20130125120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20111215_201112151200Z_20111215120015Z_ee20111222120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20120105_201201051200Z_20120105120515Z_ee20120112120000Z_np.bin_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20030124_200301241200Z_20030124000000Z_ee20100101120000Z_np.dat_Internal
off_USNO-PolarWander-UT1-ANC_Ser7_USNO_000f_20111117_201111171200Z_20111117120153Z_ee20111124120000Z_np.bin_Internal

CrIS-SDR-CC-Int
CrIS-SDR-FILL-PACKET-LUT_npp_20020101010000Z_20020101010000Z_ee00000000000000Z_PS-1-D-NPP-1-PE-_devl_dev_all-_all.bin

CMNGEO-PARAM-LUT_npp_20020101010000Z_20020101010000Z_ee00000000000000Z_PS-1-D-NPP-1-PE-_devl_dev_all-_all.bin
CMNGEO-PARAM-LUT_npp_20111101010000Z_20111101010000Z_ee00000000000000Z_PS-1-N-CCR-11-216-NGAS-002-PE-_noaa_all_all-_all.bin
CrIS-SDR-DQTT_npp_20020101010000Z_20020101010000Z_ee00000000000000Z_BASELINE-MON-1_devl_dev_noaa_ops.xml_Internal
CmnGeo-SAA-AC_npp_20020101010000Z_20020101010000Z_ee00000000000000Z_1_devl_dev_noaa_ops.xml_Internal

TLE-AUX_npp_20130510141618Z_20130511000000Z_ee00000000000000Z_-_c3s-_ops_all-_ops.txt_Internal

Am I missing any files?
Attachments
ProSdrCrisController.exe_20130517_160335_11807.log
Error log
(604.77 KiB) Downloaded 202 times
rawInputs.txt
Raw list of all input files in CRIS_INPUTPATH
(257.49 KiB) Downloaded 217 times
benesplin
 
Posts: 2
Joined: Thu Dec 06, 2012 12:24 pm

Re: PRO_CROSSGRAN_FAIL Required input not available

Postby bhenders » Mon May 20, 2013 1:09 pm

Can you clarify what the latest version of ADL compiled from source is? I assume that you are referring to possibly one of the data and source tar file packages provided from the CM portal.

Nonetheless, your problem seems directly related to not having the correct cross granule CrIS-SCIENCE-RDR files available or you are using the incorrect NPP_GRANULE_ID_BASETIME for the CrIS RDRs that you are trying to run. You should need 4 previous and 4 future granules in order to run one CrIS RDR granule. At a minimum you need 9 granules total to produce one granule of output. I've pasted the comments from the $ADL_HOME/build/envSetup.ksh file regarding the NPP_GRANULE_ID_BASETIME below. This would be the first thing I would check with regards to your failure. Second, I'd verify that you do indeed have at least 9 granules staged consecutively. If you are still having issues, please post the granule ID of the granule you are trying to execute and the granule ids that you do have staged and I will help debug further.

# The value of NPP_GRANULE_ID_BASETIME affects the granule ID utility which
# affects the granule IDs for which an algorithm will query.
#
# It is set correctly for data that ships with ADL and prelaunch proxy data.
# If real NPP data is processed by ADL, this variable will need to be
# updated.
#
# Use this value for data shipped with ADL and prelaunch proxy data.
export NPP_GRANULE_ID_BASETIME=1300968033000000
#
# Use this value for real NPP data.
#export NPP_GRANULE_ID_BASETIME=1698019234000000

Bryan Henderson
Raytheon Company
bhenders
 
Posts: 72
Joined: Wed Jan 05, 2011 9:27 am
Location: Omaha, NE

Re: PRO_CROSSGRAN_FAIL Required input not available

Postby benesplin » Tue May 21, 2013 2:53 pm

Thank you, from your post I was able to diagnose what our problem was. The script we are using to generate the XML files was not staging correctly.

I have another question. What triggers ADL to create a Correction Matrix?
My guess is that it creates a new correction matrix for the first granule run and then for every granule that contains a four minute engineering packet. Is this a correct assumption?
benesplin
 
Posts: 2
Joined: Thu Dec 06, 2012 12:24 pm

Re: PRO_CROSSGRAN_FAIL Required input not available

Postby bhenders » Wed May 22, 2013 10:54 am

The conditions that trigger a CMO rebuild I believe are described in CrIS SDR ATBD document. The CMO is not rebuilt for every 4 minute engineering packet that is received but rather will only be triggered if the monitored laser wavelength has drifted beyond a threshold. It's been quite awhile since I've been involved in CrIS but there may be the possibility that an 8 second science data packet could trigger the CMO to be rebuilt. A new CMO is always generated if one does not exist or is available as an input. The ScienceDataProcessor::refreshCorrectionMatrix() calls, I believe are all the trigger points for rebuilding the CMO.

Bryan Henderson
Raytheon Company
bhenders
 
Posts: 72
Joined: Wed Jan 05, 2011 9:27 am
Location: Omaha, NE


Return to CrIS SDR

Who is online

Users browsing this forum: No registered users and 1 guest