-
Notifications
You must be signed in to change notification settings - Fork 3
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
Allow users to generate pipelines from YAML files #563
Conversation
for more information, see https://pre-commit.ci
Likely we'll want to improve the user workflow here before merging into @CodyCBakerPhD Let me know what you think is best, though this should be fully functional. |
@garrettmflynn This particular feature is not intended to be the generic 'import from YAML' to be exposed to users; that feature would use the NeuroConv specific YAML structure (different from what I shared), and is largely dependent on the custom backend feature to be useful (and possibly other aspects, too) hence why it's not even on the current release roadmap This particular feature was only supposed to result in a single button on the settings page for developers to point to their local copy of the GIN repos and auto-generate all pre-established pipelines defined in that YAML file (which will grow over time; each entry essentially being a test case) |
Got it. Constrained the behavior to load the provided file rather than allow the selection of a custom YAML file. |
Perhaps under a 'Developer' testing header like the 'DANDI' one |
Ah I see. Phy always was, but the SpikeGLX single-probe example had the wrong interface specified (should be |
Updated with this new grouping! |
for more information, see https://pre-commit.ci
Delightful |
Awww, Chromatic build failure: https://github.com/NeurodataWithoutBorders/nwb-guide/actions/runs/7628567110/job/20779934786?pr=563 |
This PR allows for users to generate pipelines from a YAML file on the Settings page. Currently, enough metadata is pre-filled to simply click through the conversion without any interactions.
This is the first step to fix #511, where we can expand the test YAML file (
guide_testing_suite.yml
) to account for all interfaces.Since receiving the test YAML file from @CodyCBakerPhD, I've removed the
base_data_path
property to improve the shareability of the file itself and fixed thePhySortingInterface
folder path to target the correct subdirectory.