Packages

p

auth.datalab.siesta

CommandLineParser

package CommandLineParser

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. All

Type Members

  1. case class Config(system: String = "siesta", database: String = "s3", mode: String = "positions", filename: String = "synthetic", log_name: String = "synthetic", compression: String = "snappy", delete_all: Boolean = false, delete_previous: Boolean = false, lookback_days: Int = 30, traces: Int = 100, event_types: Int = 10, length_min: Int = 10, length_max: Int = 90, k: Int = -1, duration_determination: Boolean = false, declare_incremental: Boolean = false) extends Product with Serializable

    This class is the configuration object that is initialized in auth.datalab.siesta.siesta_main from the command arguments.

    This class is the configuration object that is initialized in auth.datalab.siesta.siesta_main from the command arguments. It holds the following information

    system

    What system will be used for indexing (Signature, Set-Containment, SIESTA or online SIESTA)

    database

    In what database the data will be stored. Note that for Signature and Set-Containment only Cassandra is available. Therefore only for SIESTA both options are available.

    mode

    This parameter is specific for siesta and determines whether the timestamps or positions of the event type pairs will be stored in IndexTable

    filename

    The path to the logfile that will be indexed

    log_name

    The name of the log database. Since multiple log databases can be available (similar to SQL). The same name must be given if this is an incremental indexing, in order to append the log in the correct tables.

    compression

    The compression algorithm that will be used while storing the indices in the database.

    delete_all

    Flag parameter determines if all the previous tables in the database (despite the log database name) will be deleted.

    delete_previous

    Flag parameter determines if the previous tables of this particular log database will be deleted.

    lookback_days

    Numeric parameter, determines the maximum distance (in days) between two events in order to create an event pair. That is if two events' timestamp have difference larger than this parameter they will be not stored in IndexTable.

    traces

    This parameter concerns the random generator. Defines the number of traces that will be random generated.

    event_types

    This parameter concerns the random generator. Defines the number of event types that will be contained in the traces.

    length_min

    This parameter concerns the random generator. Defines the minimum length of the generated traces.

    length_max

    This parameter concerns the random generator. Defines the maximum length of the generated traces.

    k

    Specifies the number of frequent events that will be used in the Signature method. If -1 is set it will use k=|unique event types|

    duration_determination

    Flag parameter determines if the duration of the events will be calculated and stored in.

    See also

    ParsingArguments, which describes how the parameters are parsed from the command line and what are the available values for each parameter.

Value Members

  1. object ParsingArguments

    This class is responsible to parse the parameters from the command line and generate the configuration object.

    This class is responsible to parse the parameters from the command line and generate the configuration object. This object will be passed in the different pipelines and control their flow.

    In case of new functionality it should start from here. Run the preprocess with "--help" to get the full list of available parameters and their use.

    See also

    Config, which describes the parameters parsed here.

Ungrouped