Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've been hacking on the code, after deciding that just tinkering to see what works is more productive than trying to understand all the nuances of the tools and standards and plan things out. As you know, my interest is more on the "testing" RO-Crate than the "provenance" but there is surely plenty of overlap.
I thought making a PR was the best way to share what I got so far so you can readily see the diff. I don't expect you to merge this! Unfortunately, most of the code is just testing files in the CWD which is not really making use of the fact that the code runs as a Snakemake plugin. It may as well just be a standalone script.
But I'm currently looking to see if I can trigger the
--dag
export code from Snakemake as part of the plugin, in order to auto-make therulegraph.svg
file which I think would be useful. This is going to involve using some real Snakemake internals, and may or may not be hampered by the fact that Snakemake innards are all based on coroutines in a structure I don't really understand.Any comments or questions?