sierra-research 1.3.5__py3-none-any.whl → 1.3.6__py3-none-any.whl

{sierra_research-1.3.5.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra-usage.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA-USAGE" "7" "Jun 08, 2023" "1.3.5" "SIERRA"
-.SH NAME
-sierra-usage \- How to use SIERRA. This covers all non-command line interface aspects.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,8 +27,11 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA-USAGE" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra-usage \- How to use SIERRA. This covers all non-command line interface aspects.
 .sp
-This covers everything which is (mostly) Platform independent and is not
+This covers everything which is (mostly) \fI\%Platform\fP independent and is not
 the command line interface.
 .SH SIERRA PIPELINE
 .sp
@@ -46,21 +46,21 @@ express this as a research query on the command line, and then parses your query
 to make changes to a template input file to generate launch commands and
 experimental inputs to operationalize it. Switching from targeting platform A
 (e.g., ARGoS) to platform B (e.g., ROS1+Gazebo) is as easy as changing a single
-command line argument. SIERRA handles the "backend" aspects of defining
+command line argument. SIERRA handles the \(dqbackend\(dq aspects of defining
 experimental inputs allowing you to focus on their \fIcontent\fP, rather than the
 mechanics of how to turn the content into something that can be executed. See
 also:
 .INDENT 0.0
 .IP \(bu 2
-ln\-sierra\-support\-matrix
+\fI\%SIERRA Support Matrix\fP
 .IP \(bu 2
-ln\-sierra\-usage\-cli
+\fI\%Command Line Interface\fP
 .UNINDENT
 .sp
 Part of default pipeline.
 .SS Stage 2: Experiment Execution
 .sp
-SIERRA runs a previously generated Batch Experiment\&. Exactly which batch
+SIERRA runs a previously generated \fI\%Batch Experiment\fP\&. Exactly which batch
 experiment SIERRA runs is determined by:
 .INDENT 0.0
 .IP \(bu 2
@@ -82,11 +82,11 @@ to stage 1, switching between execution environments is as easy as changing a
 single command line argument. See also:
 .INDENT 0.0
 .IP \(bu 2
-ln\-sierra\-exec\-env\-plugins
+\fI\%Execution Environment Plugins\fP
 .IP \(bu 2
-ln\-sierra\-platform\-plugins
+\fI\%Platform Plugins\fP
 .IP \(bu 2
-ln\-sierra\-support\-matrix
+\fI\%SIERRA Support Matrix\fP
 .UNINDENT
 .sp
 Part of default pipeline.
@@ -100,11 +100,11 @@ includes one or more of:
 .INDENT 0.0
 .IP \(bu 2
 Computing statistics over/about experimental data for stage 4 for use in graph
-generation in stage 4. See ln\-sierra\-usage\-cli documentation for
+generation in stage 4. See \fI\%Command Line Interface\fP documentation for
 \fB\-\-dist\-stats\fP for details.
 .IP \(bu 2
 Creating images from project CSV files for rendering in stage 4. See
-ln\-sierra\-usage\-rendering\-project for details.
+\fI\%Project Rendering\fP for details.
 .UNINDENT
 .sp
 Part of default pipeline.
@@ -128,8 +128,8 @@ SIERRA also has a rich model framework allowing you to run arbitrary models,
 generate data, and plot it on the same figure as empirical results,
 automatically. See ln\-sierra\-tutorials\-project\-models for details.
 .sp
-For some examples, see the "Generating Deliverables" section of
-\fI\%2022 AAMAS Demo\fP <\fBhttps://www-users.cse.umn.edu/~harwe006/showcase/aamas-2022-demo\fP>\&. See ln\-sierra\-usage\-rendering for details about
+For some examples, see the \(dqGenerating Deliverables\(dq section of
+\fI\%2022 AAMAS Demo\fP <\fBhttps://www-users.cse.umn.edu/~harwe006/showcase/aamas-2022-demo\fP>\&. See \fI\%Rendering\fP for details about
 rendering capabilities.
 .sp
 Part of default pipeline.
@@ -142,19 +142,19 @@ can be used to compare:
 .INDENT 0.0
 .IP \(bu 2
 Different agent control algorithms which have all been run in the same
-\fB\-\-scenario\fP\&. See ln\-sierra\-usage\-stage5\-intra\-scenario for details.
+\fB\-\-scenario\fP\&. See \fI\%Intra\-Scenario Comparison\fP for details.
 .IP \(bu 2
 A single \fB\-\-controller\fP across multiple scenarios. See
-ln\-sierra\-usage\-stage5\-inter\-scenario for details.
+\fI\%Inter\-Scenario Comparison\fP for details.
 .UNINDENT
 .sp
 Not part of default pipeline.
 .SH PIPELINE STAGE 5
 .sp
-The main idea of this pipeline stage is to "collate" the results of one or more
-Summary .csv files present in different Batch Experiments into a Inter\-Batch .csv file, and then use that file to
-generate graphs. Any Summary .csv that is present in multiple
-Batch Experiments can be used during stage 5!  This
+The main idea of this pipeline stage is to \(dqcollate\(dq the results of one or more
+\fI\%Summary .csv\fP files present in different \fI\%Batch Experiments\fP into a \fI\%Inter\-Batch .csv\fP file, and then use that file to
+generate graphs. Any \fI\%Summary .csv\fP that is present in multiple
+\fI\%Batch Experiments\fP can be used during stage 5!  This
 gives this pipeline stage tremendous flexibility as a camera\-ready graph
 generation tool.
 .sp
@@ -166,7 +166,7 @@ SIERRA invocation), because the options are quite different, but you don\(aqt
 .INDENT 0.0
 .INDENT 3.5
 You \fIcannot\fP use this stage before successfully running stage 4
-for each of the Batch Experiments you
+for each of the \fI\%Batch Experiments\fP you
 want to include on the final graph.
 .UNINDENT
 .UNINDENT
@@ -180,7 +180,7 @@ controllers in a single scenario (for example) could result in
 linegraphs containing 3,6,9,..., lines with duplicated data. In
 general, you want to delete the directories generated by stage 5
 between successive runs. See
-ln\-sierra\-usage\-runtime\-exp\-tree for details on what
+\fI\%SIERRA Runtime Directory Tree\fP for details on what
 directories are generated.
 .UNINDENT
 .UNINDENT
@@ -188,7 +188,7 @@ directories are generated.
 .sp
 Intra\-scenario comparison compares the of experiments using one or more
 controllers on the same \fB\-\-scenario\fP\&. To use it, you need to pass the
-following options to SIERRA (see ln\-sierra\-usage\-cli for documentation):
+following options to SIERRA (see \fI\%Command Line Interface\fP for documentation):
 .INDENT 0.0
 .IP \(bu 2
 \fB\-\-scenario\-comparison\fP
@@ -208,7 +208,7 @@ ln\-sierra\-tutorials\-project\-stage5\-config\-intra\&.
 .sp
 Inter\-scenario comparison compares the same \fB\-\-controller\fP across multiple
 \fB\-\-scenarios\fP\&. To use it, you need to pass the following options to SIERRA
-when running stage 5 (see ln\-sierra\-usage\-cli for documentation):
+when running stage 5 (see \fI\%Command Line Interface\fP for documentation):
 .INDENT 0.0
 .IP \(bu 2
 \fB\-\-controller\-comparison\fP
@@ -297,18 +297,18 @@ for a previously used project on subsequent runs.
 project root, which is \fBNOT\fP deleted on subsequent runs.
 .INDENT 2.0
 .IP \(bu 2
-\fBmytemplate\-SS.12x6\fP \- The directory for the Batch Experiment
+\fBmytemplate\-SS.12x6\fP \- The directory for the \fI\%Batch Experiment\fP
 is named from a combination of the template input file used
 (\fB\-\-template\-input\-file\fP) and the scenario (\fB\-\-scenario\fP).
 .INDENT 2.0
 .IP \(bu 2
-\fBexp\-inputs\fP \- Root directory for Experimental
+\fBexp\-inputs\fP \- Root directory for \fI\%Experimental\fP
 inputs; each experiment in the batch gets their own directory in here.
 .INDENT 2.0
 .IP \(bu 2
 \fBexp0\fP \- Within the input directory for each experiment in the
 batch (there are 4 such directories in this example), there will be
-an input file for each Experimental Run in the experiment,
+an input file for each \fI\%Experimental Run\fP in the experiment,
 as well as a \fBcommands.txt\fP used by GNU parallel to run them all
 in parallel. The leaf of the \fB\-\-template\-input\-file\fP, sans
 extension, has the experimental run # appended to it
@@ -401,7 +401,7 @@ during stage3 for use during stage4.
 .IP \(bu 2
 \fB\&...\fP
 .IP \(bu 2
-\fBcollated\fP \- Contains Collated .csv files. During
+\fBcollated\fP \- Contains \fI\%Collated .csv\fP files. During
 stage4, SIERRA will draw specific columns from .csv files under
 \fBstatistics\fP according to configuration, and collate them under
 here for graph generation of \fIinter\fP\-experiment graphs.
@@ -416,13 +416,13 @@ HPC clusters.
 outputs which have been converted to graphs) which can be patched
 together in stage 4 to generated videos. Each experiment will get its
 own directory under here, with unique sub\-directories for each
-different type of Experimental Run data captured for
-imagizing. See ln\-sierra\-usage\-rendering\-project for more details.
+different type of \fI\%Experimental Run\fP data captured for
+imagizing. See \fI\%Project Rendering\fP for more details.
 .IP \(bu 2
 \fBvideos\fP \- Root directory for holding rendered videos generated
 during stage 4 from either captured simulator frames for imagized
 project files. Each experiment will get its own directory under here,
-with See ln\-sierra\-usage\-rendering for more details.
+with See \fI\%Rendering\fP for more details.
 .IP \(bu 2
 \fBmodels\fP \- During stage4, the dataframes generated by all executed
 models are stored under this directory. Each experiment in the batch
@@ -467,7 +467,7 @@ First, the experiment tree for \fIscenario comparison\fP:
 \-\-scenario\-comparison\e
 \-\-batch\-criteria population_size.Log8\e
 \-\-scenarios\-list=RN.16x16x2,PL.16x16x2\e
-\-\-sierra\-root=$HOME/exp"
+\-\-sierra\-root=$HOME/exp\(dq
 .ft P
 .fi
 .UNINDENT
@@ -501,7 +501,7 @@ Second, the experiment tree for \fIcontroller comparison\fP
 \-\-controller\-comparison\e
 \-\-batch\-criteria population_size.Log8\e
 \-\-controllers\-list d0.CRW,d0.DPO\e
-\-\-sierra\-root=$HOME/exp"
+\-\-sierra\-root=$HOME/exp\(dq
 .ft P
 .fi
 .UNINDENT
@@ -531,26 +531,26 @@ depending on what you are doing.
 .INDENT 0.0
 .IP \(bu 2
 \fBparallel\fP \- GNU parallel. Used during stage 2 when running
-experiments (ARGoS, ROS1+Gazebo, ROS1+Robot platforms).
+experiments (\fI\%ARGoS\fP, \fI\%ROS1+Gazebo\fP, \fI\%ROS1+Robot\fP platforms).
 .IP \(bu 2
 \fBffmpeg\fP \- Used during stage 3 if imagizing is run. See
-ln\-sierra\-usage\-rendering\-platform\&.
+\fI\%Platform Visual Capture\fP\&.
 .IP \(bu 2
 \fBXvfb\fP \- Used during stage 1 when generating simulation inputs, and
-during stage 2 when running experiments for the ARGoS
-Platform\&. See also ln\-sierra\-usage\-rendering\-platform\&.
+during stage 2 when running experiments for the \fI\%ARGoS\fP
+\fI\%Platform\fP\&. See also \fI\%Platform Visual Capture\fP\&.
 .IP \(bu 2
 \fBparallel\-ssh\fP \- Used during stage 1 when generating experiments
-experiments (ROS1+Robot platform).
+experiments (\fI\%ROS1+Robot\fP platform).
 .IP \(bu 2
 \fBparallel\-rsync\fP \- Used during stage 1 when generating experiments
-experiments (ROS1+Robot platform).
+experiments (\fI\%ROS1+Robot\fP platform).
 .UNINDENT
 .SH ENVIRONMENT VARIABLES
 .INDENT 0.0
 .TP
 .B SIERRA_PLUGIN_PATH
-Used for locating plugins\&. The directory \fIcontaining\fP a
+Used for locating \fI\%plugins\fP\&. The directory \fIcontaining\fP a
 plugin directory outside the SIERRA source tree must be on
 \fBSIERRA_PLUGIN_PATH\fP\&. Paths are added to \fBPYTHONPATH\fP as needed to load
 plugins correctly. For example, if you have a different version of the
@@ -559,7 +559,7 @@ containing the plugin in \fB$HOME/plugins\fP, then you need to add
 \fB$HOME/plugins\fP to your \fBSIERRA_PLUGIN_PATH\fP to so that SIERRA will find
 it. This variable is used in stages 1\-5.
 .sp
-Used for locating projects; all projects specifiable with
+Used for locating \fI\%projects\fP; all projects specifiable with
 \fB\-\-project\fP are directories found within the directories on this path. For
 example, if you have a project \fB$HOME/git/projects/myproject\fP, then
 \fB$HOME/git\fP must be on \fBSIERRA_PLUGIN_PATH\fP in order for you to be able
@@ -581,9 +581,9 @@ Must be set to contain the library directory where you installed/built ARGoS,
 as well as the library directory for your project \fB\&.so\fP\&. Checked to be
 non\-empty before running stage 2 for all \fB\-\-exec\-env\fP plugins. SIERRA does
 \fInot\fP modify this variable, so it needs to be setup properly prior to
-invoking SIERRA (i.e., the directory containing the Project \fB\&.so\fP
+invoking SIERRA (i.e., the directory containing the \fI\%Project\fP \fB\&.so\fP
 file needs to be on it). SIERRA can\(aqt know, in general, where the location of
-the C++ code corresponding to the loaded Project is.
+the C++ code corresponding to the loaded \fI\%Project\fP is.
 .UNINDENT
 .INDENT 0.0
 .TP
@@ -617,7 +617,7 @@ defined and \fB\-\-nodefile\fP is not passed SIERRA will throw an error.
 .TP
 .B PARALLEL
 When running on some execution environments, such as \fBhpc.slurm,hpc.pbs\fP,
-any and all environment variables needed by your Project should be
+any and all environment variables needed by your \fI\%Project\fP should be
 exported via the \fBPARALLEL\fP environment variable before invoking SIERRA,
 because GNU parallel does not export the environment of the node it is
 launched from to slave nodes (or even on the local machine). Something like:
@@ -626,7 +626,7 @@ launched from to slave nodes (or even on the local machine). Something like:
 .sp
 .nf
 .ft C
-export PARALLEL="\-\-workdir . \e
+export PARALLEL=\(dq\-\-workdir . \e
 \-\-env PATH \e
 \-\-env LD_LIBRARY_PATH \e
 \-\-env LOADEDMODULES \e
@@ -644,19 +644,19 @@ export PARALLEL="\-\-workdir . \e
 \-\-env OMP_THREAD_LIMIT \e
 \-\-env OMP_WAIT_POLICY \e
 \-\-env SIERRA_ARCH \e
-\-\-env SIERRA_PLUGIN_PATH"
+\-\-env SIERRA_PLUGIN_PATH\(dq
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
 Don\(aqt forget to include \fI\%ARGOS_PLUGIN_PATH\fP,
-\fI\%ROS_PACKAGE_PATH\fP, etc., depending on your chosen Platform\&.
+\fI\%ROS_PACKAGE_PATH\fP, etc., depending on your chosen \fI\%Platform\fP\&.
 .UNINDENT
 .INDENT 0.0
 .TP
 .B PARALLEL_SHELL
-SIERRA sets up the Experiment execution environments by running one
+SIERRA sets up the \fI\%Experiment\fP execution environments by running one
 or more shell commands in a subprocess (treated as a \fBshell\fP, which means
 that \fBparallel\fP can\(aqt determine \fBSHELL\fP, and therefore defaults to
 \fB/bin/sh\fP, which is not what users expect. SIERRA explicitly sets
@@ -673,7 +673,7 @@ script).
 .UNINDENT
 .SH CONFIGURABLE SIERRA VARIABLES
 .sp
-Non\-Batch Criteria variables which you can use to configure
+Non\-\fI\%Batch Criteria\fP variables which you can use to configure
 simulations. All batch criteria are variables, but not all variables are batch
 criteria.
 .INDENT 0.0
@@ -682,9 +682,9 @@ criteria.
 .UNINDENT
 .SS Experiment Setup
 .sp
-Configure Experiment time: length, controller cadence (Tick
-duration/timestep), and how many datapoints to capture per Experimental
-Run\&.
+Configure \fI\%Experiment\fP time: length, controller cadence (\fI\%Tick\fP
+duration/timestep), and how many datapoints to capture per \fI\%Experimental
+Run\fP\&.
 .SS Cmdline Syntax
 .sp
 \fBT{duration}[.K{ticks_per_sec}][.N{n_datapoints}\fP
@@ -694,11 +694,11 @@ Run\&.
 .IP \(bu 2
 \fBticks_per_sec\fP \- How many times each controller will be run per second.
 .IP \(bu 2
-\fBn_datapoints\fP \- # datapoints per Experimental Run to be captured;
+\fBn_datapoints\fP \- # datapoints per \fI\%Experimental Run\fP to be captured;
 the capture interval (if configurable) should be adjusted in
-Project\-derived class from the platform "Experiment setup class"
+\fI\%Project\fP\-derived class from the platform \(dqExperiment setup class\(dq
 (e.g., \fBsierra.plugins.platform.argos.variables.exp_setup.ExpSetup\fP for
-ARGoS).
+\fI\%ARGoS\fP).
 .UNINDENT
 .SS Examples
 .INDENT 0.0

{sierra_research-1.3.5.data → sierra_research-1.3.6.data}/data/share/man/man7/sierra.7

@@ -1,8 +1,5 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SIERRA" "7" "Jun 08, 2023" "1.3.5" "SIERRA"
-.SH NAME
-sierra \- reSearch pIpEline for Reproducability, Reusability, and Automation.
 .
 .nr rst2man-indent-level 0
 .
@@ -30,9 +27,12 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 ..
+.TH "SIERRA" "7" "Apr 01, 2024" "1.3.6" "SIERRA"
+.SH NAME
+sierra \- reSearch pIpEline for Reproducability, Reusability, and Automation.
 .SH SYNOPSIS
 .sp
-This the "main menu" of the SIERRA reference manual, which captures most, but
+This the \(dqmain menu\(dq of the SIERRA reference manual, which captures most, but
 not all of its documentation. For the full experience, look at the online docs
 at \fI\%https://sierra.readthedocs.io/en/master\fP\&.
 .SH COMPONENTS
@@ -65,7 +65,7 @@ execution before proceeding to the next step. SIERRA should rarely crash with a
 cryptic interpreter error message/exception, but if it does, please report it so
 I can fix it and/or create a better error message.
 .sp
-Errors should be reported to \fI\%https://github.com:jharwell/sierra.git\fP\&.
+Errors should be reported to \fI\%https://github.com/jharwell/sierra\fP\&.
 .SH RETURN VALUE
 .sp
 SIERRA will always return 0, unless it crashes with an exception or a failed

{sierra_research-1.3.5.dist-info → sierra_research-1.3.6.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: sierra-research
-Version: 1.3.5
+Version: 1.3.6
 Summary: Automation framework for the scientific method in AI research
 Home-page: https://github.com/jharwell/sierra
 Author: John Harwell
@@ -35,7 +35,7 @@ Requires-Dist: coloredlogs
 Requires-Dist: implements
 Requires-Dist: retry
 Provides-Extra: devel
-Requires-Dist: pylint (==2.14.5) ; extra == 'devel'
+Requires-Dist: pylint ==2.14.5 ; extra == 'devel'
 Requires-Dist: pytype ; extra == 'devel'
 Requires-Dist: pydocstyle ; extra == 'devel'
 Requires-Dist: xenon ; extra == 'devel'
@@ -52,8 +52,8 @@ Requires-Dist: mypy-runner ; extra == 'devel'
 Requires-Dist: build ; extra == 'devel'
 Requires-Dist: twine ; extra == 'devel'
 Requires-Dist: setuptools ; extra == 'devel'
-Requires-Dist: sphinx (==4.4.0) ; extra == 'devel'
-Requires-Dist: docutils (==0.16) ; extra == 'devel'
+Requires-Dist: sphinx ==5.0.2 ; extra == 'devel'
+Requires-Dist: docutils ==0.18.1 ; extra == 'devel'
 Requires-Dist: sphinx-rtd-theme ; extra == 'devel'
 Requires-Dist: sphinx-argparse ; extra == 'devel'
 Requires-Dist: sphinx-tabs ; extra == 'devel'
@@ -75,8 +75,8 @@ SIERRA (reSearch pIpEline for Reproducibility, Reusability, and Automation)
 .. |supported-pythons| image:: https://img.shields.io/pypi/pyversions/sierra-research.svg
                        :target: https://pypi.python.org/pypi/sierra-research/
 
-.. |linux-supported| image:: https://svgshare.com/i/Zhy.svg
-.. |osx-supported| image:: https://svgshare.com/i/ZjP.svg
+.. |linux-supported| image:: https://img.shields.io/badge/os-Linux-crimson
+.. |osx-supported| image:: https://img.shields.io/badge/os-OSX-crimson
 
 .. |ci-integration-master| image:: https://github.com/jharwell/sierra/actions/workflows/integration-all.yml/badge.svg?branch=master
 .. |ci-analysis-master| image:: https://github.com/jharwell/sierra/actions/workflows/static-analysis.yml/badge.svg?branch=master

{sierra_research-1.3.5.dist-info → sierra_research-1.3.6.dist-info}/RECORD

@@ -1,9 +1,9 @@
 sierra/__init__.py,sha256=LrL9-6GqsT0Lvo6jb54x4m-DL1NywTXG8JKSrYis7Xo,186
 sierra/main.py,sha256=K46LsG16cSqTMfNiT3vSSF3SLh5BjAUPVqPjZ6A2Oxs,6618
-sierra/version.py,sha256=AbRCxPY1PXun3NLlT2T9qZMwI6IDu3bMujuHNw9h38U,243
+sierra/version.py,sha256=1DltYoYdHXaHmjq1Ls8zc6SRe9FsSFUWsC4fE8J1yI8,243
 sierra/core/__init__.py,sha256=IwACyV8LoLuIx3TBzC6WdcRTq9D-0GO7nguLxY64QbI,188
 sierra/core/cmdline.py,sha256=j9eAStCFolUyzvUSzqeRE1BNgtxDTgaYqDiaTTYFUBQ,58191
-sierra/core/config.py,sha256=IGekEo5htDNi-d9JTZwVtfOOYA4LcCvGPeUrIenuz1s,4557
+sierra/core/config.py,sha256=zezJgparLsD4HtgfzPvlxmwBX-6X3Ntdq2kkMlxvFQs,4562
 sierra/core/logging.py,sha256=jq_bryJDLeMfzsRsWkDpQI20HvOJqd3b14Ank9a-1DI,985
 sierra/core/platform.py,sha256=jOlm4PVPNp9EPjtckaYR66t5p6A4fQwBxmjZoFCHz-o,17359
 sierra/core/plugin.py,sha256=Bc4n1_Q5VvorAsbwt76K6cZmSrU-f0m2tNyQSWXYsOE,3500
@@ -13,7 +13,7 @@ sierra/core/startup.py,sha256=raE4kgNarzcDIDlgw2cHFenH3_qJJehEq4kBCE4Rnpk,5422
 sierra/core/stat_kernels.py,sha256=wBTWEXw2XvdSfxghNlhUbKkn1XjgTP7_d0OBM6lUvWE,6030
 sierra/core/storage.py,sha256=VJ5IqNM_grOMYH5vq6bI5EO4muySERaj4TI-Ngzny6w,1300
 sierra/core/types.py,sha256=R5gW2u9nBPHJJ7HdliFzq999SwvWgYzPGX0tlyWAiWQ,2049
-sierra/core/utils.py,sha256=TOlAupVdD9KRYIkv3IjUcb4hO6WLOV5zzsQbnjN74bU,12471
+sierra/core/utils.py,sha256=KsgUnsG7npKGnkYkcIQqnD_vAmRcrdfnMiU4rcGCn1s,12464
 sierra/core/vector.py,sha256=wVCoOU7rS7hYpmiOElh0RAF6xlKRuDr7fBD13ykpkys,3843
 sierra/core/experiment/__init__.py,sha256=6b7RQQobZUX1hRmfmq_bZ3KovuTKeBYNLWwEG_axTxQ,145
 sierra/core/experiment/bindings.py,sha256=6BSg3Li5D1ZWRxxPSXJYZ8TQlGwIfQupxbLSceTs7Pg,10152
@@ -118,16 +118,16 @@ sierra/plugins/robot/turtlebot3/plugin.py,sha256=r7TSnboGUI5cCqT_ty1X9KVJ770pMcP
 sierra/plugins/storage/__init__.py,sha256=6b7RQQobZUX1hRmfmq_bZ3KovuTKeBYNLWwEG_axTxQ,145
 sierra/plugins/storage/csv/__init__.py,sha256=6b7RQQobZUX1hRmfmq_bZ3KovuTKeBYNLWwEG_axTxQ,145
 sierra/plugins/storage/csv/plugin.py,sha256=EnFIAmeEpAcVUlbuGG3I3sdb9AVO5zg4k2pa2C1dLFM,938
-sierra_research-1.3.5.data/data/share/man/man1/sierra-cli.1,sha256=2475tBsi018sW70tehlYaBeSgQmhWn571-UVbz6fvrc,54227
-sierra_research-1.3.5.data/data/share/man/man7/sierra-examples.7,sha256=0nNm-vUOL7nuoxaehLkUoFq-c3ormAfY7hhi_VxsLLQ,17940
-sierra_research-1.3.5.data/data/share/man/man7/sierra-exec-envs.7,sha256=-YUevZd6jzD5JjfTtP3xL-dYPKDlUtvJyQdkZgvLsa4,7796
-sierra_research-1.3.5.data/data/share/man/man7/sierra-glossary.7,sha256=YT8uVfBe2jFMi_AhkxqPqQuyyRJo_RFzbnZoW65cyUs,10921
-sierra_research-1.3.5.data/data/share/man/man7/sierra-platforms.7,sha256=bBhSY1tVvMRvoJYb-yMt41PsnpD-BC_dkg4AblxGqg0,13596
-sierra_research-1.3.5.data/data/share/man/man7/sierra-usage.7,sha256=bvZuHWBrKY6nGbedGljnHaDv1ALh1S6L7bKAePQ_xnQ,24455
-sierra_research-1.3.5.data/data/share/man/man7/sierra.7,sha256=ir4cGjIzMKvvOFhTq32r2KhJIcr5woPhcN0QYLi3JyE,2476
-sierra_research-1.3.5.dist-info/LICENSE,sha256=syQ7e-OEgTREA-x8XbHp8x4CIj7LR1-_cwicIfKGWcg,1052
-sierra_research-1.3.5.dist-info/METADATA,sha256=sGoxhPq1f2TbZpt0TaQ-bo3fWGREG7RXLQKYO_IUqKs,16890
-sierra_research-1.3.5.dist-info/WHEEL,sha256=pkctZYzUS4AYVn6dJ-7367OJZivF2e8RA9b_ZBjif18,92
-sierra_research-1.3.5.dist-info/entry_points.txt,sha256=3FhShoQcDSf17edEyA6qcO1YwGrZ5kuayu2iVG5npXY,48
-sierra_research-1.3.5.dist-info/top_level.txt,sha256=cDP7dDWAyFL7fK11L89hCUHy9-G267wuHeVLVR4pTX4,7
-sierra_research-1.3.5.dist-info/RECORD,,
+sierra_research-1.3.6.data/data/share/man/man1/sierra-cli.1,sha256=xs9CghWYI3w29zeeCk5aBcth0omqLyB50UqULPb7vLY,54484
+sierra_research-1.3.6.data/data/share/man/man7/sierra-examples.7,sha256=4bqHRleirUTfjregCbaic_JzASrndk12MRlIuN3htaQ,17969
+sierra_research-1.3.6.data/data/share/man/man7/sierra-exec-envs.7,sha256=9NzoKY9hptKREts3pZgq0fCJqrLW6CK1QcowRN_ey-c,7789
+sierra_research-1.3.6.data/data/share/man/man7/sierra-glossary.7,sha256=hsiqUZADQSQS9Dig4n_pP_wC8ibH3_1AqO0c8F8aGFM,10868
+sierra_research-1.3.6.data/data/share/man/man7/sierra-platforms.7,sha256=yFoLDBl99G_aRD71PYLew5uwglh6FjXSfw-wQ4sv1Ww,13871
+sierra_research-1.3.6.data/data/share/man/man7/sierra-usage.7,sha256=cUkiTlpDxuLjIcM5QJfR39iX08AGdom8MmJmcqPEOTk,24725
+sierra_research-1.3.6.data/data/share/man/man7/sierra.7,sha256=sci8lek0-vEbDRce8ZagtMY9pIbU1wUdudD0xiYvqQM,2478
+sierra_research-1.3.6.dist-info/LICENSE,sha256=syQ7e-OEgTREA-x8XbHp8x4CIj7LR1-_cwicIfKGWcg,1052
+sierra_research-1.3.6.dist-info/METADATA,sha256=ll2CYzxeFw68RKYke_H_JjnV_9WSnRzmbUATn6M_c9A,16914
+sierra_research-1.3.6.dist-info/WHEEL,sha256=GJ7t_kWBFywbagK5eo9IoUwLW6oyOeTKmQ-9iHFVNxQ,92
+sierra_research-1.3.6.dist-info/entry_points.txt,sha256=3FhShoQcDSf17edEyA6qcO1YwGrZ5kuayu2iVG5npXY,48
+sierra_research-1.3.6.dist-info/top_level.txt,sha256=cDP7dDWAyFL7fK11L89hCUHy9-G267wuHeVLVR4pTX4,7
+sierra_research-1.3.6.dist-info/RECORD,,

{sierra_research-1.3.5.dist-info → sierra_research-1.3.6.dist-info}/WHEEL

@@ -1,5 +1,5 @@
 Wheel-Version: 1.0
-Generator: bdist_wheel (0.40.0)
+Generator: bdist_wheel (0.43.0)
 Root-Is-Purelib: true
 Tag: py3-none-any