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

Snakemake modifications for big models #10

Open
Timon-R opened this issue Jan 23, 2024 · 3 comments
Open

Snakemake modifications for big models #10

Timon-R opened this issue Jan 23, 2024 · 3 comments

Comments

@Timon-R
Copy link

Timon-R commented Jan 23, 2024

I used the workflow on a big model with 300 runs and had to make adjustments to the snakemake workflow. I note them here for convenience.

  • Change shell commands to script commands when there are multiple arguments. Command line commands have limited arguments and if lists are given, this can cause the workflow to break.
  • Use priority: 100 for the function that solves the lp file as well as for all functions that process it
  • and use priority 0 for the function that creates it; also give the function that creates the lp file 4 threats. Reason for this is that the lp file is large and can take up a lot of space on your hard drive.
@robertodawid
Copy link

robertodawid commented Jul 30, 2024

Hi @Timon-R , I am running the snakemake workflow in Windows. It seems there are issues with the (shell sections in the workflow) since most of these sections were developed for *nix. I am NOT super literate on this, but you mentioned changing the shell commands to scrips. Would that work on Windows? If so, do you have an example I can look at? or in any case. Would you happen to have a suggestion so I can run the workflow in Windows.?

@Timon-R
Copy link
Author

Timon-R commented Jul 31, 2024

Hi @robertodawid, try using my modified workflow for Windows: https://github.com/Timon-R/OSEMBN

@robertodawid
Copy link

Hi @Timon-R , I am running the snakemake workflow in Windows. It seems there are issues with the (shell sections in the workflow) since most of these sections were developed for *nix. I am NOT super literate on this, but you mentioned changing the shell commands to scrips. Would that work on Windows? If so, do you have an example I can look at? or in any case. Would you happen to have a suggestion so I can run the workflow in Windows.?

Dear @Timon-R , Thanks! I took a couple of the *.py from your workflow, and now mine seems to be working.

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

No branches or pull requests

2 participants