Open sjspielman opened 6 months ago
Just noting this original issue here. Although I don't know if any of the things from the original issue really need to be addressed anymore so I'm going to close the old one.
Maybe switching between docker and singularity would be the most helpful from that list.
🎢 from #690, just in case...
Some ideas to include right now would be:
- how to clear the nextflow cache for the repo if trying to run an updated version
- how to change the name of the queue used for your job scheduler (some places call it partition)
- how to switch between docker and singularity
Rather than adding
-r
everywhere, maybe we add a "troubleshooting" section? I would say if you see that error, trynextflow pull AlexsLemonade/scpca-nf
to get the latest release, then try again. In general, I would rather have external users use the latest version unless they have a reason to stick with an old one.Originally posted by @jashapiro in https://github.com/AlexsLemonade/scpca-nf/issues/688#issuecomment-1930626095
As quoted above, we may want a troubleshooting section which includes the "error" that users may encounter if they don't provide
-r
.