Skip to content

add ci tests #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 26 commits into from
Jun 26, 2022
Merged

add ci tests #26

merged 26 commits into from
Jun 26, 2022

Conversation

bendichter
Copy link
Collaborator

No description provided.

@@ -0,0 +1,33 @@
#from spikeinterface.extractors import toy_example
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ben, I would move this file to spikeinterface/sorters/tests.
We choose to put testing file "inplace" in the relative of the submodule.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine as long as we can keep this ci here

@bendichter
Copy link
Collaborator Author

@vncntprvst, @chyumin, @JuliaSprenger do you think you could use this structure to help put together functioning tests for each non-GPU singularity container?

@bendichter
Copy link
Collaborator Author

I agree with @samuelgarcia that we should move this over to spikeinterface, but it is more convenient to develop here for now. We can move it over once it is passing.

@chyumin
Copy link
Collaborator

chyumin commented Jun 8, 2022

@vncntprvst, @chyumin, @JuliaSprenger do you think you could use this structure to help put together functioning tests for each non-GPU singularity container?

yes definitely! thank you

kwargs = dict(recording=recording2, verbose=True, singularity_image=True)


@pytest.mark.xfail(reason="FAILING: investigate why")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is happening because of inconsistent naming format:

  • spykingcircus used to call run_sorter
  • spyking_circus as python module
  • spyking-circus as image name

I have created this PR to properly raise the error

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed SORTER_DOCKER_MAP in run_sorter.py from spikeinterface for tests.
We need to unify naming format for spyking-cirucs

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also I'm getting error using data from generate_recording for spyking-circus.

When I change to toy data it works well:

se.toy_example(
        duration=30,
        seed=0,
        num_channels=32,
        num_segments=1
    )

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

strange! @alejoe91, do you have any idea why one might work and not the other?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The image runs well, but It was raising here when extracting output.
I could see different result[...].hdf5 files in output folder, but not 'result-merged.hdf5' or 'result.hdf5'

This was referenced Jun 20, 2022
@alejoe91 alejoe91 merged commit 788772f into main Jun 26, 2022
@alejoe91 alejoe91 deleted the add_ci_tests branch June 5, 2023 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants