jvs:fscan:manual:chapter2:setschedule
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
jvs:fscan:manual:chapter2:setschedule [2012/05/04 17:50] – voyvodic | jvs:fscan:manual:chapter2:setschedule [2012/05/04 18:05] – voyvodic | ||
---|---|---|---|
Line 14: | Line 14: | ||
Linked schedule files can be used by the [[jvs: | Linked schedule files can be used by the [[jvs: | ||
- | ==== Naming convention for schedule files ==== | + | **Naming convention for schedule files**\\ |
- | Schedule file names are not required to follow any particular naming convention, but fScan recognizes | + | Schedule file names are not required to follow any particular naming convention, but fScan recognizes |
+ | Schedule files can be organized in groups to allow the events for a task to be separated in different ways. Within a group, events should not overlap in time. Schedule groups can be specified by either a number or a single letter. | ||
+ | The 4 recognized naming conventions are:\\ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | In each case, NAME will be used as the condition name (removing " | ||
+ | If the file name is one of the forms with a group identifier (G), fScan will assume that multiple files have been organized into different analysis groups so that the task timing can be analyzed in different ways (in separate processing runs). | ||
+ | In general, it is better not to mix naming conventions for schedule files linked to the same data set as this could lead to confusion. | ||
+ | If schedule files are organized in analysis groups the group should be specified explicitly when using the '-ref schedule' | ||
**See Also:**\\ | **See Also:**\\ |
jvs/fscan/manual/chapter2/setschedule.txt · Last modified: 2024/06/21 15:44 by 127.0.0.1