Skip to content

Conversation

@bergsalex
Copy link
Collaborator

@bergsalex bergsalex commented Sep 30, 2025

This PR adds a new workflow that automates the generation of classifier artifacts for the main workflow.

This will allow us to easily regenerate classifiers existing for new versions of JABs, as well as add new classifiers by placing their project directory into the /projects/kumar-lab/projects directory and updating the classifier_source.config file.

There are still some tasks left to-do before this PR is ready to merge:

  • Run the workflow with existing classifiers (except grooming)
  • Run the workflow with the grooming classifier
  • Add a jabs-init step to allow the classifiers to be generated in parallel
  • Run the workflow with thejabs-init step
  • Add @jacobbeierle's new classifiers
  • Prepare the /projects/kumar-lab/data/ and /projects/kumar-lab/projects directories for use with this workflow
  • Clean up the implementation with improved documentation

Review of the current state would be appreciated given acknowledgement of the above.

@bergsalex bergsalex self-assigned this Sep 30, 2025
@bergsalex bergsalex added the enhancement New feature or request label Sep 30, 2025
@bergsalex bergsalex requested a review from vivekJax September 30, 2025 11:29
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want configs outside the configs folder?

"stitch_value": 5,
"filter_value": 5,
],
// "Leg_splaying": [ // Currently can't be exported successfully
Copy link
Contributor

Choose a reason for hiding this comment

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

JABS v0.34 + should have this fixed. I was able to build that artifact for #75. This classifier should be okay to uncomment and include.

script:
def project_path = "${params.classifier_project_folders}/${project_folder_name}"
"""
jabs-init "${project_path}" ${window_sizes} -p 16
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this write into the frozen project folder? This may cause conflicts in 2 situations:

  1. no write permission (maybe we want it this way, because it'll fail later when trying to publish results)
  2. 2 builds running at the same time will compete writing feature files to the same location

"filter_value": 3*30,
'grooming': [
classifier_path: '/projects/kumar-lab/data/jabs/classifiers/v0.37.0/grooming/12199145d31213f79e23669d211cfa2fd33cedb9f11197b44f90a4b71297b6d2.pickle',
stitch_value: 300,
Copy link
Contributor

Choose a reason for hiding this comment

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

😢 I like the multiplication to see 10s and 3s more clearly.

Copy link
Contributor

Choose a reason for hiding this comment

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

These look like patches for something not working. These should have been in a different PR to fix the main modules.

@bergsalex bergsalex marked this pull request as ready for review October 7, 2025 19:11
@bergsalex bergsalex merged commit 7aadb1b into main Oct 7, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants