search

ncssar / radiolog

SAR radio log program
Other
13 stars 3 forks source link

change callsign dialog not opening when needed #675

Closed caver456 closed 11 months ago

caver456 commented 1 year ago

During review of the log and transcript from full team training 7/8/23, noticed that device 100:3063 has an entry as '1SAR63' but then later reverts to callsign 'KW-100-3063'. Also the log had some other callsigns of the format 'KW-100-xxxx'.

First look at the transcript seems like the CCD didn't open for 3063, because it was already open for a different device at 163003 (openChangeCallsignDialog 100:3115)? Should openChangeCallsign happen immediately after setting needsChangeCallsign? 

162941:PARSING
162941:I110031151003115
162941: line:I110031151003115
162941:getCallsign called for fleet=100 dev=3115
162941:found matching entry/entries:[]
162941: no match; returning default callsign.
162941:CID detected (not in $PKLSH): fleet=100  dev=3115  callsign=KW-100-3115
162941:checking for existing open new entry tabs: callsign=KW-100-3115 continueSec=20
162941:checking against existing widget: to_from=FROM team=Team 101 lastModAge:-1
162941:checking against existing widget: to_from=FROM team=KW-100-3126 lastModAge:-1
162941:checking against existing widget: to_from=FROM team=Team 102 lastModAge:-1
162941:updating fsLog: fleet=100 dev=3115 callsign=<None>  COM port=COM3
162941:getCallsign called for fleet=100 dev=3115
162941:found matching entry/entries:[]
162941: no match; returning default callsign.
162941:no other new entry tab was found for this callsign; inside fsParse: calling openNewEntry
162941:openNewEntry called:key=fs callsign=KW-100-3115 formattedLocString= fleet=100 dev=3115 origLocString= amendFlag=False amendRow=None isMostRecentForCallsign=False
162941:newEntryWidget __init__ called: formattedLocString= fleet=100 dev=3115 origLocString= amendFlag=False amendRow=None isMostRecentForCallsign=False
162941:newEntryWidget.addTab called: labelText=1629  widget=<__main__.newEntryWidget object at 0x000001DA4B76EB00>
162941:inserting tab
162941:First non-mic-bump call from this device.
162941:Setting needsChangeCallsign since this is the first call from the device and the beginning of its default callsign "KW-100-3115" is specified in CCD1List
162955:PARSING
162955:I010020201002020
162955: line:I010020201002020
162955:getCallsign called for fleet=100 dev=2020
162955:found matching entry/entries:[[100, 2020, 'Team 102']]
162955:CID detected (not in $PKLSH): fleet=100  dev=2020  callsign=Team 102
162955:checking for existing open new entry tabs: callsign=Team 102 continueSec=20
162955:checking against existing widget: to_from=FROM team=Team 101 lastModAge:-1
162955:checking against existing widget: to_from=FROM team=KW-100-3126 lastModAge:-1
162955:checking against existing widget: to_from=FROM team=Team 102 lastModAge:-1
162955:  new entry widget is already open from this callsign within the 'continue time'; not opening a new one
162955:location strings updated because the message is not relayed
162955:checking against existing widget: to_from=FROM team=KW-100-3115 lastModAge:-1
162955:updating fsLog: fleet=100 dev=2020 callsign=<None>  COM port=COM3
162956:PARSING
162956:$PKLDS,232955,A,3918.6679,N,12054.9697,W,,,,,00,100,2020,80,00,*15

$PKLSH,3918.6679,N,12054.9697,W,232955,A,100,2020,*3D

$GPRMC,232955,A,3918.6679,N,12054.9697,W,,,,,*0B

$GPGGA,232955,3918.6679,N,12054.9697,W,1,,,,,,,,*4A


162956: line:$PKLDS,232955,A,3918.6679,N,12054.9697,W,,,,,00,100,2020,80,00,*15

162956: line:$PKLSH,3918.6679,N,12054.9697,W,232955,A,100,2020,*3D

