SSEC forums

Posted: **Tue Oct 01, 2013 3:59 pm**

Hi,

I am running Tk Chain runner in command line mode. However, it seems that some granules were failed because of missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile".The fact is that all "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile" tiles already included in the "INFTK_DM_ROOT" variable. Sometimes, if I ran the same granule for several times, it will go through. I started to have this problem since Mx7.1 build.
Thanks,

/data/data020/weizhong/ADL4.1/CSPP/ADL4.2/log/ProSdrViirsController_20131001_185328_7258.log:
2013/10/01 18:56:49.015.135 (7258.47944276903200): DBG_HIGH ProCmnAlgorithm.cpp|7917|Error retrieving data for GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile

Posted: **Wed Oct 02, 2013 9:19 am**

You log file points to an issue with the following tile id:

2013/10/01 18:56:49.016.581 (7258.47944276903200): DBG_HIGH ProCmnMessage.cpp|191|Status: INF_STATUSTYPE_GIP_PREREQ_ABSENT | ShortName: GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile | Description: Required input not available for Shortname: GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile , Tile ID: 4492 Failure(s): (GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile, )

However, since debug was set to HIGH, there isn't a great deal of information in the log file to help pinpoint the issue. I would ensure that you do have this tile in your file system and INFTK_DM_ROOT path variable.

I assume this granule will fail every time, if so can you set debug to LOW as it will provide more information on the failure hopefully. Are you running the parallel option for the chain runner?

If you can post the asc file for tile id 4492 that may also be helpful in understanding the problem.

Thanks,

Bryan Henderson
Raytheon Company

Posted: **Wed Oct 02, 2013 3:30 pm**

Hi Bryan,

I ran it again with debug LOW. Please found the log file in the attachment. Also, I got a new error beside the old "SNOW ICE ROLLING TILE" one. The chain run still failed and it show the following message on my screen.

I did see this "Dataset Lock: 1" error since the new Mx7.1 built which I think it was caused by the "envSetup.pm" perl module which I converted from the "envSetup.ksh" file line by line. I started to use my "envSetup.pm" perl module since Mx6.6. It never had any problem until Mx7.1. I can not find the reason why it cause the problem. Now, I have to source the "envSetup.ksh" file in the shell. Anyway, I already disable this perl module in my script when I did this chain run.

Thanks,

Delta Algorithm Chain Run Started...
Running Algorithms With 2 Threads.

Algorithm Chain Queue:
ProSdrViirsController:NPP000573773056:Not Yet Built

Creating ProSdrViirsController.exe TK file for granule ID NPP000573773056
/data/data020/weizhong/ADL4.1/CSPP/ADL4.2/log/ProSdrViirsController_NPP000573773056.xml
Running ProSdrViirsController.exe for granule ID NPP000573773056
/data/data020/weizhong/ADL4.1/CSPP/ADL4.2/bin/ProSdrViirsController.exe
Algorithm Run Failure - ProSdrViirsController, NPP000573773056 Failed During Execution!
Algorithm Run Failure - ProSdrViirsController, NPP000573773056 Failed to Produce an Output Product!
Algorithm Run Failure - ProSdrViirsController, NPP000573773056 Algorithm Stopped Early or Core Dumped!

-----------------Failure Details Start---------------------
Output Product: VIIRS-ANC-Dig-Bath-Data-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Geopot-Ht-Press-Lev-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Nitr-Depl-Temp-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Tot-Col-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Preci-Wtr-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Temp-Skin-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Sp-Humd-Surf-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Geopot-Ht-Lev-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Press-Surf-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Temp-Surf2M-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Surf-Ht-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Tropo-Geopot-Ht-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Wind-Direction-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-ANC-Wind-Speed-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-VIIRS-Ann-Max-Min-Ndvi-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-VIIRS-Nbar-Ndvi-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-VIIRS-Qst-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-VIIRS-Qst-Lwm-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-VIIRS-Snow-Ice-Cover-Mod-Gran
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-GridIP-NN-Img-IP
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-Grid-To-Gran-GridIP-AW-SWATH-Mod-IP
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-Gran-To-Grid-GridIP-AW-GRID-Mod-IP
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M1-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M1-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M2-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M2-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M3-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M3-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M4-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M4-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M5-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M5-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M6-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M6-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M7-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M7-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M8-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M8-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M9-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M9-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M10-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M10-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M11-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M11-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M12-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M12-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M13-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M14-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M14-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M15-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M15-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M16-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-M16-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I1-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I1-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I2-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I2-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I3-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I3-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I4-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I4-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I5-FSDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-I5-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-DNB-SDR
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-DualGain-Cal-IP
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-OBC-IP
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-IMG-RGEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-RGEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-IMG-RGEO-TC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-RGEO-TC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-DNB-GEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-IMG-GEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-GEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-UNAGG-GEO
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-IMG-GEO-TC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-GEO-TC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-GRC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-MOD-GRC-TC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-IMG-GRC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

Output Product: VIIRS-DNB-GRC
Product Creation Date Time: 2013-10-01 17:36:23.533000
Dataset Lock: 1

-----------------Failure Details End---------------------
Error: An Algorithm in the Chain has Failed to Complete Successfully!
Chain Run did not Completed Successfully!
VIIRS-SDR is done!

Posted: **Wed Oct 02, 2013 4:42 pm**

I took a look at your log file and it seems to be tile 4565 that has issues this time. It is URID 50c21318-126ef-9b9dea82-ec60c729.

The root of the problem is near line 202788:

Code: Select all

2013/10/02 19:01:47.093.321 (21595.47754486797600): DBG_HIGH ProCmnMethodAudit.cpp|207|ProCmnDataItem[14ProCmnTileItem]::setDataVectorExisting(GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile) [0x5fa0800] ROOT PRO_FAIL disk file missing and we can't be a shell granule ( your inventory may be corrupted) from file ProCmnDataItem.cpp, line 2677

That message usually indicates that a binary file is not in the same directory as its .asc file. In ADL, a .asc file and its corresponding binary file *must* be in the same directory.

There are several questions that may provide clues:
--Do you have the patch applied for ADL 4.2 with Mx7.2? This was released a bit over a month ago.
--Are you running any other ADL processes that could be modifying the tile data?
--Does the path /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin exist on your system.
--Could you run this command to find all .asc or .jasc files referencing 50c21318-126ef-9b9dea82-ec60c729

Code: Select all

$> find /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-17 /data/data020/pub/NPP_DATA/LUTs/AllLuts_20130612_2213_Mx72 /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata /data/data048/pub/weizhong/temp/run_test_viirs/data/input/withMetadata/ProSdrViirsControllerInputs/20130817-test/d20130817_t0208246_e0209500_b09345/run_set /data/data048/pub/weizhong/temp/run_test_viirs/data/output/withMetadata/ProSdrViirsControllerOutputs/20130817-test/d20130817_t0208246_e0209500_b09345 -name \*.asc -o -name \*.jasc | xargs grep 50c21318-126ef-9b9dea82-ec60c729

--Could you run this command to find all binary files for 50c21318-126ef-9b9dea82-ec60c729.

Code: Select all

$> find /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-17 /data/data020/pub/NPP_DATA/LUTs/AllLuts_20130612_2213_Mx72 /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata /data/data048/pub/weizhong/temp/run_test_viirs/data/input/withMetadata/ProSdrViirsControllerInputs/20130817-test/d20130817_t0208246_e0209500_b09345/run_set /data/data048/pub/weizhong/temp/run_test_viirs/data/output/withMetadata/ProSdrViirsControllerOutputs/20130817-test/d20130817_t0208246_e0209500_b09345 -name 50c21318-126ef-9b9dea82-ec60c729.\*

Posted: **Thu Oct 03, 2013 10:35 am**

The following is the result. I already have snow ice in the "/data/data020/pub/NPP_DATA/LUTs/AllLuts_20130612_2213_Mx72 /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all" folder. However, since ADL complained missing snowice tiles sometimes. So I included an extra snowice tiles "/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata" too. Could the duplicate snowice tiles cause problems?

There are several questions that may provide clues:
--Do you have the patch applied for ADL 4.2 with Mx7.2? This was released a bit over a month ago.
Yes, I applied all required patches. And did some successful run.

--Are you running any other ADL processes that could be modifying the tile data?
It is a shared folder. But no one should modify any tiles file.

--Does the path /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin exist on your system.
It is wired. The file name is still in the *.jasc file which I created long time ago. It seems that it has disappeared now. Maybe it didn't totally recover from our last power outage.

I will try it again with new Tiles.

