Clarify the 'assim move' model #6871
Description
In the course of developing Autodock and BUDA job-processing systems for BOINC Central, I've created a new framework for handling output files. Now I need to
- Document it in the wiki
- Give it a name, and change file and function names accordingly.
An app can be 'stream-oriented' or 'batch-oriented'. A project can have a mix.
If an app is stream-oriented, its output files live in the upload hierarchy.
Its assimilator marks WUs and results as FILE_DELETE_READY.
The 'file_deleter' deletes the files.
If an app is batch-oriented, there are two options:
'assim-stay': the assimilator leaves the files in the upload hierarchy,
When the batch is retired, its WUS and results are marked as FILE_DELETE_READY.
file_deleter deletes the files.
'assim-move': the assimilator moves the files of the canonical result to
a directory project/results/batchid.
Web interfaces allow the user to view or download these files,
either individually or as a zipped group.
When the batch is retired, the directory is deleted.
The file project/html/project/remote_apps.inc has a list of descriptors for batch-oriented apps; it says which option each one uses.
The assimilators tools/sample_assimilate.py and sched/sample_assimilator.cpp both implement the assim-move model; they should be renamed accordingly.
Files like submit_util.inc have utility functions for things like getting output file paths. These assume only model or the other, and should be named accordingly.