tilt workflow ready to be tested by Anne

[Tilmon]

Dear @maurolepore ,

our target is to have a user friendly workflow ready until end of March. The ultimate validation of whether we achieved the target will be done through a testing by @AnneSchoenauer .

Therefore, please make sure the tilt workflow (MT part) is ready to be tested by Anne by end of March. That means the workflow should be easy enough to use for someone like @AnneSchoenauer. With "someone like Anne" I mean:

• no developer, but some R knowledge;
• by then not involved in day-to-day development anymore, i.e. sufficient documentation of what to do how required

This task is important (prio high) but not now. Therefore, I put it into the backlog for Sprint 10 as a reminder.

[maurolepore]

@Tilmon, this is precisely the goal of this package:

The goal of tiltWorkflows is to make it easy to run tilt workflows.

I believe you and @AnneSchoenauer were already successful in using this package with toy data.

What specifically would you like to change?

Please see/add issues and prioritize them.

Note I assigned this broad task to you and @AnneSchoenauer. The best tasks to assign to me would be the more granular issues that you want me to work on in order to complete these task. This approach would keep the broad task in your radar, while avoiding duplication in my board -- making everyone's work easier to see and prioritize during sprint planning.

One good way to link the granular issues to this broad one is with a task list. If you want to track the progress automatically it's important to NOT write the description of each task but instead to simply link it.

For example, this syntax

- [ ] #123
- [ ] #117

generates this task list item

• Ensure each workflow is reproducible (i.e. calls set.seed()) #123
• tilt workflow ready to be tested by Anne #117

which will automatically change color/icon to reflect the status of the linked issue.