Summary | Channels: execute | execute2 | karajan | kickstart | info | falkon | assorted swift library routines | Other: scheduler
This plot shows the state of executions over time. When a SwiftScript program makes a procedure call, an execution will appear on this plot in START state. Over time, jobs should end up either in END_SUCCESS or END_FAILURE states. (More detail about execute events)
Number of karajan level job submissions that are 'Active' - this means that the underlying execution layer (such as GRAM) has reported that the job is actually executing - this is an approximation of the number of cores in use at once (for single threaded application code) (More detail about karajan events)
Various execution-related total-event plots on one chart:
Some execution counts:
Total executes (derivations) attempted: 14 Total execute2s (program executions) attempted: 14 execute2 / execute - average execution attempts per derivation: 1.00000000000000000000 Total kickstart records available: 1 kickstart records / execute2 = kickstart collection success rate: 7.14285714285714285714 %
List of sites used in this run:
teraport
The whole workflow (text file of event(s)) - there should be just one of them and it should take the whole span of execution time:
end