You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The thing to do would be to use argmin instead of min to find the time index that is minimum, and then use that index to get the time and position of the first source.
In summary:
The flash IDs go with the correct sources
The start time is correct
The start lat/lon/alt is incorrect when using mflash
The problem could be corrected by manually recalculating the flash metadata table after applying my suggested fix.
The text was updated successfully, but these errors were encountered:
It applies to data sorted with the mflash clustering method. It may also apply to the sklearn clustering method, but this has not been verified.
The point data are recorded out of order to the HDF5 file, because I sort the mflash output (which I verified is in time order) by flash_id to split the flashes up.
https://github.com/deeplycloudy/lmatools/blob/master/flashsort/autosort/autorun_mflash.py#L114
That sort algorithm, when applied to flash_id, isn’t guaranteed to preserve the original time order.
The time is still calculated correctly, since I take the minimum of the time:
https://github.com/deeplycloudy/lmatools/blob/master/flashsort/autosort/flash_stats.py#L142
But the initial position is taken to be the first index, which isn’t guaranteed to be the minimum since the time is not sorted in order:
https://github.com/deeplycloudy/lmatools/blob/master/flashsort/autosort/flash_stats.py#L146
The thing to do would be to use argmin instead of min to find the time index that is minimum, and then use that index to get the time and position of the first source.
In summary:
The text was updated successfully, but these errors were encountered: