Pre-condition/Post-condition handling. This is where quality assessment can fit. about framework HOT 2 CLOSED

Each method call in the pipeline will be surrounded by a pre-condition and post-condition. The Framework will execute the conditions to determine whether something should be executed for pre-conditions and whether it executed successfully for post-conditions.

Pre-conditions can check to see if the necessary conditions for execution have been met. If they have not been met, it can execute any commands deemed necessary and return true or false as necessary. If the conditions have been met then it returns true.

Post-conditions can check to see if the proper output was created after the command has been executed.

from framework.

Each pre- and post-condition should log the steps it took during the checks and any information relating to those steps.

For example, before the flat-fielding step is applied to reduce science, the precondition for that step must be that there is a master flat on file. If there is no master flat, that will be recorded in the log and the processing of the science file will quit to be reprocessed later when a master flat is obtained. In the naive setup, users will have to track this and trigger a reprocess command manually. However, in a more advanced mode, the post-condition of a master flat creation function can check for files that need to be reprocessed via the proc table.

Pre- and Post- conditions offer a robust way to transfer priority to other parts of the program without the need to abort the current process. They can also handle aborting the process if there is a need. In their simplest form, they can be used as gatekeepers to prevent access to a primitive/recipe.

from framework.