Time reordering
See original GitHub issueSupport for different time reorderings.
- For example, there could be a set of special files
spike_times.myreorder1.npy
that would be like the existingspike_times.npy
, but with different spike times (for example, a reordering of the normal spike times). - One could switch between these different sets of spike times with a keyboard shortcut.
- The following views should be updated accordingly:
- Diagonal subplots in Feature view
- Amplitude view
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Timing Is Everything: The Science of Reordering - Wonderment
When asking someone to reorder, better timing leads to better conversions. Here's how to get the timing right.
Read more >Reorder point - Wikipedia
The reorder point (ROP) is the level of inventory which triggers an action to replenish that ... the forecast usage during the replenishment...
Read more >Reorder Point – Definition, Formula & Importance - Zoho
You should reorder when you have 40 boxes of stock left in your inventory, which is four days of stock. Given that your...
Read more >Reorder Point Formula and Safety Stock: A Complete Guide
The reorder point formula is daily unit sales multiplied by delivery lead time, with some safety stock for good measure.
Read more >Rabbit Order: Just-in-Time Parallel Reordering for Fast Graph ...
This paper presents a first algorithm for just-in-time parallel reordering, named Rabbit Order. It reduces end-to-end runtime by achieving high locality and ...
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
I think just those two are enough.
Hey guys,
I wanted to take a look at spike amplitudes in batch-reordered state, but I’m not sure where/how to generate a corresponding
spike_times_reordered.npy
output. Is there a straightforward point within the normal processing stream (rezToPhy
?) to just add an extra column to st3 for these reordered timestamps?Even without creating an alternate
spike_times_reordered.npy
file, togglingctrl+r
in Phy does produce slight data point shifts & histogram bin changes in the AmplitudeView, leaving me extra confused as to what/how that was implementedThanks!