[10:23 weizhong@rhw3022 MX6.7]$ find /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-17 /data/data020/pub/NPP_DATA/LUTs/AllLuts_20130612_2213_Mx72 /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata /data/data048/pub/weizhong/temp/run_test_viirs/data/input/withMetadata/ProSdrViirsControllerInputs/20130817-test/d20130817_t0208246_e0209500_b09345/run_set /data/data048/pub/weizhong/temp/run_test_viirs/data/output/withMetadata/ProSdrViirsControllerOutputs/20130817-test/d20130817_t0208246_e0209500_b09345 -name \*.asc -o -name \*.jasc | xargs grep 50c21318-126ef-9b9dea82-ec60c729

/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/with-meta-all.jasc:)("50c21318-126ef-9b9dea82-ec60c729" UR "2012-12-07 16:02:32.000000"
/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/with-meta-all.jasc: ("/npd/adelotel/myDmsPath/ids/DMSI1.5_NIGHTLY_MX7_SHAREDPRO_CSI/data//DmSm//GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile/07_16/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin" FILE

/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.asc:("50c21318-126ef-9b9dea82-ec60c729" UR "2012-12-07 16:02:32.000000"
/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.asc: ("/npd/adelotel/myDmsPath/ids/DMSI1.5_NIGHTLY_MX7_SHAREDPRO_CSI/data//DmSm//GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile/07_16/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin" FILE

[10:36 weizhong@rhw3022 MX6.7]$ find /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NCEP/2013-08-17 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-16 /data/data020/weizhong/run_ADL/data/input/withMetadata/IngMsdOutputs-NAAPS/2013-08-17 /data/data020/pub/NPP_DATA/LUTs/AllLuts_20130612_2213_Mx72 /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata /data/data048/pub/weizhong/temp/run_test_viirs/data/input/withMetadata/ProSdrViirsControllerInputs/20130817-test/d20130817_t0208246_e0209500_b09345/run_set /data/data048/pub/weizhong/temp/run_test_viirs/data/output/withMetadata/ProSdrViirsControllerOutputs/20130817-test/d20130817_t0208246_e0209500_b09345 -name 50c21318-126ef-9b9dea82-ec60c729.\*

/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin
/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.asc

Posted: **Thu Oct 03, 2013 6:02 pm**

The problem URID is referenced in 2 files:
/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/with-meta-all.jasc
/data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.asc

As stated previously, the binary file must exist in the same directory as the .jasc or .asc files. The order that files are restored in can change a little because the restoration process uses multiple OpenMP threads to restore files. In the case of the log file you posted, the .jasc was restored first and the binary file was assumed to be in /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/. That is why it says

Code: Select all

2013/10/02 19:01:47.093.262 (21595.47754486797600): DBG_LOW DmCoreFileTools.cpp|267| tid-47754486797600 isFile() /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/with-meta-all/50c21318-126ef-9b9dea82-ec60c729.GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_20121115000000Z_ee000000000000000_CONST-NPP_VIIRS_4565_STAR-GMSI123200901-474-12-0726.bin not a file: path not found

around line 202786 in your log file.

When /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata/50c21318-126ef-9b9dea82-ec60c729.asc was restored sometime after the .jasc file, it was determined that URID 50c21318-126ef-9b9dea82-ec60c729 already existed in inventory. However, the metadata was identical, so no error was thrown. A warning was generated at 2340 saying "...Warning: The UR 50c21318-126ef-9b9dea82-ec60c729 already exists in inventory but is identical to the existing copy. This UR was not added."

As for how to fix your issue, your input directory is in a bad state because it has metadata (in the .jasc file), but no binary file in that same directory. So you need to recreate your .jasc file to only contain metadata for instances where you also have a binary file on disk.

If with-meta-all.jasc contains only SnowIce tiles it appears you could use $ADL_HOME/script/createJascFiles.sh to create a .jasc based on /data/data020/pub/NPP_DATA/TILES/NovGroundCCR692Tiles/GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile_Nov_2012/withMetadata.

If with-meta-all.jasc contains more than SnowIce tiles, you'll need to recreate it some other way.

FYI, while the presence of a .jasc causes .asc files to be ignored in a directory, it is acceptable to have multiple .jasc files in the same directory. So you could have snowIce.jasc and qstLwm.jasc in the same directory for example.

Posted: **Mon Oct 07, 2013 11:16 am**

Hi Kevin,

Thanks for your help. That's exactly where the problem is. Now, everything is working fine.

SSEC forums

missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"

Re: missing "GridIP-VIIRS-Snow-Ice-Cover-Rolling-Tile"