A puzzle on how the event ID numbers in hypoinverse output summary are assigned?

[JUNZHU-SEIS]

Hi,
I test the picker/associater of PAL for OBS data. Both of them work pretty well but the hypoinverse part doesn't, in which many events even have origin time following the phase arrivals. Below is an example event in the output full.pha file.

20161227054615.49,11.7858,141.8110,-0.9,-2.00,0
MA.y09,2016-12-17T05:38:25.100000Z,2016-12-17T05:38:33.800000Z,1791.55453134137,230.7
MA.y03,2016-12-17T05:38:25.600000Z,2016-12-17T05:38:34.450000Z,1027.8541081597514,31.8
MA.y06,2016-12-17T05:38:26.440000Z,2016-12-17T05:38:35.620000Z,4893.81141548549,172.5
MA.y07,2016-12-17T05:38:21.570000Z,2016-12-17T05:38:26.160000Z,6748.022477182553,6.4

So I guess there may be something wrong when joining event line and phase lines. I try to understand every line of your sum2csv.py code. For the line below, I have a puzzle.

PAL/hypoinverse/sum2csv.py

Line 43 in 8203019

evid = sum_line.split()[-1]

I found the number of event lines in the .sum file equals the event number in input phase file. I suspect that the ID numbers reported by hypoinverse may be wrong, which are restricted to 0-17 and repeat 10 times each while I have 171 events in my input phase file.
So I change this line

PAL/hypoinverse/sum2csv.py

Line 43 in 8203019

evid = sum_line.split()[-1]

into

  for i,sum_line in enumerate(sum_lines):
    evid = str(i)

It seems work. Below are the output full.pha file.

20161217053813.59,12.4832,141.5732,30.1,-2.00,0
MA.y09,2016-12-17T05:38:25.100000Z,2016-12-17T05:38:33.800000Z,1791.55453134137,230.7
MA.y03,2016-12-17T05:38:25.600000Z,2016-12-17T05:38:34.450000Z,1027.8541081597514,31.8
MA.y06,2016-12-17T05:38:26.440000Z,2016-12-17T05:38:35.620000Z,4893.81141548549,172.5
MA.y07,2016-12-17T05:38:21.570000Z,2016-12-17T05:38:26.160000Z,6748.022477182553,6.4