Debugging CSPP Active Fire Errors

VIIRS Sensor Data Record
Post Reply
eapau
Posts: 1
Joined: Thu Aug 12, 2021 8:34 am

Debugging CSPP Active Fire Errors

Post by eapau »

I'm currently using VIRS-L1 data created via IPOPP and attempting to process it to L2 active fire .nc files via the CSPP active fire library.

The current log isn't helpful in determining what the issue is. i've confirmed by L1 data is not corrupted because i can process them into VIRS-AF L2 .tifs via IPOPP
Any help pointing me to the right place to debug this would be helpful

Code: Select all

################################################################################
#                    Community Satellite Processing Package                    #
#                              VIIRS Active Fires                              #
#                                                                              #
#                       CSPP Active Fires: Version 1.1.1                       #
#            I-band: Version 2.5.4, compiled Dec 27 2020 06:55:55.             #
#                Current date: 2021-08-10 13:16:25.803666+00:00                #
################################################################################

Using cache dir /root/cspp-active-fire-noaa_1.1.1/bin/cspp_active_fire_cache_dir

>>> Preparing inputs

Submitting 9 nagg tasks to the pool...
Processing aggregated file /root/fire_test_data/s3/GITCO_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for GITCO_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.645319 seconds
Processing aggregated file /root/fire_test_data/s3/GMTCO_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for GMTCO_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.594256 seconds
Processing aggregated file /root/fire_test_data/s3/IVCDB_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for IVCDB_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.619025 seconds
Processing aggregated file /root/fire_test_data/s3/SVI01_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVI01_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.620487 seconds
Processing aggregated file /root/fire_test_data/s3/SVI02_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVI02_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.637295 seconds
Processing aggregated file /root/fire_test_data/s3/SVI03_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVI03_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.623554 seconds
Processing aggregated file /root/fire_test_data/s3/SVI04_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVI04_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.621023 seconds
Processing aggregated file /root/fire_test_data/s3/SVI05_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVI05_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.623075 seconds
Processing aggregated file /root/fire_test_data/s3/SVM13_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5...
	nagg execution for SVM13_j01_d20210719_t1810520_e1815570_b00000_c20210719184319188000_ipop_dev.h5 took 0 days, 0 hours, 0 minutes, 0.621038 seconds
Unaggregation took 0 days, 0 hours, 0 minutes, 5.707108 seconds
>>> No valid I-band inputs detected, aborting.
attempted_runs    []
successful_runs   []
problem_runs      []
crashed_runs      []
kathys
Posts: 484
Joined: Tue Jun 22, 2010 4:51 pm

Re: Debugging CSPP Active Fire Errors

Post by kathys »

Dear Colleague,

Can you please run the code again using a higher verbosity "-vvv" and post the main log file here (prefixed with cspp_active_fire_noaa.)?

Thank you,

Kathy
Post Reply