SSEC forums

Hello,

I am having a difficult time running the CrIS SDR algorithm on the ADL V3.1 Virtual Appliance. The issue has been identified from the log files as shown below:

2012/02/16 22:10:07.099.332 (32546.47003767665408): DBG_MED CorrectionMatrix.cpp|719|resetting size of the matrix
2012/02/16 22:10:07.100.112 (32546.47003767665408): DBG_HIGH EventLogEngine.cpp|133|NOTE: Declared window size of (EarthScene 15) with (Reference 30)
2012/02/16 22:10:07.100.260 (32546.47003767665408): DBG_MED CrIS_SDR.cpp|263|ProSdrCris - crisMain() packet unpacking beginning
2012/02/16 22:10:07.100.308 (32546.47003767665408): DBG_HIGH InfTk_CppApi.cpp|272|updateHealth|Description=Load Correction Matrix Started
2012/02/16 22:10:07.100.330 (32546.47003767665408): DBG_LOW InfTk_ServiceModule.cpp|665|updateHealth
2012/02/16 22:10:07.209.565 (32546.47003767665408): DBG_HIGH EventLogEngine.cpp|133|NOTE: Engineering packet load started
2012/02/16 22:10:07.210.277 (32546.47003767665408): DBG_HIGH ProSdrCris.cpp|916|caught standard EXCEPTION class version 33EngCalRec_ICTEmissivityParameters
2012/02/16 22:10:07.210.323 (32546.47003767665408): DBG_HIGH ProCmnMethodAudit.cpp|206|ProSdrCris[ProSdrCris]::doProcessing(NPP001212025561) [0x2abfeb81b010] ROOT PRO_FAIL Science Algorithm: crisMain() call from file ProSdrCris.cpp, line 931
2012/02/16 22:10:07.210.391 (32546.47003767665408): DBG_LOW ProCmnAbstractItem.cpp|480|19ProCmnSDROutputItem is not a shell item (data size 17102928)
2012/02/16 22:10:07.210.414 (32546.47003767665408): DBG_LOW ProCmnDataItem.cpp|3920|INFSTATUS infStatusData: 19ProCmnSDROutputItem INF_STATUSTYPE_SDR_FAIL CrIS-SDR ( SDR--CrIS-SDR ) ProSdrCris
2012/02/16 22:10:07.210.435 (32546.47003767665408): DBG_HIGH ProCmnMessage.cpp|191|Status: INF_STATUSTYPE_SDR_FAIL | ShortName: CrIS-SDR | Description: SDR--CrIS-SDR
2012/02/16 22:10:07.210.459 (32546.47003767665408): DBG_LOW ProCmnDataItem.cpp|3920|INFSTATUS infStatusData: 19ProCmnAUXOutputItem INF_STATUSTYPE_AUX_FAIL CrIS-Correct-Matrix-AUX ( AUX--CrIS-Correct-Matrix-AUX ) ProSdrCris
2012/02/16 22:10:07.210.477 (32546.47003767665408): DBG_HIGH ProCmnMessage.cpp|191|Status: INF_STATUSTYPE_AUX_FAIL | ShortName: CrIS-Correct-Matrix-AUX | Description: AUX--CrIS-Correct-Matrix-AUX
2012/02/16 22:10:07.210.497 (32546.47003767665408): DBG_LOW ProCmnOutputItem.cpp|2452|NO FAIL GRAN message for 19ProCmnDQNOutputItem implemented
2012/02/16 22:10:07.210.517 (32546.47003767665408): DBG_LOW ProCmnAbstractItem.cpp|480|19ProCmnIPROutputItem is not a shell item (data size 25920)
2012/02/16 22:10:07.210.536 (32546.47003767665408): DBG_LOW ProCmnOutputItem.cpp|2477|skipping FAIL XDR message for 19ProCmnIPROutputItem (not allowed for heap items)
2012/02/16 22:10:07.210.555 (32546.47003767665408): DBG_LOW ProCmnOutputItem.cpp|2452|NO FAIL GRAN message for 19ProCmnGEOOutputItem implemented
2012/02/16 22:10:07.210.573 (32546.47003767665408): DBG_LOW ProCmnOutputItem.cpp|2452|NO FAIL GRAN message for 19ProCmnGEOOutputItem implemented

Does anyone know the reason for the standard exception class version 33EngCalRec_ICTEmissivityParameters?

I have installed the Boost Library version 1.42.0, and rebuilt ADL, but this has not solved the problem. I hope more experienced CrIS users may have seen this and can help point me towards a solution. Thank you.

Idahosa

The error seems to be occurring during the retrieval of the CrIS Correction Matrix input, specifically loading the data back into the respective object containers.

ADL was not dropped with a CrIS correction matrix input, rather it is an optional input item and one is created on the fly for the data that was staged.

We already know that there seems to be some sort of problem with the BOOST versions with the serialization library being used. Raytheon tested with BOOST version 1.39 which is the version currently approved by IDPS sustainment. I'm not sure if 1.42 has an issue or not, but I see that it is the version that UW has put on the ADL download site.

Lastly, is the ByteOrder metadata set correctly for the binary that you have staged. It may be a big endian binary versus running on a little endian platform.

In order to help further, we'll probably need some more information, such as where the correction matrix input you are using came from and maybe the platform and metadata ASCII file for it. You might want to just remove this input and see if CrIS SDR executes without it and creates one during execution successfully. It should write out a new one. Can the new correction matrix that is written out then be used?

Bryan Henderson
Raytheon Company

Thanks a lot Bryan. Your suggestion to remove the CrIS-Correct-Matrix worked! The algorithm ran successfully and a new CrIS-Correct_Matrix was generated. I am about to analyze the outputs to make sure it is as expected. Thanks.


Idahosa Osaretin
MIT Lincoln Laboratory

Idahosa,

You will probably want to coordinate with Dan Mooney of your laboratory for patches in test currently by the CrIS SDR Cal-Val team.

Mark