<commit_before>========
Glossary
========

.. _glossary-terms:

.. glossary::
   :sorted:

   Abstract Workflow
   DAX
      The workflow input in YAML format given to Pegasus in which
      transformations and files are represented as logical names. It is an
      execution-independent specification of computations. The abstract
      workflow can optionally include catalog descriptions that tell
      Pegasus the location of the files (Replica Catalog), executables
      (Transformation Catalog) and the sites (Site Catalog).

   Concrete Workflow
   Executable Workflow
      The output workflow generated by Pegasus in which files are
      represented by physical filenames, transformations are represented by
      paths to executables, and sites or hosts have been selected
      for running each task. By default, Pegasus generates an executable
      workflow represented as a HTCondor DAGMan workflow.

   Compute Site
      The logical handle of the computational resource in the Site Catalog
      on which the executable workflow is executed by Pegasus.

   Clustering
      The process of grouping short running jobs together into a larger
      job. This is done to minimize the scheduling overhead for the jobs.
      The scheduling overhead is only incurred for the clustered job. For
      example if scheduling overhead is x seconds and 10 jobs are clustered
      into a larger job, the scheduling overhead for 10 jobs will be x
      instead of 10x.

   Directed Acyclic Graph (DAG)
      A graph in which all the arcs (connections) are unidirectional,linear,
      and without loops (cycles).

   Deferred Planning
      Planning mode to set up Pegasus. In this mode, instead of mapping the
      job at submit time, the decision of mapping a job to a site is
      deferred until a later point, i.e. when the job is about to be run.
      Deferred planning only applies to pegasusWorkflow jobs in the
      hierarchical workflows, where these jobs refer to another abstract
      workflow to be executed.

   Full Ahead Planning
      Planning mode to set up Pegasus. In this mode, all the jobs are
      mapped before submitting the workflow for execution to the underlying
      execution resources..

   Globus
      The Globus Alliance is a community of organizations and individuals
      developing fundamental technologies behind the "Grid," which lets
      people share computing power, databases, instruments, and other
      on-line tools securely across corporate, institutional, and
      geographic boundaries without sacrificing local autonomy.

      See Globus Toolkit

   Globus Toolkit
      Globus Toolkit is an open source software toolkit used for building
      Grid systems and applications.

   GRAM
      A Globus service that enables users to locate, submit, monitor and
      cancel remote jobs on Grid-based compute resources. It provides a
      single protocol for communicating with different batch/cluster job
      schedulers.

   Grid
      A collection of many compute resources , each under different
      administrative domains connected via a network (usually the
      Internet).

   GridFTP
      A high-performance, secure, reliable data transfer protocol optimized
      for high-bandwidth wide-area networks. It is based upon the Internet
      FTP protocol, and uses basic Grid security on both control (command)
      and data channels.

   Hierarchical Workflow
      A abstract workflow where some jobs in the
      workflow, instead of referring to compute jobs, point to another workflow
      that needs to be executed. Hierarchical workflows are one way for users
      to compose very large workflows that end up containing hundreds of
      thousands of tasks across all the sub workflows.

   HTCondor DAGMan
      The workflow execution engine used by Pegasus to manage the execution
      of the executable workflow.

   HTCondor-G
      A task broker that manages jobs to run at various distributed sites,
      using Globus GRAM to launch jobs on the remote
      sites. More information can be found at
      `HTCondor Website <https://research.cs.wisc.edu/htcondor>`_

   Input Site
      The logical handle to the storage resource described in the Site Catalog,
      where input data required by a workflow resides.

   Kickstart
      A lightweight C executable that Pegasus uses to launch user executables to
      gather m

   Logical File Name (LFN)<commit_msg>PM-1575 minor in the glossary, fixed the kickstart entry<commit_after>========
Glossary
========

.. _glossary-terms:

.. glossary::
   :sorted:

   Abstract Workflow (formerly known as DAX, prior to 5.0 version)
      The workflow input in YAML format given to Pegasus in which
      transformations and files are represented as logical names. It is an
      execution-independent specification of computations. The abstract
      workflow can optionally include catalog descriptions that tell
      Pegasus the location of the files (Replica Catalog), executables
      (Transformation Catalog) and the sites (Site Catalog).

   Concrete Workflow or Executable Workflow
      The output workflow generated by Pegasus in which files are
      represented by physical filenames, transformations are represented by
      paths to executables, and sites or hosts have been selected
      for running each task. By default, Pegasus generates an executable
      workflow represented as a HTCondor DAGMan workflow.

   Compute Site
      The logical handle of the computational resource in the Site Catalog
      on which the executable workflow is executed by Pegasus.

   Clustering
      The process of grouping short running jobs together into a larger
      job. This is done to minimize the scheduling overhead for the jobs.
      The scheduling overhead is only incurred for the clustered job. For
      example if scheduling overhead is x seconds and 10 jobs are clustered
      into a larger job, the scheduling overhead for 10 jobs will be x
      instead of 10x.

   Directed Acyclic Graph (DAG)
      A graph in which all the arcs (connections) are unidirectional,linear,
      and without loops (cycles).

   Deferred Planning
      Planning mode to set up Pegasus. In this mode, instead of mapping the
      job at submit time, the decision of mapping a job to a site is
      deferred until a later point, i.e. when the job is about to be run.
      Deferred planning only applies to pegasusWorkflow jobs in the
      hierarchical workflows, where these jobs refer to another abstract
      workflow to be executed.

   Full Ahead Planning
      Planning mode to set up Pegasus. In this mode, all the jobs are
      mapped before submitting the workflow for execution to the underlying
      execution resources.

   Globus
      The Globus Alliance is a community of organizations and individuals
      developing fundamental technologies behind the "Grid," which lets
      people share computing power, databases, instruments, and other
      on-line tools securely across corporate, institutional, and
      geographic boundaries without sacrificing local autonomy.

      See Globus Toolkit

   Globus Toolkit
      Globus Toolkit is an open source software toolkit used for building
      Grid systems and applications.

   GRAM
      A Globus service that enables users to locate, submit, monitor and
      cancel remote jobs on Grid-based compute resources. It provides a
      single protocol for communicating with different batch/cluster job
      schedulers.

   Grid
      A collection of many compute resources , each under different
      administrative domains connected via a network (usually the
      Internet).

   GridFTP
      A high-performance, secure, reliable data transfer protocol optimized
      for high-bandwidth wide-area networks. It is based upon the Internet
      FTP protocol, and uses basic Grid security on both control (command)
      and data channels.

   Hierarchical Workflow
      A abstract workflow where some jobs in the
      workflow, instead of referring to compute jobs, point to another workflow
      that needs to be executed. Hierarchical workflows are one way for users
      to compose very large workflows that end up containing hundreds of
      thousands of tasks across all the sub workflows.

   HTCondor DAGMan
      The workflow execution engine used by Pegasus to manage the execution
      of the executable workflow.

   HTCondor-G
      A task broker that manages jobs to run at various distributed sites,
      using Globus GRAM to launch jobs on the remote
      sites. More information can be found at
      `HTCondor Website <https://research.cs.wisc.edu/htcondor>`_

   Input Site
      The logical handle to the storage resource described in the Site Catalog,
      where input data required by a workflow resides.

   Kickstart
      A lightweight C executable that Pegasus uses to launch user executables to
      gather metrics about the execution of each job.

   Logical File Name (LFN)
{'fraction_non_alphanumeric': 0.02878016382554793, 'fraction_numerical': 0.0019924728802302415, 'mean_word_length': 3.031682284694333, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5305273', 'n_tokens_mistral': 2218, 'n_tokens_neox': 2043, 'n_words': 1201}