-
Notifications
You must be signed in to change notification settings - Fork 6
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
view usage/verification #7
Comments
Re verification, that's a good idea. Headers - I don't know... Good question. All rules support a view (where the underlying command supports it, so not chromosight or mustache), just define it once at the top of the config and it will be applied everywhere. |
Verification is done! Just in the main code in the Snakefile for local coolers, and immediately in the download rule for remote coolers. |
In general there are a lot more checks that con be done on all inputs, we can just start a separate issue with a checklist for that. |
|
After all I keep getting errors for view that are totally valid, no idea why.... |
would it make sense to verify view/cooler compatibility before launching all rules?
also, did we decide that views should be saved w/o headers?
it seems that many rules don't support views-- should that be a future upgrade?
The text was updated successfully, but these errors were encountered: