Page 2 of 3
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Fri Jul 24, 2015 10:50 am
by kbisanz
This issue has been solved. The breakthrough came when someone noticed that a BeginningOrbitNumber metadata was 0. So the issue was metadata on inputs.
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Tue Aug 11, 2015 11:22 am
by wzchen
Hi Kevin,
Thanks for your help. We finally got a new dataset with the valid orbit number. However, I have another problem now. It seems that the RSBAutoCal can not run in extension granule mode. Is anyway to fix it?
Also, there is no "VIIRS-RSBAUTOCAL-HISTORY-AUX" H5 file generated after run, only binary file like "55ca1291-a3394-020ab506-6c4011eb.VIIRS-RSBAUTOCAL-HISTORY-AUX_j01_20150811151945Z_20120121000000Z_ee00000000000000Z_-_null_dev_all-_dev.bin".
Thanks,
Weizhong
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Tue Aug 11, 2015 1:13 pm
by kbisanz
You can switch to cross granule mode by changing the value of "EXTENDED_GRANULES" from true to false in $ADL_HOME/cfg/ADL_CFG.xml. This "cross granule" mode was the only way of running in Block 1.2. There is no need to recompile. It should be picked up at runtime.
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Tue Aug 11, 2015 1:19 pm
by kbisanz
Oops, I missed the second half of your question. It should have written an H5 file to $HDF_OUTPUT_PATH/ProSdrViirsRSBAutoCalOutputs/. If it did not, see if there are any errors in the debug log. If you don't see any errors, ensure DBG_LOW is enabled and then upload the log file and we can take a look.
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Wed Aug 12, 2015 10:19 am
by wzchen
Hi Kevin,
I will try your suggestion later.
Now, I have trouble to locate which LUT may caused the problem when I try to run RSBAutoCal by using updated LUTs. Please check the log file in the attachment.
Thanks,
Weizhong
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Wed Aug 12, 2015 2:03 pm
by wzchen
Hi Kevin,
I try to rerun it with debug LOW to see why the ADL5 can not generate HDF5 file. However, after 1hour and 20min, it seems that it is still running. It keeps writing the following sentences in the log file for about 20min already. Is it normal? or it is in dead loop?
Code: Select all
32746 2015-08-12 19:00:18.185000Z DBG_LOW InfInfo_MessageFactory.cpp(157)[ProSdrViirsRSBA (47175775692544)]: "created" InfInfo_StatusMessageImpl from queue with address 0x1dddb80
32747 2015-08-12 19:00:18.186000Z DBG_LOW InfWfm_LwMessageAsciiFileWriter.cpp(138)[ProSdrViirsRSBA (47175775692544)]: write
32748 2015-08-12 19:00:18.186000Z DBG_LOW InfInfo_MessageFactory.cpp(102)[ProSdrViirsRSBA (47175775692544)]: released InfInfo_StatusMessageImpl back to the queue with address 0x1dddb80
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Thu Aug 13, 2015 11:54 am
by wzchen
I can run it when debug is set to MED, nut not LOW.
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Thu Aug 13, 2015 11:57 am
by kbisanz
When increasing the debug level, it's normal for a process to slow down slightly because it's writing more lines to the debug file. However, it should not slow down by nearly that much. A 10-20% is normal. An infinite loop is not. It's pretty strange that debug med works but low does not.
It sounds like there is some issue if it keeps writing the same series of lines. I'll take a look at the log file you posted.
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Thu Aug 13, 2015 2:15 pm
by wzchen
Log file with debug LOW
Re: missing VIIRS-RSBAUTOCAL-OBCIP-HISTORY-AUX
Posted: Thu Aug 13, 2015 5:02 pm
by kbisanz
In the debug MED file, the HDF packing "looks" successfully, but runs very quickly (probably too quickly). The debug LOW file hits the message loop issue before getting to HDF packing. So let's try packing the HDF file manually and maybe we can see the error.
1) Ensure that DBG_LOW is enabled for the packer by checking $ADL_HOME/cfg/packer.xml
2) Run $ADL_HOME/tools/bin/ADL_Packer.exe URID OUTPUT_DIR. For example: ./ADL_Packer.exe 55ca1291-a3394-020ab506-6c4011eb /home/your_name/
The URID is that alphanumeric number that's at the start of the binary file name for example: "55ca1291-a3394-020ab506-6c4011eb.VIIRS-RSBAUTOCAL-HISTORY-AUX_j01_20150811151945Z_20120121000000Z_ee00000000000000Z_-_null_dev_all-_dev.bin".
That should create a log file in the log directory. Please post that log file.