All Classes and Interfaces
Class
Description
A job derived from a
Task that can be placed on different threadsMonitors all submitted jobs and their current state of execution.
Logs messages to the console, STDOUT.
Executes different processors depending on whether we are in debug mode or not.
Generates report of the execution-times of different operations.
An error-reporter that replaces particular errors/exceptions with user-friendly messages.
Arguments that can further specify an experiment's execution (in its entirety) in addition
to its bean specification.
Creates an instance of
ExecutionTimeRecorder depending in what outputs are enabled.A base class for a type of task that produces some kind of result of interest.
An exception that occurs when an experiment is executed.
Objects to give the user feedback about different aspects of the experiment.
A method to produce an identifier for an experiment.
Automatically populates a experiment-name and version number
Defines constants for name and version of an experiment
Writes text to a file, but only if
FailureOnlyMessageLogger.close(boolean, boolean) is called with successful==true.Context for creating initialization-parameters.
Arguments that can further specify an experiment's input in addition to its bean
specification.
Input for executing a task, associated with shared-state and other parameters.
This exists as an implementation of
InputOutputContext that exposes a StatefulMessageLogger.An experiment that uses both an
InputManager to specify inputs and a OutputManager to specify outputting.A list of base (parent) classes for input-types that a task expects.
A description of the job's name and associated number.
An exception that occurs when a job is executed.
Base class for a method to apply a task on inputs.
Logs events when jobs start and stop, with or without errors.
Monitor execution-state of a job, and how long it is taking/took to execute.
The destination(s) to which log-messages are sent.
Logs error messages into a
String via StringBuilder.Runs executes sequence of jobs/tasks/whatever monitoring various pieces of information - how many
have run? - how many successful/failed? - how long did execution take? - etc.
Logs messages to multiple other loggers.
Fake shared-state to use to indicate none exists (for type safety)
Logs messages to a particular location ONLY if debug-mode is enabled.
Arguments that can further specify an experiment's output in addition to its bean
specification.
An
Experiment that produces output files, as defined by a OutputManager.Executes jobs in parallel across cores on the system.
Parameters for executing a task, when the log etc.
Indicates and provides a mechanism that the
InputManager can be replaced.Indicates and provides a mechanism that the
OutputManager can be replaced.Indicates and provides a mechanism that the
Task can be replaced.A predicate on whether all necessary arguments exist for some purpose.
Require that debug-mode has been enabled.
Wraps a
RunningSum with an additional variable, indicating the total number of parent
operations.Executes jobs sequentially, without any parallelism.
A
MessageLogger that can be started and stopped, and is aware of this state.Does nothing (i.e.
A job that has been submitted for execution.
Switches between two log-reporters depending on whether detailed logging is switched on or not
Encapsulates some kind of processing to be performed on a set of inputs.
Arguments that can further specify an experiment's task in addition to its bean
specification.
Maintains statistics on the execution of a task (considering jobs in aggregate).
A particular type of task that doesn't share-state between running jobs
Logs messages to a text-file.
Logs messages to the console.
Rather than logging to one location, logs to multiple locations (from a list).
Logs to a text-file created in the output-directory under a particular name.
Logs messages to a text-file create in the output-directory.
Logs to a text file like with
ToTextFile but the
log is ONLY written if a failure occurs in the experiment.