Thrifty - Cutils Command Qualifier: Difference between revisions

m
Line 70: Line 70:


=== Uploading Automatically ===
=== Uploading Automatically ===
Automatic ''Thrifty'' handling assumes a daily run of ''CumulusUtils''.
The decision to automatically upload a file or not - assuming ''DoUploadFTP=true'' = is done on the basis of two parameters:
The decision to automatically upload a file or not - assuming ''DoUploadFTP=true'' = is done on the basis of two parameters:
#Have the cycle conditions become true
#Have the cycle conditions become true
Line 79: Line 80:
Examples:
Examples:
#When the [[records]] output needs to be generated, during that generation it is determined whether any records have been set at all. If no record has been set then the ''Dirty bit'' remains false. If possible the generation of the output is cancelled and the upload will not be done.
#When the [[records]] output needs to be generated, during that generation it is determined whether any records have been set at all. If no record has been set then the ''Dirty bit'' remains false. If possible the generation of the output is cancelled and the upload will not be done.
#When the [[Yadr]]
#For the [[Yadr]] module under the ''Thrifty'' condition we definitely know the past years will not have been modified so those years need not to be generated nor uploaded again. So only the current year is generated and uploaded. The menu actually only changes when a  new year is added which is done on the 2<sup>nd</sup> of January so that is the only day Yadr.txt will be  uploaded under ''Thrifty''.
 
Then at the end during uploading for each module under Thrifty condition it is checked if any of the Thrifty conditions has become true (periodic or ''Dirty bit'') and if so, the module output is uploaded.