jbwexler

So I tried `git annex find --unlocked` in the dataset while the job was running to see if the files were getting successfully unlocked. Interestingly, when I first checked for...

Here is the reproman command: ``` reproman run -r local --sub slurm --orc datalad-no-remote \ --bp sub="$sub_list" --output . \ --jp num_processes="$processes" --jp num_nodes="$nodes" \ --jp walltime="$walltime" --jp queue="$queue" --jp...

I was able to solve this using the "More scalable workaround ". Essentially the following: 1) Delete all fmriprep results from dataset pertaining to subjects that will be rerun. 2)...

Thanks! To clarify, would the solution involving changing the `working_directory` also require ephemeral clones or those are two separate solutions? I think generally the input data is pretty separate between...

Sounds good, I'll probably take a look at it next week

I'm finally coming back to this. One question: I'm currently using datalad-no-remote as an orchestrator - will the proposed solution be compatible with this?

> may be in your case you don't need anything "datalad" Do you mean don't need anything "reproman"? I think one of the main reasons we were using reproman is...

Is there a workaround for this that doesn't involve making a commit? Currently I add the --bind in .datalad/config but that's not the most yoda-friendly.

So would it be helpful for us to upload a new revision of this dataset that fixes this issue? Or is it easy enough to work around? Is it something...

We are currently trying to decide on practices for the workflow that will be used consistently, which will hopefully help with machine readability. One change we are planning to make...