...
- This is how much we can collect if the user does nothing.
- These steps accumulate in a folder owned by the user for steps not owned by any particular analysis. If the user wanted to associate a step at a later date with an analysis, they can do so.
- If R crashes, we don't end the step, but that's okay. This is a best effort. The next time they start R, we'll create a new step and continue on our merry way.
- We are capturing additional provenance details such as the the MD5 sum of the layer (as indicated by its Synapse version number) and the SVN revision of a Code entity, but that is not yet shown in the diagrams below.
User creates an analysis
- You can see that part way through the R session, the user decides this analysis is worth noting.
- To do, update these examples with a Synapse Code metadata object
...
User creates an analysis and saves code in SVN
- This user knows how to use SVN
User creates an analysis, saves code, and manually updates the step with more detail
Unsupervised R Session
Basically the same as above.