Skip to content

Commit

Permalink
Update get_started and we_to_sa
Browse files Browse the repository at this point in the history
  • Loading branch information
chrishalcrow committed Apr 17, 2024
1 parent a1cacde commit b273622
Show file tree
Hide file tree
Showing 12 changed files with 133 additions and 426 deletions.
191 changes: 128 additions & 63 deletions doc/how_to/get_started.rst

Large diffs are not rendered by default.

Binary file removed doc/how_to/get_started_files/get_started_52_0.png
Binary file not shown.
Binary file added doc/how_to/get_started_files/get_started_55_0.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed doc/how_to/get_started_files/get_started_90_1.png
Binary file not shown.
Binary file removed doc/how_to/get_started_files/get_started_90_2.png
Binary file not shown.
Binary file added doc/how_to/get_started_files/get_started_93_1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added doc/how_to/get_started_files/get_started_93_2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 4 additions & 3 deletions doc/how_to/waveform_extractor_to_sorting_analyzer.rst
Original file line number Diff line number Diff line change
Expand Up @@ -312,9 +312,9 @@ Compute Extensions

Waveforms, templates, quality metrics etc are all extensions of the ``SortingAnalyzer`` object.
Some extensions depend on other extensions. To calculate a *child* we must first have calculated its
**parents**. The relationship between some commonly used extensions are shown below:
**parents**. The relationship between all the currently available extensions is displayed below:

.. image:: waveform_extractor_to_sorting_analyzer_files/child_parent_plot.svg
.. image:: ../images/parent_child.svg
:alt: Child parent relationships

We see that to compute ``spike_amplitudes`` we must first compute ``templates``. To compute templates
Expand Down Expand Up @@ -348,7 +348,8 @@ looks slightly different. Let's calculate these extensions, and also add a param
peak_sign="pos"
)
Read more about extensions and their keyword arguments in the
Note that if a parent is recomputed, all its children are deleted to maintain data consistency.
Read more about this, the extensions and their keyword arguments in the
`postprocessing module documentation <https://spikeinterface.readthedocs.io/en/latest/modules/postprocessing.html>`_

In many cases, you can still use the old notation for ``SortingAnalyzer`` objects,
Expand Down

This file was deleted.

2 changes: 1 addition & 1 deletion examples/how_to/get_started.py
Original file line number Diff line number Diff line change
Expand Up @@ -254,7 +254,7 @@
analyzer_TDC.compute("template_similarity", method="cosine_similarity")
# -

# Find out more about the available parameters and extensions [here](https://spikeinterface.readthedocs.io/en/latest/modules/postprocessing.html#available-postprocessing-extensions).
# Find out more about the available parameters and extensions [here](https://spikeinterface.readthedocs.io/en/latest/modules/postprocessing.html).

# The calculations are saved in the `extensions` subfolder of the `SortingAnalyzer` folder.
# Similar to the waveforms we can access them using `get_extension` and `get_data`. For example,
Expand Down

0 comments on commit b273622

Please sign in to comment.