Additional example

[Alkohost]

Can you please add a step-by-step example with instructions for own data (jupyter example)?

According to issue #18 set a path to mountainsort4_1_0 using sys.path.append('.../mountainsort_examples-master/python') Is this step necessary or there are other ways to fix it?

According to .mda format descriptions generate for own data raw.mda (easy to do with mdaio for Matlab) geom.csv params.json

To solve 'widjets' problem use conda install -c tjd2002 'mountainlab_pytools=0.7.4'

All other initialization instructions according to ms4_jupyter_example.ipynb and just call ms4_sort_dataset

What '.prv' is actually, when it necessary and when is not?

[tjd2002]

The files ending *_true are the original ‘ground truth’ data used to simulate spiking in the synthetic datasets.

When you are working with real electrophysiological recordings, you will not have these files, since you don’t know what the ground truth is (if you did, you wouldn’t need to do spike sorting 😁)

A .prv file is essentially a link to a larger data file elsewhere in the MountainLab search path. A .prv file can be used anywhere that the original file was used (I.e. you can generally just ignore this suffix).

Sent from my phone

On Jan 28, 2019, at 7:10 AM, Alkohost notifications@github.com wrote:

Hello.

Can you please add an example with descriptions for own data?

According to .mda format descriptions I generate for own data raw.mda geom.csv params.json

but synthesize_dataset generates also firings_true.mda.prv waveforms_true.mda.prv

How to create these files and is '.prv' necessary?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Alkohost]

Thank you, I understood all items and just asked for a more detailed ReadMe if possible. Please see the updated comment above.