Changeset 18722


Ignore:
Timestamp:
01/08/17 12:05:36 (8 years ago)
Author:
tbretz
Message:
Added explanations for suspend and resume
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/FACT++/www/schedule/index.html

    r17716 r18722  
    113113
    114114    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Scheduling</H3>
    115     Note that the last entry display in red will most probably the first one
    116     executed by the scheduler. If the scheduling is running, it will just replace
    117     the next entry in the schedule and be executed completely. If the scheduler is not
     115    Note that the last entry display in red will most probably be the first one
     116    executed by the scheduler. If the scheduler (Main.js) is running, it will just replace
     117    the next entry in the schedule and be executed completely. If the scheduler (Main.js) is not
    118118    running, still the last red entry will be the first one to be executed, but since
    119119    it is the first one executed by the script, the script assumes that it failed and
    120     was restarted. Therefore, only the last of its observations (usually <I>data</I>
     120    was restarted. Therefore, only the last of its observations (usually <I>data</I>)
    121121    is executed.
     122
     123    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Suspend</H3>
     124    If a <I>suspend</I> is scheduled, all further observations are discarded. The
     125    <I>suspend</I> itself is just a <I>sleep</I>. If very soon, a new observation
     126    will be started, it is best to schedule the <I>suspend</I> before it, otherwise
     127    the observation might get started before the <I>suspend</I> is executed. Note
     128    that a suspend does <b>not</b> interrupt the current observation, but will work
     129    as a normal entry, i.e. the previous measurement (usually a <i>data</i> run) will
     130    be finished before the suspend is executed.
     131
     132    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Resume</H3>
     133    If a <I>resume</I> is scheduled, it has the same effect as if the preceeding
     134    <i>suspend</i> was removed. That effectively means that the last observation
     135    which was scheduled before the <i>resume</i> will be executed as it if just became
     136    valid. Consequently, if it is scheduled close to the change of observation,
     137    it makes sense to schedule it after this observation, to avoid that the previous
     138    observation becomes effective.
    122139
    123140    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Options</H3>
Note: See TracChangeset for help on using the changeset viewer.