Thrifty - Cutils Command Qualifier: Difference between revisions

Thrifty - Cutils Command Qualifier (view source)

Revision as of 12:50, 15 April 2021

1,326 bytes added , 12:50, 15 April 2021

m

→‎Inner working

HansR

Bureaucrats, Administrators

1,651

edits

@@ Line 68: / Line 68: @@
 The above is the advise if you are uploading manually and make the decisions on your own. It is also important for understanding what is happening in the automatic Thrifty system. If you upload automatically everything this is being taken care of : a module is generated and uploaded only according to the above specification.
+=== Uploading Automatically ===
+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
+#Has a file been modified
+Some modules have a period in days associated with them which determines if the module is run and uploaded at all. An example is e.g. every third day for the graphs because either the user does not look at this so often of the chart does not change that much on the basis of one or two days. Default the cycles are set to one day which means the cycle condition will always be true.
+The modification of the file is being done either during the data selection (in which case the generation of the module output will be finished) or because of the algorithm in which case some of the output will not be generated. This is done by setting the ''Dirty bit''. Which is simply a flag that - if true - says : yes the output has changed since yesterday so it needs to be generated and uploaded.
+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 [[Yadr]]