Skip to content
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

Cron jobs for running workflows and publishing results #16

Closed
ajtritt opened this issue Dec 12, 2024 · 1 comment
Closed

Cron jobs for running workflows and publishing results #16

ajtritt opened this issue Dec 12, 2024 · 1 comment
Assignees
Labels
analysis@nersc analysis workflows at NERSC (bilbomd, alphafold, docking)

Comments

@ajtritt
Copy link
Contributor

ajtritt commented Dec 12, 2024

Set up cron jobs in Spin or Perlmutter workflow queue for running AlphaFold jobs and submitting the results to JAMO.

We need two cron jobs:

  1. A cron job to check the Jira project for new work and submitting jobs to Perlmutter. Jobs should output to a specific directory
  2. A cron job to check the output directory from step 1 for new results and push results to Jira and JAMO. This should use the scripts developed as part of Push AlphaFold results to JAMO t5-data#3
@ajtritt ajtritt self-assigned this Dec 12, 2024
@oruebel oruebel added the analysis@nersc analysis workflows at NERSC (bilbomd, alphafold, docking) label Feb 26, 2025
@ajtritt ajtritt changed the title Cron job for running AlphaFold and publishing results Cron job for running workflows and publishing results Feb 27, 2025
@ajtritt ajtritt changed the title Cron job for running workflows and publishing results Cron jobs for running workflows and publishing results Feb 27, 2025
@ajtritt
Copy link
Contributor Author

ajtritt commented Mar 8, 2025

This was addressed by #29

@ajtritt ajtritt closed this as completed Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis@nersc analysis workflows at NERSC (bilbomd, alphafold, docking)
Projects
None yet
Development

No branches or pull requests

2 participants