162956:getCallsign called for fleet=100 dev=2020
162956:found matching entry/entries:[[100, 2020, 'Team 102']]
162956:$PKLSH detected containing CID: fleet=100  dev=2020  -->  callsign=Team 102
162956:Valid location string:'3918.6679|N|12054.9697|W'
162956:convertCoords called: targetDatum=WGS84 targetFormat=UTM 5x5 coords=['3918.6679', 'N', '12054.9697', 'W']
162956:Formatted location string:'79658  53374'
162956:convertCoords called: targetDatum=WGS84 targetFormat=D.dList coords=['3918.6679', 'N', '12054.9697', 'W']
162956:WGS84 lat=39.31113166666667  lon=-120.91616166666667
162956: line:$GPRMC,232955,A,3918.6679,N,12054.9697,W,,,,,*0B

162956: line:$GPGGA,232955,3918.6679,N,12054.9697,W,1,,,,,,,,*4A

162956: line:
162956:checking for existing open new entry tabs: callsign=Team 102 continueSec=20
162956:checking against existing widget: to_from=FROM team=Team 101 lastModAge:-1
162956:checking against existing widget: to_from=FROM team=KW-100-3126 lastModAge:-1
162956:checking against existing widget: to_from=FROM team=Team 102 lastModAge:-1
162956:  new entry widget is already open from this callsign within the 'continue time'; not opening a new one
162956:location strings updated because the message is not relayed
162956:checking against existing widget: to_from=FROM team=KW-100-3115 lastModAge:-1
162956:updating fsLog: fleet=100 dev=2020 callsign=<None>  COM port=COM3
162956:calling processEvents before sending GET request...
162956:Sending GET request:
162956:http://192.168.1.20:8080/rest/location/update/position?lat=39.31113166666667&lng=-120.91616166666667&id=FLEET:100-Team 102
162956:  exception during sending of GET request: HTTPConnectionPool(host='192.168.1.20', port=8080): Max retries exceeded with url: /rest/location/update/position?lat=39.31113166666667&lng=-120.91616166666667&id=FLEET:100-Team%20102 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000001DA4B6A6F20>, 'Connection to 192.168.1.20 timed out. (connect timeout=0.0001)'))
163003:Accepted
163003:newEntry called with these values:

163003:['1628', 'FROM', 'Team 102', 'will retrieve hat', '79658  53374', '', 1688858887.98316, '100', '2020', '3918.6679|N|12054.9697|W']
163003:Accepted2
163003:  writing C:\Users\NCSSAR\RadioLog\FTT_2023_07_08_121532\FTT_2023_07_08_121532.csv
163003:  done writing C:\Users\NCSSAR\RadioLog\FTT_2023_07_08_121532\FTT_2023_07_08_121532.csv
163003:  writing X:\FTT_2023_07_08_121532.csv
163003:  done writing X:\FTT_2023_07_08_121532.csv
163003:  writing C:\Users\NCSSAR\RadioLog\FTT_2023_07_08_121532\FTT_2023_07_08_121532_clueLog.csv
163003:  done writing C:\Users\NCSSAR\RadioLog\FTT_2023_07_08_121532\FTT_2023_07_08_121532_clueLog.csv
163003:  writing X:\FTT_2023_07_08_121532_clueLog.csv
163003:  done writing X:\FTT_2023_07_08_121532_clueLog.csv
163003:openChangeCallsignDialog called.  fleet=100  dev=3115
163004:PARSING
163004:I110030631003063
163004: line:I110030631003063
163004:getCallsign called for fleet=100 dev=3063
163004:found matching entry/entries:[]
163004: no match; returning default callsign.
163004:CID detected (not in $PKLSH): fleet=100  dev=3063  callsign=KW-100-3063
163004:checking for existing open new entry tabs: callsign=KW-100-3063 continueSec=20
163004:checking against existing widget: to_from=FROM team=Team 101 lastModAge:-1
163004:checking against existing widget: to_from=FROM team=KW-100-3126 lastModAge:-1
163004:checking against existing widget: to_from=FROM team=KW-100-3115 lastModAge:-1
163004:updating fsLog: fleet=100 dev=3063 callsign=<None>  COM port=COM3
163004:getCallsign called for fleet=100 dev=3063
163004:found matching entry/entries:[]
163004: no match; returning default callsign.
163004:no other new entry tab was found for this callsign; inside fsParse: calling openNewEntry
163004:openNewEntry called:key=fs callsign=KW-100-3063 formattedLocString= fleet=100 dev=3063 origLocString= amendFlag=False amendRow=None isMostRecentForCallsign=False
163004:newEntryWidget __init__ called: formattedLocString= fleet=100 dev=3063 origLocString= amendFlag=False amendRow=None isMostRecentForCallsign=False
163004:newEntryWidget.addTab called: labelText=1630  widget=<__main__.newEntryWidget object at 0x000001DA4B76A950>
163004:inserting tab
163004:First non-mic-bump call from this device.
163004:Setting needsChangeCallsign since this is the first call from the device and the beginning of its default callsign "KW-100-3063" is specified in CCD1List
163016:PARSING
163016:I110030631003063
163016: line:I110030631003063
163016:getCallsign called for fleet=100 dev=3063
163016:found matching entry/entries:[]
163016: no match; returning default callsign.
163016:CID detected (not in $PKLSH): fleet=100  dev=3063  callsign=KW-100-3063
163016:checking for existing open new entry tabs: callsign=KW-100-3063 continueSec=20
163016:checking against existing widget: to_from=FROM team=Team 101 lastModAge:-1
163016:checking against existing widget: to_from=FROM team=KW-100-3126 lastModAge:-1
163016:checking against existing widget: to_from=FROM team=KW-100-3115 lastModAge:-1
163016:checking against existing widget: to_from=FROM team=KW-100-3063 lastModAge:-1
163016:  new entry widget is already open from this callsign within the 'continue time'; not opening a new one
163016:location strings updated because the message is not relayed
163016:updating fsLog: fleet=100 dev=3063 callsign=<None>  COM port=COM3
caver456 commented 11 months ago

All occurrances of 'openChangeCallsignDialog called', which happens in changeCallsignDialog.init (in v3.7.0 which was used in that session), and 'callsign pairing created', which happens in changeCallsignDialog.accept: (all listed here in chronological order; pairings indented to visually stand out)

122649:openChangeCallsignDialog called.  fleet=100  dev=3137
123507:openChangeCallsignDialog called.  fleet=100  dev=3096
125109:openChangeCallsignDialog called.  fleet=100  dev=3020
130840:openChangeCallsignDialog called.  fleet=100  dev=3010
133929:openChangeCallsignDialog called.  fleet=100  dev=3008
  133956:New callsign pairing created: fleet=100  dev=3008  callsign=Team 101
134051:openChangeCallsignDialog called.  fleet=100  dev=2005
134253:openChangeCallsignDialog called.  fleet=100  dev=3051
  134309:New callsign pairing created: fleet=100  dev=3051  callsign=Team 104
135507:openChangeCallsignDialog called.  fleet=100  dev=3109
135716:openChangeCallsignDialog called.  fleet=100  dev=3133
  135722:New callsign pairing created: fleet=100  dev=3133  callsign=Team 102
140022:openChangeCallsignDialog called.  fleet=100  dev=3089
  140026:New callsign pairing created: fleet=100  dev=3089  callsign=Team 103
140712:openChangeCallsignDialog called.  fleet=100  dev=2005
  140719:New callsign pairing created: fleet=100  dev=2005  callsign=Team 105
141642:openChangeCallsignDialog called.  fleet=100  dev=2006
142922:openChangeCallsignDialog called.  fleet=100  dev=3100
143720:openChangeCallsignDialog called.  fleet=100  dev=3018
145526:openChangeCallsignDialog called.  fleet=100  dev=3105
  145539:New callsign pairing created: fleet=100  dev=3105  callsign=Team 103
145900:openChangeCallsignDialog called.  fleet=100  dev=2020
150509:openChangeCallsignDialog called.  fleet=100  dev=3035
  160529:New callsign pairing created: fleet=100  dev=2020  callsign=Team 102
151146:openChangeCallsignDialog called.  fleet=100  dev=3126
160521:openChangeCallsignDialog called.  fleet=100  dev=2020
163003:openChangeCallsignDialog called.  fleet=100  dev=3115
163057:openChangeCallsignDialog called.  fleet=100  dev=3063
164426:openChangeCallsignDialog called.  fleet=100  dev=3115

The quickest that a CCD was accepted after its opening was 4 seconds, and the slowest was 29 seconds (followed by 27, 14, 13, 7, 6). Most often, the CCD was never accepted.

Some context on this session: this full team training was used to give some operator time to various operators, none of which had any previous training on the software. Since many members were calling in, it's possible that the message stack was getting busy and adding extra confusion.

Takeaways: