From cbe0a92b9323e55c57ea65541cd8bf6ff0712f53 Mon Sep 17 00:00:00 2001
From: nickb <nickb@ssec.wisc.edu>
Date: Tue, 23 Feb 2021 16:49:12 +0000
Subject: [PATCH] attempted fix for the 20s end times issue. we might need to
revisit and be more explicit in order to handle bad input as well.
---
gridded_glm/libexec/_minute_gridder.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gridded_glm/libexec/_minute_gridder.py b/gridded_glm/libexec/_minute_gridder.py
index c24cb71..16b997c 100644
--- a/gridded_glm/libexec/_minute_gridder.py
+++ b/gridded_glm/libexec/_minute_gridder.py
@@ -158,7 +158,9 @@ def get_outpath_base(args):
start_time, end_time: datetimes that can be used with strftime syntax, e.g.
'./{start_time:%y/%b/%d}/GLM_{start_time:%Y%m%d_%H%M%S}.nc'
"""
- ops_environment, algorithm, platform, start_time, end_time, created_time = parse_glm_filename(os.path.basename(args.filenames[0]))
+ ordered_filenames = sorted(args.filenames)
+ _, _, platform, start_time, _, _ = parse_glm_filename(os.path.basename(ordered_filenames[0]))
+ _, _, _, _, end_time, _ = parse_glm_filename(os.path.basename(ordered_filenames[-1]))
sector_short = get_sector_shortstring(args)
mode = "M3" # FIXME: is GLM always in M3?
--
GitLab