k2ew_tcp: Anybody remember this module?

17 views
Skip to first unread message

Meremonte, Mark E

unread,
Jan 23, 2023, 7:32:56 PM1/23/23
to earthwo...@googlegroups.com
Dear Earthworm forum,

Sorry to bring this module back into the light of day but moving to EW_7.11 on Red Hat Enterprise 8.   

Even though all related modules setup the same as for 7.10 on CentOS-7, am receiving this message:
        Error fetching logo values for TYPE_SNW messages: k2ew_tcp_lan_FRNT.d
Any ideas?   Do not know where the "TYPE_SNW" logo is coming from.   Log type not found in 7.10 log files for this module.

All individual K2 modules using "ring" named K2_RING in combination with the condenselogo module to manage buffering where it is setup as:
MyModuleId    MOD_K2ALL      # module id for this instance of condenselogo
InRing               K2_RING          # shared memory ring for input
OutRing         RAW_RING         # shared memory ring for output

Thank you & Regards, Mark

***************************************************************
Mark Meremonte    Geophysicist  
Seismology & Geomorphology Group
US Bureau of Reclamation   http://www.usbr.gov
Technical Services Center, Seismology & Geomorphology Group
Denver Federal Center,  PO Box 25007, 85-833000, Denver, CO  80225                  
Ship:  US Bureau of Reclamation, DFC, Bldg. 67-10th Floor, Denver, CO 80225
***************************************************************

Dietz, Lynn D

unread,
Jan 23, 2023, 7:41:43 PM1/23/23
to earthwo...@googlegroups.com
I think you just need to define TYPE_SNW as a message type in your earthworm.d file.  This is a message that would go to SeisNetWatch.  



From: 'Meremonte, Mark E' via Earthworm Community Forum <earthwo...@googlegroups.com>
Sent: Monday, January 23, 2023 4:32 PM
To: earthwo...@googlegroups.com <earthwo...@googlegroups.com>
Subject: [EXTERNAL] [Earthworm Forum] k2ew_tcp: Anybody remember this module?
 

 

 This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.  



--
--
You received this message because you are subscribed to the Google
Groups "Earthworm Community Forum" group.
 
To post to this group, send an email to earthwo...@googlegroups.com
 
To unsubscribe from this group, send an email to
earthworm_for...@googlegroups.com
 
For more options, visit this group at
http://groups.google.com/group/earthworm_forum?hl=en

---
You received this message because you are subscribed to the Google Groups "Earthworm Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to earthworm_for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/earthworm_forum/BY3PR09MB806796FA4E3A1178FFD8213BB3C89%40BY3PR09MB8067.namprd09.prod.outlook.com.

Larry Baker

unread,
Jan 23, 2023, 7:44:47 PM1/23/23
to mmere...@usbr.gov, Larry Baker, 'jona...@ntu.edu.sg' via Earthworm Community Forum
SNW sounds suspiciously like SeisNet Watch.
-- 

El Berto

unread,
Jan 24, 2023, 3:23:57 AM1/24/23
to Earthworm Community Forum
Never heard about TYPE_SNW messages in _tty or _tcp K2 modules.

Nicholas Novoa, CDWR

unread,
Jan 24, 2023, 11:02:17 AM1/24/23
to Earthworm Community Forum
Hi Mark,
Lynn is right. You just need to add a line like " Message  TYPE_SNW           120" near the bottom of your earthworm.d file. The actual number may vary depending on your existing message-type mappings. I believe the k2ew_tcp module was modified between the 7.8 and 7.9 releases (might have been between 7.9 and 7.10) to read state of health information and create Type_SNW messages for SeisNetWatch. I had problems with the module dying and not restarting, so we ultimately reverted back to the version of the module that was released with 7.8. Hopefully, you have better luck.

Nick

Reply all
Reply to author
Forward
0 new messages