FFFF EmptyDataError / ' Updating to current Sample Annotation' always triggers · Issue #677 · gagneurlab/drop · GitHub
[go: up one dir, main page]

Skip to content

EmptyDataError / ' Updating to current Sample Annotation' always triggers #677

Open

Description

@Queex

(Potentially related to #676)

While trying to run using the --slurm parameter, I've encountered the following error in one of jobs:

26517848.log

This seems to be an error, possibly caused by an incomplete file. However, the other jobs despatched in the same run do not choke at this point, as in this example:

26517843.log

I think this is being caused by the jobs always determining that the sample annotation has changed (even though it hasn't - indeed cannot have - changed between these jobs starting to run). If two jobs hit that point at the same time, concurrency means that one finds an empty or missing file as the other is writing it. I would have thought that this check and update should only happen at most once, when the main snakemake thread begins; either by explicitly skipping that part when the sub-jobs run or because the initial input files have not changed.

What might be causing the scripts to attempt to update those .csv files on every run, and what can I do to fix it?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0