Will do, time to make some coffee...
On Wed, Dec 10, 2025 at 11:42 AM Stonie Cooper <cooper@xxxxxxxx> wrote:
> Tiffany is also looking at it from what the WFO AWIPS instance is doing.
> I think the community would like this, so please let everyone know if you
> come up with something.
> -
> Stonie Cooper, PhD
> Software Engineer III
> NSF Unidata
> cooper@xxxxxxxx
>
>
> On Wed, Dec 10, 2025 at 10:39 AM Mike Zuranski <mike@xxxxxxxxxxxxxxxxxxx>
> wrote:
>
>> Hey Stonie,
>>
>> Thanks for that info.
>>
>> I might try to hack something together later but level2 -> level3 should
>> be fairly straight forward. If I get it working would you (or anyone else
>> here) be interested in that solution?
>>
>> Best,
>> -Mike
>>
>> On Wed, Dec 10, 2025 at 9:54 AM Stonie Cooper <cooper@xxxxxxxx> wrote:
>>
>>> It is no longer being produced by NOAA at a national level, but rather
>>> at each WFO. Unidata staff are investigating if it is feasible to replicate
>>> creating L3 GLM data.
>>>
>>> -
>>> Stonie Cooper, PhD
>>> Software Engineer III
>>> NSF Unidata
>>> cooper@xxxxxxxx
>>>
>>>
>>> On Tue, Dec 9, 2025 at 2:10 PM Mike Zuranski <mike@xxxxxxxxxxxxxxxxxxx>
>>> wrote:
>>>
>>>> Hi Gilbert & Everyone,
>>>>
>>>> I see what you see (and don't see). It looks like the level2
>>>> GLMISatSS (gridded) GLM data is still flowing but not level3, see below.
>>>>
>>>> The difference between the level2 and level3 GLMISatSS data sets is
>>>> temporal aggregation; level2 is one minute while level3 is five minute .
>>>> Interesting that we lost one but not the other, especially since the five
>>>> minute set is more used. Did an IDD script die someplace? I can't recall
>>>> where/how this data is generated/fed...
>>>>
>>>> If it is just gone you have a couple options. Since we still have the
>>>> level2 data you can aggregate that yourself. You can also compile this
>>>> product yourself starting from raw GLM tiles, if you want to go that route
>>>> I'm including some references below to help you do that. TL;DR: you stitch
>>>> raw tiles together into the level2 product using glm-restitch, and then
>>>> each time you make a new one you aggregate that and the last four to make a
>>>> level3 set. And see, that's why I wonder if a script just crashed
>>>> someplace because that tiled and level2 data is still there and I thought
>>>> this was Unidata's processing flow too... but it's been a minute and I'm
>>>> probably wrong.
>>>>
>>>> Best,
>>>> -Mike
>>>>
>>>>
>>>> References:
>>>>
>>>> https://mailinglists.unidata.ucar.edu/archives/idvusers/2022/msg00007.html#gsc.tab=0
>>>>
>>>> https://www.weather.gov/media/notification/pdf_2023_24/scn22-112_goes-r_glm_gridded_data_products_aaa.pdf
>>>> https://github.com/Unidata/ldm-alchemy/blob/main/glm-restitch.py
>>>>
>>>>
>>>> $ notifyme -v -h idd.cod.edu -p GLMISatSS -o 300
>>>> 20251209T194830.514624Z notifyme[3157216] notifyme.c:main:596
>>>> NOTE Starting Up: idd.cod.edu: 20251209194330.514495
>>>> TS_ENDT {{ANY, "GLMISatSS"}}
>>>> 20251209T194830.515119Z notifyme[3157216]
>>>> inetutil.c:addrbyhost:964 INFO Resolving idd.cod.edu to
>>>> 192.203.136.196 took 0.000435 seconds
>>>> 20251209T194830.539576Z notifyme[3157216]
>>>> notifyme.c:notifyme6:432 NOTE OK
>>>> 20251209T194831.599375Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 184781 20251209194416.270800
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES18/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G18_s20253431942000_e20253431943000_c20253431942300.nc
>>>> 20251209T194831.626749Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 269354 20251209194425.008981
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES19/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G19_s20253431942000_e20253431943000_c20253431942300.nc
>>>> 20251209T194831.678468Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 172906 20251209194529.559040
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES18/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G18_s20253431943000_e20253431944000_c20253431943300.nc
>>>> 20251209T194831.678525Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 277577 20251209194542.851395
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES19/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G19_s20253431943000_e20253431944000_c20253431943300.nc
>>>> 20251209T194831.678546Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 167196 20251209194615.440857
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES18/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G18_s20253431944000_e20253431945000_c20253431944300.nc
>>>> 20251209T194831.678574Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 264742 20251209194622.883552
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES19/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G19_s20253431944000_e20253431945000_c20253431944300.nc
>>>> 20251209T194831.692097Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 180089 20251209194715.952655
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES18/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G18_s20253431945000_e20253431946000_c20253431945300.nc
>>>> 20251209T194831.692142Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 271423 20251209194724.174000
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES19/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G19_s20253431945000_e20253431946000_c20253431945300.nc
>>>> 20251209T194831.717980Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 162728 20251209194815.425465
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES18/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G18_s20253431946000_e20253431947000_c20253431946300.nc
>>>> 20251209T194831.718022Z notifyme[3157216]
>>>> notifyme.c:notifymeprog_6:276 INFO 267687 20251209194824.354332
>>>> NIMAGE 000
>>>>
>>>> /data/ldm/pub/native/satellite/GOES/GOES19/Products/GLMISatSS/Level2/FullDisk/20251209/OR_GLM-L2-GLMF-M6_G19_s20253431946000_e20253431947000_c20253431946300.nc
>>>> ^C20251209T194834.112035Z notifyme[3157216]
>>>> notifyme.c:cleanup:73 NOTE exiting
>>>>
>>>>
>>>>
>>>> On Mon, Dec 8, 2025 at 5:48 PM Sebenste, Gilbert <sebensteg@xxxxxxx>
>>>> wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> It has been over a week (possibly more due to lack of weather) where
>>>>> we are not seeing any GLM level 3 products. We ARE seeing lightning strike
>>>>> data
>>>>> just fine (level 2 data):
>>>>>
>>>>> OR_GLM-L2-LCFA_G19_s20253242246000_e20253242246200_c20253242246218.nc
>>>>>
>>>>> However, we are NOT seeing:
>>>>>
>>>>> GOES GLM Total Optical Energy
>>>>> GOES GLM Minimum Flash Area
>>>>> GOES GLM Flash Extent Density
>>>>>
>>>>> A notifyme shows no level 3 products being received on idd or iddb:
>>>>>
>>>>> localserver % notifyme -v -h idd.unidata.ucar.edu -p GLMISatSS/Level3
>>>>> -o 3600 -O
>>>>>
>>>>> 20251120T225605.667426Z notifyme[3709300]
>>>>> notifyme.c:main:592 NOTE Starting Up:
>>>>> idd.unidata.ucar.edu: 20251120215605.667336 TS_ENDT {{ANY,
>>>>> "GLMISatSS/Level3"}}
>>>>>
>>>>> 20251120T225605.668151Z notifyme[3709300]
>>>>> inetutil.c:addrbyhost:964 INFO Resolving
>>>>> idd.unidata.ucar.edu to 128.117.135.3 took 0.000633 seconds
>>>>>
>>>>> 20251120T225605.696393Z notifyme[3709300]
>>>>> notifyme.c:notifyme6:428 NOTE OK
>>>>>
>>>>> 20251120T225635.793049Z notifyme[3709300]
>>>>> notifyme.c:sendNotifyMe:346 ERROR NOTIFYME reclassified: "" -> ""
>>>>>
>>>>> 20251120T225635.793089Z notifyme[3709300]
>>>>> notifyme.c:executeService:396 ERROR Connection to upstream LDM
>>>>> timed-out
>>>>>
>>>>>
>>>>> Is anyone seeing this missing data?
>>>>>
>>>>> Thank you for any help!
>>>>>
>>>>> Gilbert Sebenste
>>>>>
>>>>> Meteorology Support Analyst
>>>>>
>>>>> [image: image001.png]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _________________________________________________________
>>>>> NOTE: All exchanges posted to NSF Unidata maintained email lists are
>>>>> made publicly available through the web. Users who post to any of the
>>>>> lists we maintain are reminded to remove any personal information that
>>>>> they do not want to be made public.
>>>>>
>>>>> NSF Unidata ldm-users Mailing List
>>>>> (ldm-users@xxxxxxxxxxxxxxxx)
>>>>> For list information, to unsubscribe, or change your membership
>>>>> options,
>>>>> visit: https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/
>>>>>
>>>> _________________________________________________________
>>>> NOTE: All exchanges posted to NSF Unidata maintained email lists are
>>>> made publicly available through the web. Users who post to any of the
>>>> lists we maintain are reminded to remove any personal information that
>>>> they do not want to be made public.
>>>>
>>>> NSF Unidata ldm-users Mailing List
>>>> (ldm-users@xxxxxxxxxxxxxxxx)
>>>> For list information, to unsubscribe, or change your membership options,
>>>> visit: https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/
>>>>
>>> _________________________________________________________
>>> NOTE: All exchanges posted to NSF Unidata maintained email lists are
>>> made publicly available through the web. Users who post to any of the
>>> lists we maintain are reminded to remove any personal information that
>>> they do not want to be made public.
>>>
>>> NSF Unidata ldm-users Mailing List
>>> (ldm-users@xxxxxxxxxxxxxxxx)
>>> For list information, to unsubscribe, or change your membership options,
>>> visit: https://mailinglists.unidata.ucar.edu/listinfo/ldm-users/
>>>
>>
