Identify bursts groups also using the burst number
See original GitHub issueScheme proposed by @alexamici:
- remove the (slow) parsing of GCP on
open_dataset(..., group=None)
and only report available groups by burst_id, e.g.["IW1/1", "IW1/2", ...]
- move the naming logic to an external function in
xarray_sentinel
that takes either the filename or the gcp dataset (whatever is more reasonable) and returns the mapping between the label and the burst_id
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Parameters for burst detection - Frontiers
A burst was identified if N spikes occurred in less than T ms, where the threshold T was automatically determined from observing a...
Read more >Detection of Bursts and Pauses in Spike Trains - PMC - NCBI
Burst detection methods that are based on interspike interval (ISI) duration, with a criterion for a minimal number of spikes with short ...
Read more >The Burst Analyzer Tutorial - Becker & Hickl GmbH
With Burst Analyzer you can find and analyzer such bursts in many different ways. ... which is also located in the Start//Traces Visibility...
Read more >Detection of bursts in neuronal spike trains by the mean inter ...
This method is based on characteristics of ISI sequences and identifies bursts as 'many' spikes with a 'small' interval (spike cluster).
Read more >Fast Algorithms for Burst Detection - NYU Courant
[89] and Kleinberg [55] focus on bursty behaviors and modeling, our focus is a high-performance algorithm to detect bursts across multiple window sizes....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Pretty much all groups use a ascending node based scheme since you don’t need to read a lot of metadata or do geometry based computations to do the labeling. Lot of them are in public literature, e.g - https://www.mdpi.com/2072-4292/12/18/2960/htm . Exact implementation doesnt matter as long as the labeling is consistent.
@scottyhq & @piyushrpt current
main
is a big refactor and there is a defined way to access burst data via the burst index in the swath.See: https://github.com/bopen/xarray-sentinel#crop-single-slc-burst-dataset
I plan to make a release soon, then we will try to add more ways to identify and access a burst.