Upload 49 files

VenusLibraryDocumentation-DocsForGPT/.gitignore

@@ -0,0 +1,156 @@
+
+# Created by https://www.toptal.com/developers/gitignore/api/python,jupyternotebooks
+# Edit at https://www.toptal.com/developers/gitignore?templates=python,jupyternotebooks
+
+### JupyterNotebooks ###
+# gitignore template for Jupyter Notebooks
+# website: http://jupyter.org/
+
+.ipynb_checkpoints
+*/.ipynb_checkpoints/*
+
+# IPython
+profile_default/
+ipython_config.py
+
+# Remove previous ipynb_checkpoints
+#   git rm -r .ipynb_checkpoints/
+
+### Python ###
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+
+# IPython
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# End of https://www.toptal.com/developers/gitignore/api/python,jupyternotebooks

VenusLibraryDocumentation-DocsForGPT/.readthedocs.yaml

@@ -0,0 +1,17 @@
+version: "2"
+
+build:
+  os: "ubuntu-22.04"
+  tools:
+    python: "3.10"
+
+python:
+  install:
+    - requirements: docs/requirements.txt
+
+sphinx:
+  configuration: docs/source/conf.py
+
+formats:
+  - pdf
+  - epub

VenusLibraryDocumentation-DocsForGPT/README.rst

@@ -0,0 +1,4 @@
+Venus Library Documentation
+=======================================
+
+Venus is a coding language wrapper used in the programming of devices such as the Hamilton Microlab STAR. This is unofficial documentation for it and it's libraries, compiled from official sources and personal troubleshooting. If any issues or mistakes are found, please message me and let me know.

VenusLibraryDocumentation-DocsForGPT/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = source
+BUILDDIR      = build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

VenusLibraryDocumentation-DocsForGPT/docs/make.bat

@@ -0,0 +1,35 @@
+@ECHO OFF
+
+pushd %~dp0
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+	set SPHINXBUILD=sphinx-build
+)
+set SOURCEDIR=source
+set BUILDDIR=build
+
+if "%1" == "" goto help
+
+%SPHINXBUILD% >NUL 2>NUL
+if errorlevel 9009 (
+	echo.
+	echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
+	echo.installed, then set the SPHINXBUILD environment variable to point
+	echo.to the full path of the 'sphinx-build' executable. Alternatively you
+	echo.may add the Sphinx directory to PATH.
+	echo.
+	echo.If you don't have Sphinx installed, grab it from
+	echo.http://sphinx-doc.org/
+	exit /b 1
+)
+
+%SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+goto end
+
+:help
+%SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% %O%
+
+:end
+popd

VenusLibraryDocumentation-DocsForGPT/docs/requirements.txt

@@ -0,0 +1,2 @@
+sphinx==7.1.2
+sphinx-rtd-theme==1.3.0rc1

VenusLibraryDocumentation-DocsForGPT/docs/source/ASWGlobal.rst

@@ -0,0 +1,18 @@
+ASWGlobal
+============================================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ASWGlobal.pkg
+
+The ASWGlobal library doesn't add any functions, but instead declares common HSL constants  used in other libraries, SMTs, and methods. These are often used as the return values for functions. The constants it declares are:
+
+  - False, No, and Off are all assigned as being hslFalse
+  - True, Yes, and On are all assigned as being hslTrue
+  - For dialogue buttons, each one is assigned a specific number: 
+      - Ok = 1
+      - Cancel = 2
+      - Abort = 3
+      - Retry = 4
+      - Ignore = 5
+      - Yes = 6
+      - No = 7
+  - Clicking STOP on a timer is assigned as being 3

VenusLibraryDocumentation-DocsForGPT/docs/source/Aliquot_for_EasySteps_v2.txt

@@ -0,0 +1,50 @@
+Aliquot for Easy Steps v2
+=================================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Aliquot_for_EasySteps_v2.pkg
+
+This library adds two functions aimed at making aliquoting steps easier. The functions added are:
+
+  - :ven:func:`CalcAliquot_v2_1`
+  - :ven:func:`CalcChannelPattern`
+
+.. ven:function:: CalcAliquot_v2_1(sequence DispenseSequence, variable VolumePerWell, variable VolumePreAliquote, variable VolumePostAliquote, variable MaxVolumeTip, variable NumberOfDispense, variable NumberOfChannels, variable intNumberOfChannelsInstalled, array arrVolumeToAspirateByChannel, array arrVolumeToMixBeforeAspiration, array arrChannelPatternDispense, variable strChannelPatternAspirate)
+
+  This function calculates the important variables for performing an aliquote pipetting with Easy- or Single Steps
+
+  :params DispenseSequence: The sequence for the aliquots to be dispensed into
+  :params VolumePerWell: The volume of the aliquotes per well
+  :params VolumePreAliquote: The volume of the pre-aliquote
+  :params VolumePostAliquote: The volume of the post-aliquote
+  :params MaxVolumeTip: The maximum volume of the selected CO-RE Tip
+  :params NumberOfDispense: The number of dispense steps per aspiration
+  :params NumberOfChannels: The number of the channels to use for the process
+  :params intNumberOfChannelsInstalled: The number of channels installed in the system
+  :params arrVolumeToAspirateByChannel: An output of the array of volumes to aspirate by channel
+  :params arrVolumeToMixBeforeAspiration: An output of the array of volumes to mix before aspiration (typically used during the first aspiration only)
+  :params arrChannelPatternDispense: The output array of channel patterns for the dispense
+  :params strChannelPatternAspirate: An output string of the channel pattern to aspirate
+  :type DispenseSequence: Sequence
+  :type VolumePerWell: Variable 
+  :type VolumePreAliquote: Variable
+  :type VolumePostAliquote: Variable
+  :type MaxVolumeTip: Variable
+  :type NumberOfDispense: Variable
+  :type NumberOfChannels: Variable
+  :type intNumberOfChannelsInstalled: Variable
+  :type arrVolumeToAspirateByChannel: Array
+  :type arrVolumeToMixBeforeAspiration: Array
+  :type arrChannelPatternDispense: Array
+  :type strChannelPatternAspirate: String
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: CalcChannelPattern(variable i_int_NumberOfPositions, variable i_int_NumberOfInstalledChannels, variable o_str_ChannelPattern)
+
+  This function creats a channel pattern based on the number of desired positions and the number of installed channels.
+
+  :params i_int_NumberOfPositions: The number of positions to use, which must be less than or equal to the Number of Installed Channels
+  :params i_int_NumberOfInstalledChannels: The number of channels installed on the instrument
+  :params o_str_ChannelPattern: The output channel pattern as a string  
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/Aliquot_with_EasySteps.rst

@@ -0,0 +1,33 @@
+Aliquot with Easy Steps
+==========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Aliquot_for_EasySteps.pkg
+
+The Aliquot with Easy Steps library adds one function aimed at making aliquoting with Easy- or Single steps easier. This library is outdated, the Aliquot_for_EasySteps_v2 library should be used instead. The function it adds is:
+
+- :ven:func:`CalcAliquote`
+
+.. ven:function:: CalcAliquote(sequence DispenseSequence, variable VolumePerWell, variable VolumePreAliquote, variable VolumePostAliquote, variable MaxVolumeTip, variable VolumeToAspirate, variable NumberOfDispense, variable FullTrace, variable NumberOfChannels)
+
+  This function calculates the important variables for performing aliquoting with Easy- or Single steps.
+
+  :params DispenseSequence: The sequence for the aliquots to be dispensed into
+  :params VolumePerWell: The volume of the aliquots per well
+  :params VolumePreAliquote: The volume of the pre-aliquot
+  :params VolumePostAliquote: The volume of the post-aliquot
+  :params MaxVolumeTip: The maximum volume of the selected CO-RE Tip
+  :params VolumeToAspirate: The volume which has to be aspirated
+  :params NumberOfDispense: The number of dispense steps per aspiration
+  :params FullTrace: The detail level of the trace (1 is full, 0 is normal)
+  :params NumberOfChannels: The number of channels installed on the system
+  :type DispenseSequence: Sequence
+  :type VolumePerWell: Variable
+  :type VolumePreAliquote: Variable
+  :type VolumePostAliquote: Variable
+  :type MaxVolumeTip: Variable
+  :type VolumeToAspirate: Variable
+  :type NumberOfDispenses: Variable
+  :type FullTrace: Boolean
+  :type NumberOfChannels: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/AlphaNumericConversion.rst

@@ -0,0 +1,63 @@
+Alpha Numeric Conversion
+=============================================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/AlphaNumericConversion.pkg
+
+This library adds four functions related to converting plate positions to their integer equivalents and vice versa. The functions it adds are:
+
+- :ven:func:`Alpha_Num_Add_0_to_Position`
+- :ven:func:`Alpha_Num_Remove_0_from_Position`
+- :ven:func:`Convert_Alpha_Numeric_to_Numbers`
+- :ven:func:`Convert_Numbers_to_Alpha_Numeric`
+
+.. ven:function:: Alpha_Num_Add_0_to_Position(variable io_Str_Position_ID)
+
+  This function takes a single position and adds the 0 between the letter and number if it needs one. Example would be A1 -> A01, B1 -> B01. Position variable must be a string.
+
+  :params io_Str_Position_ID: The alphanumeric position that the 0 needs to be added to.
+  :type io_Str_Position_ID: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Alpha_Num_Remove_0_from_Position(variable io_Str_Position_ID)
+
+  This function takes a single position and removes the 0 if there is one. Example would be A01 -> A1, B01 -> B1. Position variable must be a string.
+
+  :params io_Str_Position_ID: The alphanumeric position that the 0 needs to be removed from.
+  :type io_Str_Position_ID: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Convert_Alpha_Numeric_to_Numbers(variable i_Sort_by_Column, variable i_Alpha_Numeric_Value, variable i_Total_Rows, variable i_Total_Columns, variable o_Numeric_Value)
+
+  This function takes an alpha numeric value and returns the integer that corresponds to that position number. If a 1 is entered for "i_Sort_by_Column", the submethod will sort by columns, i.e. A1 -> 1, B1 -> 2, etc. If a 0 is entered, it will sort by rows, i.e. A1 -> 1, A2 -> 2.
+
+  :params i_Sort_by_Column: Whether the positions will be sorted by row (0) or by column (1)
+  :params i_Alpha_Numeric_Value: The alpha numeric value to be converted
+  :params i_Total_Rows: The total number of rows in the target labware, between 1 and 26.
+  :params i_Total_Columns: The total number of columns in the target labware, betweem 1 and 99.
+  :params o_Numeric_Value: The output converted position
+  :type i_Sort_by_Column: Boolean
+  :type i_Alpha_Numeric_Value: Variable  
+  :type i_Total_Rows: Variable
+  :type i_Total_Columns: Variable
+  :type o_Numeric_Value: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Convert_Numbers_to_Alpha_Numeric(variable i_Sort_by_Column, variable i_Numeric_Value, variable i_Total_Rows, variable i_Total_Columns, variable o_Alpha_Numeric_Value)
+
+  This function takes an integer value and returns the corresponding alpha numeric position. If a 1 is entered for "i_Sort_by_Column", the submethod will sort by columns, i.e. 1 -> A1, 2 -> B1, etc. If a 0 is entered, it will sort by rows, i.e. 1 -> A1, 2 -> A2.
+
+  :params i_Sort_by_Column: Whether the positions will be sorted by row (0) or by column (1)
+  :params i_Numeric_Value: The numeric value to be converted
+  :params i_Total_Rows: The total number of rows in the target labware, between 1 and 26.
+  :params i_Total_Columns: The total number of columns in the target labware, between 1 and 99.
+  :params o_Alpha_Numeric_Value: The output converted position
+  :type i_Sort_by_Column: Boolean
+  :type i_Numeric_Value: Variable
+  :type i_Total_Rows: Variable
+  :type i_Total_Columns: Variable
+  :type o_Alpha_Numeric_Value: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/Array.txt

@@ -0,0 +1,213 @@
+Array (from HSLExtensions)
+=========================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Array.pkg
+
+The array library from HSLExtensions adds functions to help manipulate 1-D arrays. The following functions are added:
+
+- :ven:func:`Append`
+- :ven:func:`CompareArrays`
+- :ven:func:`Concat`
+- :ven:func:`ContainsDuplicates`
+- :ven:func:`ContainsValue`
+- :ven:func:`ConvertToBooleanArray`
+- :ven:func:`ConvertToFloatArray`
+- :ven:func:`ConvertToIntegerArray`
+- :ven:func:`ConvertToStringArray`
+- :ven:func:`Copy`
+- :ven:func:`FindValue`
+- :ven:func:`InitializeAllValues`
+- :ven:func:`IsBooleanArray`
+- :ven:func:`IsEmpty`
+- :ven:func:`IsFloatArray`
+- :ven:func:`IsIntegerArray`
+- :ven:func:`IsStringArray`
+- :ven:func:`Sort`
+
+.. ven:function:: Append(array io_arrValuesA, array i_arrValuesB)
+
+  This function updates the array io_arrValuesA to add all the values from i_arrValuesB at the end of the array.
+
+  :params io_arrValuesA: The array to which the values will be added 
+  :params i_arrValuesB: The array from which the values will be added
+  :type io_arrValuesA: Array
+  :type i_arrValuesB: Array
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: CompareArrays(array i_arrExpectedValues, array i_arrActualValues, array o_arrMissingValues, array o_arrNotExpectedValues)
+
+  This function compares two arrays and outputs arrays of values which are missing from the first array but present in the second, and values which are present in the second array but not in the first.
+
+  :params i_arrExpectedValues: The first array, which the second array will be checked against, usually is the array of expected values
+  :params i_arrActualValues: The second array, which will use the first array as a template when comparing against, usually is your "actual" array
+  :params o_arrMissingValues: An output array of values which are present in the first array but not the second 
+  :params o_arrNotExpectedValues: An output array of values which are present in the second array but not the first (i.e. unexpected values in your actual data)
+  :type i_arrExpectedValues: Array
+  :type i_arrActualValues: Array
+  :type o_arrMissingValues: Array
+  :type o_arrNotExpectedValues: Array
+  :return: True if both arrays contain the same values (resulting in empty output arrays), false if arrays don't contain the same values (in which case the output arrays will have data in them)
+  :rtype: Boolean
+
+.. ven:function:: Concat(array i_arrValuesA, array i_arrValuesB)
+
+  This function appends one array to the other and then returns the concatenated array. The difference between this and the :ven:func:`Append` function is that the Append function updates an existing array, whereas this function doesn't change the existing arrays and instead returns a new array.
+
+  :params i_arrValuesA: The array to which the values will be added
+  :params i_arrValuesB: The array from which the values will be added
+  :type i_arrValuesA: Array
+  :type i_arrValuesB: Array
+  :return: A new array which is the concatenated version of the input arrays
+  :rtype: Array
+
+.. ven:function:: ContainsDuplicates(array i_arrValues)
+
+  This function checks whether the input array has multiple of the same value in it
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: An array with all values which appear more than once in the input array
+  :rtype: Array
+
+.. ven:function:: ContainsValue(array i_arrValues, variable i_varValue)
+
+  This function determines whether a value exists in an array without returning its index
+
+  :params i_arrValues: The array to be searched
+  :params i_varValue: The value to be searched for
+  :type i_arrValues: Array
+  :type i_varValue: Variable
+  :return: True if the value is present, false otherwise
+  :rtype: Boolean
+
+.. ven:function:: ConvertToBooleanArray(array i_arrValues, variable o_blnSuccessfullyConverted)
+
+  This function converts the input array to an array with boolean values. If it is not possible to convert one or more values of the input array, the output will be false and the output array will be empty. Cannot interact with strings, will convert a non-zero int or float into a 1, and will turn a 0 float into a 0.
+
+  :params i_arrValues: The array to be converted
+  :params o_blnSuccessfullyConverted: A boolean which tells you whether the conversion was successful or not
+  :type i_arrValues: Array
+  :type o_blnSuccessfullyConverted: Boolean
+  :return: The boolean version of the input array
+  :rtype: Array
+
+.. ven:function:: ConvertToFloatArray(array i_arrValues, variable o_blnSuccessfullyConverted)
+
+  This function converts the input array to an array with float values. If it is not possible to convert one or more values of the input array, the output will be false and the output array will be empty. Cannot interact with strings, will convert any int into a float. 
+
+  :params i_arrValues: The array to be converted
+  :params o_blnSuccessfullyConverted: A boolean which tells you whether the conversion was successful or not
+  :type i_arrValues: Array
+  :type o_blnSuccessfullyConverted: Boolean
+  :return: The float version of the input array
+  :rtype: Array
+
+.. ven:function:: ConvertToIntArray(array i_arrValues, variable o_blnSuccessfullyConverted)
+
+  This function converts the input array to one with integer values. If it is not possible to convert one or more values of the input array, the output will be false and the output array will be empty. Cannot interact with strings, will round any floats to the nearest integer.
+
+  :params i_arrValues: The array to be converted
+  :params o_blnSuccessfullyConverted: A boolean which tells you whether the conversion was successful or not
+  :type i_arrValues: Array
+  :type o_blnSuccessfullyConverted: Boolean
+  :return: The integer version of the input array
+  :rtype: Array
+
+.. ven:function:: ConvertToStringArray(array i_arrValues)
+
+  This function converts the input array to one with string values. 
+
+  :params i_arrValues: The array to be converted
+  :type i_arrValues: Array
+  :return: The float version of the input array
+  :rtype: Array
+
+.. ven:function:: Copy(array i_arrValues)
+
+  This function will output an exact copy of the input array. 
+
+  :params i_arrValues: The array to be copied
+  :type i_arrValues: Array
+  :return: A copy of the input array
+  :rtype: Array
+
+.. ven:function:: FindValue(array i_arrValues, variable i_varValue)
+
+  This function will lookup the input variable within the input array and return a 1-based array of the indices of all positions that the input variable was found.
+
+  :params i_arrValues: The array to be searched
+  :params i_varValue: The variable to be searched for
+  :type i_arrValues: Array
+  :type i_varValue: Variable
+  :return: An array of all the locations that the input variable was found
+  :rtype: Array
+
+.. ven:function:: InitializeAllValues(array io_arrValues, variable i_varValue)
+
+  This function sets all values within an array to the input variable. Does not work on empty arrays. 
+
+  :params io_arrValues: The array in which all values will be converted. 
+  :params i_varValue: The variable to which all values will be converted.
+  :type io_arrValues: Array
+  :type i_varValue: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: IsBooleanArray(array i_arrValues)
+
+  This function checks whether all values in the array are booleans.
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: A boolean of whether the input array is all booleans or not
+  :rtype: Boolean
+
+.. ven:function:: IsEmpty(array i_arrValues)
+
+  This function checks whether the input array is empty
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: A boolean of whether the input array is empty or not
+  :rtype: Boolean
+
+.. ven:function:: IsFloatArray(array i_arrValues)
+
+  This function checks whether all values in the array are floats.
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: A boolean of whether the input array is all floats or not
+  :rtype: Boolean
+
+.. ven:function:: IsIntegerArray(array i_arrValues)
+
+  This function checks whether all values in the array are integers.
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: A boolean of whether the input array is all integers or not
+  :rtype: Boolean
+
+.. ven:function:: IsStringArray(array i_arrValues)
+
+  This function checks whether all values in the array are strings.
+
+  :params i_arrValues: The array to be checked
+  :type i_arrValues: Array
+  :return: A boolean of whether the input array is all strings or not
+  :rtype: Boolean
+
+.. ven:function:: Sort(array i_arrValues, variable i_intSortMode, o_bSuccessfulSorted)
+
+  This function outputs a sorted version of the array using the Shakersort sorting algorithm. All values in the array must share the same type for this function to work. Sort mode can either be 1 or 2, 1 is ascending and 2 is descending. 
+
+  :params i_arrValues: The array containing the values to be sorted  
+  :params i_intSortMode: Whether the array is to be sorted in ascending (1) or descending (2) order
+  :params o_bSuccesfulSorted: A boolean of whether the sort was successful or not
+  :type i_arrValues: Array
+  :type i_intSortMode: Variable
+  :type o_bSuccesfulSorted: Boolean
+  :return: A sorted copy of the array
+  :rtype: Array

VenusLibraryDocumentation-DocsForGPT/docs/source/ArrayTools.rst

@@ -0,0 +1,154 @@
+ArrayTools
+====================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ArrayTools.pkg
+
+The ArrayTools library provides the following functions:
+
+- :ven:func:`ArraySeqVLookup`
+- :ven:func:`ArrayVLookup`
+- :ven:func:`ConvertArrayOfNumericIntegersToString`
+- :ven:func:`ConvertArrayOfNumericStringsToInteger`
+- :ven:func:`Lookup`
+- :ven:func:`Sort3ArraysByNumericAscendingOrder`
+- :ven:func:`Update_Value_in_Array`
+- :ven:func:`get_distinct_from_array`
+- :ven:func:`mergeArrays`
+- :ven:func:`removeValueFromArray_basedOnIndex`
+
+.. ven:function:: ArraySeqVLookup(array i_arraySequencesA, array i_arrayValuesB, variable i_varCondition, array o_arraySequencesC)
+
+  Given 2 arrays  A (Sequences) and B (Values) with same size
+  Retrieve all the sequences in A where B = input value
+  A(seq1, seq2, seq3,seq4,seq5, seq6, ...)
+  B(1, 2, 3, 1, 2, 3, ...)
+
+  Get from A all elements where B = 1
+  C(seq1, seq4, ...)
+
+  :param i_arraySequencesA: The input array of sequences to filter
+  :param i_arrayValuesB: The input array of variables to act as a filter
+  :param i_varCondition: The input value of the variable which is to be selected
+  :param o_arraySequencesC: The output array of the sequences whose index matches the indices in which the the value of the variable is equal to the filter
+  :type i_arraySequencesA: Array of sequences
+  :type i_arrayValuesB: Array of variables
+  :type i_varCondition: Variable
+  :type o_arraySequencesC: Array of sequences
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: ArrayVLookup(array i_arrayValuesA, array i_arrayValuesB, variable i_varCondition, array o_arrayValuesC)
+
+  Given 2 arrays of values A and B with same size
+  Retrieve all the elements in B where A = input value
+
+  A(100, 20, 15, 45, 42, 1, ...)
+  B(1, 2, 3, 1, 2, 3, ...)
+
+  Get from A all elements where B = 1
+  C(100, 15, ...)
+
+  :param i_arrayValuesA: The input array of variables to filter
+  :param i_arrayValuesB: The input array of variables to act as a filter
+  :param i_varCondition: The input value of the variable which is to be selected
+  :param o_arrayValuesC: The output array of the variables whose index matches the indices in which the value of the variable is equal to the filter
+  :type i_arrayValuesA: Array of variables
+  :type i_arrayValuesB: Array of variables
+  :type i_varCondition: Variable
+  :type o_arrayValuesC: Array of variables
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: ConvertArrayOfNumericIntegersToString(array i_arr1_int, array o_arr1_str)
+
+  Converts all the numeric integers within an array to strings.
+
+  :param i_arr1_int: The input array containing the integers to be converted
+  :param o_arr1_str: The output array containing the strings
+  :type i_arr1_int: Array of variables
+  :type o_arr1_str: Array of variables
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: ConvertArrayOfNumericStringsToIntegers(array i_arr1_str, array o_arr1_int)
+
+  Converts all the numeric strings within an array to integers.
+
+  :param i_arr1_str: The input array containing the strings to be converted
+  :param o_arr1_int: The output array containing the integers
+  :type i_arr1_str: Array of variables
+  :type o_arr1_int: Array of variables
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Lookup(array array, variable item)
+
+  Looks up a value within an array, outputting a 1-based index of the value if found in the array, and a 0 if the value isn't found.
+
+  :param array: The input array to be searched
+  :param item: The variable to be searched for
+  :type array: Array
+  :type item: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Sort3ArraysByNumericAscendingOrder(array io_array1, array io_array2, array io_array3)
+
+  Sorts 3 arrays by numeric ascending order. io_array1 must contain only numeric values; this one will be sorted and then the other arrays will update to match the new order of io_array1.
+
+  :param io_array1: The first of the arrays to be sorted, which must contain only numeric values.
+  :param io_array2: The second of the arrays to be sorted, which can contain any values.
+  :param io_array3: The third of the arrays to be sorted, which can contain any values.
+  :type io_array1: Array
+  :type io_array2: Array
+  :type io_array3: Array
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Update_Value_in_Array(array i_array, variable i_value, variable i_index)
+
+  Overwrites a value in the array at a specified index.
+
+  :param i_array: The array in which the value will be changed.
+  :param i_value: The new value to be inserted into the array.
+  :param i_index: The 1-based index of the position in the array to be overwritten.
+  :type i_array: Array
+  :type i_value: Variable
+  :type i_index: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: get_distinct_from_array(array i_arr, array o_arr)
+
+  Gets all the values in an array that only appear once.
+
+  :param i_arr: The input array to be searched.
+  :param o_arr: The new output array containing the values which only appear once.
+  :type i_arr: Array
+  :type i_arr: Array
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: mergeArrays(array array1, array array2, array array3)
+
+  Concatenates two arrays and outputs the result into a third array.
+
+  :param array1: The first array of interest.
+  :param array2: The second array of interest.
+  :param array3: The resulting array of values.
+  :type array1: Array
+  :type array2: Array
+  :type array3: Array
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: removeValueFromArray_basedOnIndex(array i_array_elements, variable i_index_to_remove)
+
+  Removes a value from an array at the specified index.
+
+  :param i_array_elements: The array from which an item is to be removed.
+  :param i_index_to_remove: The 1-based index of the array from which the item is to be removed.
+  :type i_array_elements: Array
+  :type i_index_to_remove: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/CheckCarrierPresence_V2.rst

@@ -0,0 +1,34 @@
+Check Carrier Presence v2
+=======================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/CheckCarrierPresence.pkg
+
+This library adds functions which allow you to check whether one or more carriers are loaded on the deck. It requires the sensor at each carrier position to be present and functional. The functions it adds are:
+
+  - :ven:func:`CheckCarrierPresenceByArrOfLabIDs`
+  - :ven:func:`CheckCarrierPresenceByLabID`
+
+.. ven:function:: CheckCarrierPresenceByArrOfLabIDs(variable iInstrument, array iArrLabIDs, array oArrLabIDsNotLoaded)
+
+  This function checks whether several carriers are loaded on the deck. This is done by checking if the sensor at each carrier is giving a signal. It will output an array of all the not-loaded carriers, as well as returning a boolean to say whether all carriers are loaded (0) or at least one carrier is not loaded properly (1)
+
+  :params iInstrument: The instrument present, must be ML_STAR
+  :params iArrLabIDs: The input array of the Lab IDs for the carriers being checked
+  :params oArrLabIDsNotLoaded: The output array of the Lab IDs of any carriers which are not loaded. Empty if every Lab ID is loaded.
+  :type iInstrument: Variable
+  :type iArrLabIDs: Array
+  :type oArrLabIDsNotLoaded: Array
+  :return: Boolean of whether all carriers are loaded correctly (0) or at least one carrier is not loaded correctly (1)
+  :rtype: Boolean
+
+.. ven:function:: CheckCarrierPresenceByLabID(variable iInstrument, variable iLabIDOfCarrier)
+
+  This function checks whether a carrier is loaded on the deck. This is done by checking if the sensor at the carrier is giving a signal. It will return a boolean to say whether the carrier is not loaded (0) or loaded (1). 
+
+  :params iInstrument: The instrument present, must be ML_STAR
+  :params iLabIDOfCarrier: The labware ID of the carrier being checked
+  :type iInstrument: Variable
+  :type iLabIDOfCarrier: variable  
+  :return: A boolean determining whether the carrier is loaded (0) or not loaded (1)
+  :rtype: Boolean
+

VenusLibraryDocumentation-DocsForGPT/docs/source/ColourSchemeLibrary.rst

@@ -0,0 +1,17 @@
+ColourSchemeLibrary
+=============================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ColourSchemeLibrary.pkg
+
+The ColourSchemeLibrary allows the user to change the colour scheme of the Hamilton standard dialogues. It adds the following function
+
+- :ven:func:`Assign`
+
+.. ven:function:: Assign(variable i_str_ColorSchemeCode)
+
+  This function updates the colour scheme of the Standard Dialogues that will be used in the method where the library is executed. Requires HSLExtensions(File), HSLExtensions(Directory), and ASW Global.
+
+  :params i_str_ColorSchemeCode: The input color scheme code which is the int KitProviderCode. Hamilton = 0.
+  :type i_str_ColorSchemeCode: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/ConvertFileToASCII.rst

@@ -0,0 +1,17 @@
+Convert File To ASCII
+=========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ConvertFileToASCII.pkg
+
+The Convert File to ASCII library adds the ability to convert Hamilton files to ASCII files. The function it adds is:
+
+  - :ven:func:`ConvertFileToASCII`
+
+.. ven:function:: ConvertFileToASCII(variable i_Str_SourceFile)
+
+  This function converts files from binary to ASCII. The file must be a Hamilton file.
+
+  :params i_Str_SourceFile: The path to the file which is being converted.
+  :type i_Str_SourceFile: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/DataManagerInterface - unfinished.rst

@@ -0,0 +1,52 @@
+Data Manager Interface - unfinished
+=============================
+
+Data Manager Interface provides the following functions: 
+
+- ven:func:`AddColumn`
+- ven:func:`AddTable`
+- ven:func:`DeleteRows`
+- ven:func:`ExecuteAggregateFunction`
+- ven:func:`ExecuteSelectAllLineByLineCommand`
+- ven:func:`ExecuteSelectCommand`
+- ven:func:`ExportColumnsToCSVFile`
+- ven:func:`ExportColumnsToExcelFile`
+- ven:func:`ExportColumnsToXMLFile`
+- ven:func:`ExportSelectedToCSVFile`
+- ven:func:`ExportSelectedToExcelFile`
+- ven:func:`ExportSelectedToXMLFile`
+- ven:func:`ExportToCSVFile`
+- ven:func:`ExportToExcelFile`
+- ven:func:`ExportToXMLFile`
+- ven:func:`GetRowCount`
+- ven:func:`GetSelectCommandRow`
+- ven:func:`ImportFromCSVFile`
+- ven:func:`ImportFromExcelFile`
+- ven:func:`ImportFromXMLFile`
+- ven:func:`Init`
+- ven:func:`InsertRow`
+- ven:func:`InsertSortedRow`
+- ven:func:`LoadDataManagerContent`
+- ven:func:`RemoveColumn`
+- ven:func:`RemoveTable`
+- ven:func:`RenameColumn`
+- ven:func:`ResetManager`
+- ven:func:`SaveDataManagerContent`
+- ven:func:`Terminate`
+- ven:func:`UpdateRows`
+
+.. ven:function:: AddColumn(variable i_strTableName, variable i_strColumnName, variable i_iColumnType, variable i_bAllowDBNull, variable i_oValue)
+
+This function adds a column to the specified table.
+
+:params i_strTableName: The name of the table
+:params i_strColumnName: The name of the column to be added
+:params i_iColumnType: The type of column as an integer (
+
+INPUT:
+i_strTableName : name of the table (string)
+i_strColumnName : name of the column (string)
+i_iColumnType : type of the column (int) (see enum DATAMANAGERINTERFACEBASE::VALUTYPE)
+                               String = 1, Integer = 2, Double = 3, Boolean = 4
+i_bAllowDBNull : set whether null is allowed for the columns (bool)
+i_oValue : value which shall bes set to all row values of the new column (object, regarding to 'i_iColumnType')

VenusLibraryDocumentation-DocsForGPT/docs/source/DebugAssist.rst

@@ -0,0 +1,19 @@
+DebugAssist
+============================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/DebugAssist.pkg 
+
+The debug assist library adds one function aimed at helping the user identify, understand, and fix runtime errors. The function it adds is:
+
+- :ven:func:`FullErrorAnalysis`
+
+This function can use the `ASWStandardDialog library <https://github.com/theonetruenerd/VenusPackages/blob/main/ASWStandardDialogs.pkg>`_ which makes the dialog nicer, but is not a requirement.
+
+.. ven:function:: FullErrorAnalysis(variable i_PathForErrorDataAnalysis)
+
+  This function is designed to be called in the "OnAbort" submethod. It will look at the error that caused the abort to be triggered, convert the trace file error code into the more standard form, identify what that error corresponds with and hopefully suggest some initial things to check. In order for the dialogue to pop up, this function requires ASWStandardDialogues to be initialised.
+
+  :params i_PathForErrorDataAnalysis: A file path for where the error data will be exported. Currently not very important as the main bonus of the library is the dialogue that pops up, although the intention is to add more detail to this exported file.
+  :type i_PathForErrorDataAnalysis: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/Directory_Unfinished.rst

@@ -0,0 +1,21 @@
+Directory (from HSLExtensions) - unfinished
+=================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Directory.pkg
+
+The directory library from HSLExtensions adds functions which help interact with directories, files, and subdirectories. The following functions are added: 
+
+- :ven:func:`Copy`
+- :ven:func:`Create`
+- :ven:func:`Delete`
+- :ven:func:`Exists`
+- :ven:func:`GetDirectoryInformation`
+- :ven:func:`GetFileCount`
+- :ven:func:`GetFileNames`
+- :ven:func:`GetNewestFileName`
+- :ven:func:`GetOldestFileName`
+- :ven:func:`GetSubdirectories`
+- :ven:func:`Move`
+- :ven:func:`Rename`
+
+.. ven:function:: Copy(string i_strDirectoryNameSource, string i_strDirectorynameTarget, variable i_bOverwriteExisting)

VenusLibraryDocumentation-DocsForGPT/docs/source/EditFileAttributes.rst

@@ -0,0 +1,47 @@
+EditFileAttributes
+===============================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/EditFileAttributes.pkg
+
+The Edit File Attributes library adds the following functions: 
+
+- :ven:func:`Make_Hidden`
+- :ven:func:`Make_ReadOnly`
+- :ven:func:`Remove_Hidden`
+- :ven:func:`Remove_ReadOnly`
+
+.. ven:function:: Make_Hidden(variable Filename)
+
+  Applies the hidden attribute to the file found at the path specified.
+
+  :params filename: The path to the file that is going to be modified.
+  :type filename: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Make_ReadOnly(variable Filename)
+
+  Applies the read only attribute to the file found at the path specified.
+
+  :params filename: The path to the file that is going to be modified.
+  :type filename: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Remove_Hidden(variable Filename)
+
+  Removes the hidden attribute from the file found at the path specified.
+
+  :params filename: The path to the file that is going to be modified.
+  :type filename: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Remove_ReadOnly(variable Filename)
+
+  Removes the read only attribute from the file found at the path specified.
+
+  :params filename: The path to the file that is going to be modified.
+  :type filename: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/ErrorCodes.rst

@@ -0,0 +1,9 @@
+Error Codes & Debugging
+===========================
+
+I will try compile as many different error codes and their explanations here, as well as potential causes and solutions to deal with them as and when they pop up. If there are any you wish to add, please message me on my discord "theonetruenerd" or email me at "tarunchapman@hotmail.com". Notably, the error codes that show up in the trace look slightly different to the ones presented here. If the trace error code looks like this: (0x12 - 0x3 - 0x45) [which corresponds to (MinorID - MajorID - SpecificErrorID)], then the translated error code will look like this: 0xa3120045. The error code should always be 10 digits long, with zeroes padding the bit between the 2 and 45. 
+
+The Major ID is usually assigned in the library which is causing the error; for example in HSLUtilLib2 there is a function called "Error" in which there is a static const variable called MajorID. The minor ID corresponds to the general type of error; in HSLUtilLib2 "0x01" is used to refer to a general runtime error.
+
+  - :ref:`Runtime Errors <RuntimeErrors>`
+  - :ref:`Syntax Errors <SyntaxErrors>`

VenusLibraryDocumentation-DocsForGPT/docs/source/ErrorReportLibrary.rst

@@ -0,0 +1,45 @@
+Error Report Library
+===================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ErrorReportLibrary.pkg
+
+The error report library generates concise reports on both general errors and pipetting errors that occur during a run, extracting the information from the trace file. It adds the following functions:
+
+- :ven:func:`CopyActiveTraceFile`
+- :ven:func:`GenerateGeneralErrorsReport`
+- :ven:func:`GeneratePipettingErrorsReport`
+
+.. ven:function:: CopyActiveTraceFile(variable o_strTraceCopyFilePath)
+
+  Finds the trace file that is currently active (i.e. associated with the current run) and makes a copy of it, which it saves in the location specified.
+
+  :params o_strTraceCopyFilePath: The location that the copy of the trace file will be created in
+  :type o_strTraceCopyFilePath: Variable
+  :return: None 
+  :rtype: N/A
+
+.. ven:function:: GenerateGeneralErrorsReport(variable i_strTraceFilePath, variable o_strPDF_FilePath)
+
+  Reads the active trace file, locates errors found within it and generates an error report on errors found in non-pipetting steps
+
+  :params i_strTraceFilePath: The path to the current trace file 
+  :params o_strPDF_FilePath: The file path for the exported PDF of the error report
+  :type i_strTraceFilePath: Variable
+  :type o_strPDF_FilePath: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: GeneratePipettingErrorsReport(variable i_strTraceFilePath, variable i_strTemplateFilePath, variable i_intWriteRowStart, o_strPDF_FilePath)
+
+  Reads the active trace file, locates errors in the pipetting steps within it and generates an error report for the pipetting steps only
+
+  :params i_strTraceFilePath: The path to the current trace file
+  :params i_strTemplateFilePath: The path to the excel file used as a template for generating the report; should be installed when the library is unpacked
+  :params i_intWriteRowStart: Which row of the excel file to begin the report on; usually two, can be more than two
+  :params o_strPDF_FilePath: The file path for the exported PDF of the error report
+  :type i_strTraceFilePath: Variable
+  :type i_strTemplateFilePath: Variable
+  :type i_intWriteRowStart: Variable
+  :type o_strPDF_FilePath: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/ErrorSimulator.rst

@@ -0,0 +1,190 @@
+Error Simulator
+======================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ErrorSimulator.pkg
+
+This library adds the ability to simulate a variety of errors, to assist with debugging or custom error handling. The functions it adds are:
+
+  - :ven:func:`AA_Abstract`
+  - :ven:func:`STEP1_PrepareRegistryAndCfgFile`
+  - :ven:func:`STEP2a_SimulateError_Channels`
+  - :ven:func:`STEP2b_SimulateError_COREGripper`
+  - :ven:func:`STEP2c_SimulateError_iSWAP`
+  - :ven:func:`STEP2d_SimulateError_96Head`
+  - :ven:func:`STEP2e_SimulateError_384Head`
+  - :ven:func:`STEP2f_SimulateError_BarcodeReading`
+  - :ven:func:`STEP2g_SimulateError_Autoload`
+  - :ven:func:`STEP2h_SimulateError_CRWashstation`
+  - :ven:func:`STEP3_Restore_BackupCfgFile`
+  - :ven:func:`STEP4_Optional_SwitchChecksum_ON`
+
+.. ven:function:: AA_Abstract()
+
+  This function does nothing. In the submethod library itself it simply lists the changelog.
+
+.. ven:function:: STEP1_PrepareRegistryAndCfgFile(device ML_STAR)
+
+  This function prepares the system files and registry to perform the error simulation. You can put this step at the beginning of your method, and you can disable it after the 1st run, once all registry and configuration settings are done. It switches off the checksum in the registry, asking for confirmation to modify the registry during run. It converts the \Config\ML_STAR_Simulator.cfg file to ASCII. It creates a copy of ML_STAR_Simulator.cfg named ML_STAR_Simulator.cfg.bak for future restoration if needed. It replaces the string reload "0" with reload "1".
+
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type ML_STAR: Device  
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2a_SimulateError_Channels(variable ChannelNumber, variable WhenSimulateError, variable ErrorToSimulate, device ML_STAR)
+
+  This function simulates an error in the channels. It can simulate an error of your choice (between errors 1 and 12) in a desired channel at any step of the pipetting process. The error codes are: 
+  - 1....... Liquid Level not found  (error 06/70)
+  - 2.......  Not enough liquid  (error 06/71)
+  - 3....... Liquid level not found with Dual LLD ( error 06/73)
+  - 4....... Clot error (error 04/81)
+  - 5....... Liquid not correctly aspirated (error 06/80)
+  - 6.......Tip already present (error 07/00)
+  - 7....... No Tip (error 08/00)
+  - 8....... Wrong tip type detected (error 08/78)
+  - 9....... Syntax / parameter out of range (error 01/00)
+  - 10....... Hardware (error 02/00)  
+  - 11....... Not Executed (error 03/00)
+  - 12....... Not Completed (error 10/00)
+
+  :params ChannelNumber: A string of the channel(s) in which the error is to be simulated, e.g. "1,2,4,7"
+  :params WhenSimulateError: The step of the process in which the error is desired to be simulated. 1 = Aspiration, 2 = Dispense, 3 = Tip pickup, 4 = Tip eject
+  :params ErrorToSimulate: Integer corresponding to the desired simulated error, key listed in function description.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type ChannelNumber: Variable
+  :type WhenSimulateError: Variable
+  :type ErrorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2b_SimulateError_COREGripper(variable ChannelNumber, variable WhenSimulateError, variable ErrorToSimulate, device ML_STAR)
+
+  This function simulates an error in the CO-RE gripper. It can simulate an error of your choice (between errors 1 and 4) in a desired channel at any step of the process. The error codes are:
+  - 1....... Can´t get the CORE grippers  (error 08/75)
+  - 2....... Step lost in Z drive, crash against something (error 02/62)
+  - 3....... Hardware (error 02/00)
+  - 4....... Read Barcode Error (05/00)
+
+  :params ChannelNumber: A string of the channel(s) in which the error is to be simulated, e.g. "1,2,4,7"
+  :params WhenSimulateError: The step of the process in which the error is desired to be simulated. 1 = Pickup CO-RE, 2 = Get Plate, 3 = Put Plate, 4 = Eject CO-RE gripper
+  :params ErrorToSimulate: Integer corresponding to the desired simulated error, key listed in function description.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type ChannelNumber: Variable
+  :type WhenSimulateError: Variable
+  :type ErrorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2c_SimulateError_iSWAP(variable WhenSimulateError, variable ErrorToSimulate, device ML_STAR)
+
+  This function simulates an error in the iSWAP. It can simulate an error of your choice (between errors 1 and 4) at any step of the process. The error codes are:
+  - 1...... Expected object not found (error 21/94)
+  - 2...... Step lost in Z drive, crash against something (error 02/62)
+  - 3...... Hardware (error 02/00)
+  - 4...... Object lost (error 23/96)
+
+  :params WhenSimulateError: The step of the process in which the error is desired to be simulated. 1 = Get Plate, 2 = Put Plate
+  :params ErrorToSimulate: Integer corresponding to the desired simulated error, key listed in function description.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type WhenSimulateError: Variable
+  :type ErrorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2d_SimulateError_96Head(variable WhenSimulateError, variable ErrorToSimulate, device ML_STAR)
+
+  This function simulates an error in the 96-head. It can simulate an error of your choice (between errors 1 and 12 - not all available) at any step of the process. The error codes are:
+  - 1....... Liquid Level not found  (error 06/70)
+  - 2....... Not enough liquid  (error 06/71)
+  - 6....... Tip already present (error 07/00)
+  - 7....... No Tip (error 08/00)
+  - 8....... Wrong tip type detected (error 08/78)
+  - 9....... Syntax / parameter out of range (error 01/00)
+  - 10...... Hardware (error 02/00)  
+  - 11...... Not Executed (error 03/00)
+  - 12...... Not Completed (error 10/00)
+
+  :params WhenSimulateError: The step of the process in which the error is desired to be simulated. 1 = Aspiration, 2 = Dispense, 3 = Tip Pickup, 4 = Tip eject, 5 = Wash
+  :params ErrorToSimulate: Integer corresponding to the desired simulated error, key listed in function description.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type WhenSimulateError: Variable
+  :type ErrorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2e_SimulateError_384head(variable WhenSimulateError, variable ErrorToSimulate, device ML_STAR)
+
+  This function simulates an error in the 384-head. It can simulate an error of your choice (between errors 1 and 12 - not all available) at any step of the process. The error codes are:
+  - 1....... Liquid Level not found  (error 06/70)
+  - 2....... Not enough liquid  (error 06/71)
+  - 6....... Tip already present (error 07/00)
+  - 7....... No Tip (error 08/00)
+  - 8....... Wrong tip type detected (error 08/78)
+  - 9....... Syntax / parameter out of range (error 01/00)
+  - 10...... Hardware (error 02/00)  
+  - 11...... Not Executed (error 03/00)
+  - 12...... Not Completed (error 10/00)
+
+  :params WhenSimulateError: The step of the process in which desired error is to be simulated. 1 = Aspiration, 2 = Dispense, 3 = Tip Pickup, 4 = Tip eject, 5 = Wash.
+  :params ErrorToSimulate: Integer corresponding to the desired simulated error, key listed in function definition.
+  :params ML_STAR: The instrument being used. Should be ML_STAR
+  :type WhenSimulatedError: Variable
+  :type ErrorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2f_SimulateError_BarcodeReading(variable WhenSimulateError, device ML_STAR)
+
+  This function simulates an error during the barcode reading step. It can simulate the error as though it was either the CO-RE grips or the iSWAP involved.
+
+  :params WhenSimulateError: Poorly labelled variable, likely copied and pasted. This is not when the error is simulated; it is instead whether the barcode is being read with CO-RE grips (1) or the iSWAP (2)
+  :param ML_STAR: The instrument being used. Should be ML_STAR
+  :type WhenSimulateError: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP2g_SimulateError_Autoload(variable notReadPosition_Str, variable notPresentPosition_Str, device ML_STAR)
+
+  This submethod simulates the "Barcode not read"  and "Labware not Present Errors".you can enter positions with errors separated by a comma
+
+  :params notReadPosition_Str: A string of comma separated values with the positions in which you want to simulate barcode errors
+  :params notPresentPosition_Str: A string of comma separated values with the positions in which you want to simulate labware not present errors.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type notReadPosition_Str: Variable
+  :type notPresentPosition_Str: Variable
+  :type ML_STAR: Device
+  :return: None  
+  :rtype: N/A
+
+.. ven:function:: STEP2h_SimulateError_CRWashstation(variable errorToSimulate, device ML_STAR)
+
+  This function simulates an error when starting the washing with the CR washstation
+
+  :params errorToSimulate: The error being simulated. 1 = Not washing liquid error, 2 = hardware error.
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type errorToSimulate: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP3_Restore_BackupCfgFile(device ML_STAR)
+
+  This function restores the backup configuration file created in function STEP1_PrepareRegistryAndCfgFile
+
+  :params ML_STAR: The instrument being used. Should be ML_STAR.
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: STEP4_Optional_SwitchChecksum_ON()
+
+  This function is optional.  Use it at the end of your method if you want to Switch the File Checksum ON in the registry
+
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/Framework.txt

@@ -0,0 +1,25 @@
+Framework (from HSLExtensions)
+=========================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Framework.pkg
+
+The framework library from HSLExtensions provides two visible functions, but is also required for a few of the other HSLExtension libraries. It uses the functionality of the ASW Standard TraceLevel library. The functions it adds are: 
+
+- :ven:func:`GetVersion`
+- :ven:func:`SetTraceLevel`
+
+.. ven:function:: GetVersion()
+
+  This function gets the framework version
+
+  :return: The framework version
+  :rtype: String
+
+.. ven:function:: SetTraceLevel(variable i_intTraceLevel)
+
+  This function sets the trace level of the framework.
+
+  :params i_intTraceLevel: The trace level, for the ASWStandard::TraceLevel library. 0 = TRACE_LEVEL_NONE, 1 = TRACE_LEVEL_RELEASE, 2 = TRACE_LEVEL_DEBUG.
+  :type i_intTraceLevel: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLDeckVisualize.rst

@@ -0,0 +1,55 @@
+HSLDeckVisualize
+======================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLDeckVisualize.pkg
+
+The HSLDeckVisualize library adds functions which will update the layout shown in the run control to account for manually performed actions or cause specific effects to occur. The functions it adds are:
+
+- :ven:func:`UpdateUsedPositions`
+- :ven:func:`UpdateUsedLabware`
+- :ven:func:`UpdateLoadedLabware`
+
+.. ven:function:: UpdateUsedPositions(device dev, sequence positions, variable action, variable description)
+
+  This function updates the list of used positions and updates the view.
+
+  :params dev: The instrument for which the associated deck view will be updated. ML_STAR should be the only option visible in the dropdown.
+  :params positions: The sequence of labware and positions IDs to be updated.
+  :params action: The action to be performed on the specified positions. The same action will be performed for all positions. Action can be an integer from 0-6, with the values each representing a different event. 0 = Position is selected, 1 = Processing, 2 = Reserved, 3 = Error, 4 = Processed, 5 = Reset action state to none, 6 = Position selected and flashing.
+  :params description: The description displayed in the first section of the status bar in the deck view. 
+  :type dev: Device
+  :type positions: Sequence
+  :type action: Variable
+  :type description: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: UpdateUsedLabware(device dev, array labware, array action, variable description)
+
+  This function updates the list of used labware and updates the view accordingly. The labware and action arrays must be the same size.
+
+  :params dev: The instrument for which the associated deck view will be updated. ML_STAR should be the only option visible in the dropdown.
+  :params labware: The array of labware IDs for updating
+  :params action: The array of actions which will be applied to the associated labware at the same index in the labware array. Action can be an integer from 0-6, with the values each representing a different event. 0 = Position is seleccted, 1 = Processing, 2 = Reserved, 3 = Error, 4 = Processed, 5 = Reset action state to none, 6 = Position selected and flashing.
+  :params description: The description displayed in the first section of the status bar in the deck view. 
+  :type dev: Device
+  :type labware: Array
+  :type action: Array
+  :type description: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: UpdateLoadedLabware(device dev, array labware, array state, variable description)
+
+  This function updates the list of loaded labware and updates the view accordingly. The labware and action arrays must be the same size.
+
+  :params dev: The instrument for which the associated deck view will be updated. ML_STAR should be the only option visible in the dropdown.
+  :params labware: The array of labware IDs for updating
+  :params state: The array of load state which will be applied to the associated labware at the same index in the labware array. State can be an integer from 0-5, with the values each representing a different state. 0 = unload the labware and make not visible, 1 = load the labware, 2 = preparing to unload, 3 = preparing to load, 4 = labware will flash, 5 = labware will flash
+  :params description: The description displayed in the first section of the status bar in the deck view. 
+  :type dev: Device
+  :type labware: Array
+  :type state: Array
+  :type description: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLFilLib.rst

@@ -0,0 +1,215 @@
+HSLFilLib
+================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLFilLib.pkg
+
+This library allows interaction with and manipulation of files present on the host computer. It adds the following functions: 
+
+- :ven:func:`FilEof`
+- :ven:func:`FilFindFile`
+- :ven:func:`FilFindNextFile`
+- :ven:func:`FilFormatBarcodeFile`
+- :ven:func:`FilGetBinPath`
+- :ven:func:`FilGetCommState`
+- :ven:func:`FilGetCommTimeouts`
+- :ven:func:`FilGetConfigPath`
+- :ven:func:`FilGetLabwarePath`
+- :ven:func:`FilGetLibraryPath`
+- :ven:func:`FilGetLogFilesPath`
+- :ven:func:`FilGetMethodsPath`
+- :ven:func:`FilGetSystemPath`
+- :ven:func:`FilIsNull`
+- :ven:func:`FilReadString`
+- :ven:func:`FilRemoveFields`
+- :ven:func:`FilSearchPath`
+- :ven:func:`FilSetCommState`
+- :ven:func:`FilSetCommTimeouts`
+- :ven:func:`FilUpdateRecord`
+- :ven:func:`FilWriteString`
+
+.. ven:function:: FilEof(variable filObj)
+
+  This function checks whether the current position in the specified file is the final line
+
+  :params filObj: The opened file to be checked
+  :type filObj: Variable (file)
+  :return: Boolean as to whether the position is the end of the file or not
+  :rtype: Boolean
+
+.. ven:function:: FilFindFile(variable filName)
+
+  This function starts searching the specified path for a file. This function is obsolete, and :ven:func:`FilSearchPath` should be used instead.
+
+  :params filName: The directory or path and file name to be searched for. Can contain wildcard characters such as * or ?
+  :type filName: Variable
+  :return: If successful, the path name of the first file found that matches the input
+  :rtype: Variable
+
+.. ven:function:: FilFindNextFile()
+
+  Continues the search from :ven:func:`FilFindFile` to the next file.
+
+  :return: If successful, the path name of the next file found that matches the input from the most recent FilFindFile command
+  :rtype: Variable
+
+.. ven:function:: FilFormatBarcodeFile(variable dataSource, variable dataTarget)
+
+  This function takes the barcode ASCII text file written during LoadCarrier and converts it into a strongly formatted barcode file. This strongly formatted file can be an ASCII text file, a Microsoft Excel file, or a Microsoft Access file. Will contain the following columns:
+
+  - ID (record ID, integer)
+  - Specifier (string, P = position, C = carrier)
+  - Position (position, integer)
+  - Barcode (barcode, string)
+  - Timestamp (timestamp, YYYY-MM-DD hh:mm:ss, string)
+
+  :params dataSource: The name of the barcode ASCII file generated during the load carrier step
+  :params dataTarget: The name of the barcode ASCII text file, Microsoft Excel file or Microsoft Access file generated by the function. The name must include a table name for a Microsoft Excel file or a Microsoft Access Database. 
+  :type dataSource: Variable
+  :type dataTarget: Variable
+  :return: Boolean showing if the function was successful or not
+  :rtype: Boolean
+
+.. ven:function:: FilGetBinPath()
+
+  This function retrieves the vector binary path
+
+  :return: The vectory binary path (usually C:\Program Files (x86)\Hamilton\Bin)
+  :rtype: Variable
+
+.. ven:function:: FilGetCommState(file port)
+
+  This function retrieves the configuration information for the specified communication resource. The entries of the structure that retrieves the configuration information must be accessible in the global scope.
+
+  :params port: The communication resource opened during the file-Open operation
+  :type: Port
+  :return: Boolean showing if the function was successful or not
+  :rtype: Boolean
+
+.. ven:function:: GetCommTimeouts(file port)
+
+  This function retrieves the time-out parameters for all read and write operations for the specified communication resource. The entries of the structure that contains the configuration information must be accessible in the global scope. 
+
+  :params port: The communication resource opened during the file-Open operation
+  :type port: Port
+  :return: Boolean showing if the function was successful or not
+  :rtype: Boolean
+
+.. ven:function:: FilGetConfigPath()
+
+  This function retrieves the vector configuration path
+
+  :return: The vector configuration path (usually C:\Program Files (x86)\Hamilton\Config)
+  :rtype: Variable
+
+.. ven:function:: FilGetLabwarePath()
+
+  This function retrieves the vector labware path
+
+  :return: The vector labware path (usually C:\Program Files (x86)\Hamilton\Labware)
+  :rtype: Variable
+
+.. ven:function:: FilGetLibraryPath()
+
+  This function retrieves the vector library path
+
+  :return: The vector library path (usually C:\Program Files (x86)\Hamilton\Library)
+  :rtype: Variable
+
+.. ven:function:: FilGetLogFilesPath()
+
+  This function retrieves the vector log files path
+
+  :return: The vector log files path (usually C:\Program Files (x86)\Hamilton\LogFiles)
+  :rtype: Variable
+
+.. ven:function:: FilGetMethodsPath()
+
+  This function retrieves the vector methods path
+
+  :return: The vector methods path (usually C:\Program Files (x86)\Hamilton\Methods)
+  :rtype: Variable
+
+.. ven:function:: FilGetSystemPath()
+
+  This function retrieves the vector system path
+
+  :return: The vector system path (usually C:\Program Files (x86)\Hamilton\System)
+  :rtype: Variable
+
+.. ven:function:: FilIsNull(variable value)
+
+  This function returns a non-zero if the variable is a null value (SQL style Null). 
+
+  :params value: The variable being checked
+  :type value: Variable
+  :return: A boolean determining if the variable is SQL style Null or not
+  :rtype: Boolean
+
+.. ven:function:: FilReadString(file fileObj)
+
+  This function reads the next record from the input file as string-valued data. Row data, but no schema data, is saved to the string. After you call FilReadString, the next unread record becomes the current record, or Eof is set to hslTrue if there are no more records.
+
+  :params fileObj: The file being looked at
+  :type fileObj: File
+  :return: The contents of the line being looked at as string-valued data, or the specific run-time error
+  :rtype: String
+
+.. ven:function:: FilRemoveFields(file fileObj)
+
+  This function removes all fields from a record definition
+
+  :params fileObj: The file containing the record which is having its fields removed
+  :type fileObj: File
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: FilSearchPath(variable fileName)
+
+  This function searches for the specified file, and outputs the path and filename of the file if found, or an empty string if not found. Will search the current directory, the methods directory, the library directory, and any directories in the PATH environment variable.
+
+  :params fileName: The file name to be searched for
+  :type fileName: Variable
+  :return: The path name of the first file found, or an empty string if no files were found
+  :rtype: Variable
+
+.. ven:function:: FilSetCommState(file port, variable cfgFile)
+
+  This function configures a communication resource according to the specifications in a structure that contains the configuration information. The structure that contains the configuration information must be structured as shown below. Each entry in the structure is optional and overwrites the default value in parentheses.
+
+  :params port: The communication resource opened during the file-Open operation
+  :params cfgFile: The name of the file containing the configuration information. If this parameter is empty, the entries in the structure that contains the configuration information must be accessible in the global scope.
+  :type port: File
+  :type cfgFile: Variable
+  :return: Boolean showing whether the function succeeded or not
+  :rtype: Boolean
+
+.. ven:function:: FilSetCommTimeouts(file port, variable cfgFile)
+
+  This function sets the time-out parameters for all read and write operations on a specified communication resource. The structure that contains the time-out information is as shown below. Each entry in the structure is optional and overwrites the default value in parentheses.
+
+  :params port: The communication resource opened during the file-Open operation
+  :params cfgFile: The name of the file that contains the time-out information. If this parameter is empty, the entries in the structure that contains the time-out information must be accessible in the global scope.
+  :type port: File
+  :type cfgFile: Variable
+  :return: Boolean showing whether the function succeeded or not
+  :rtype: Boolean
+
+.. ven:function:: FilUpdateRecord(file fileObj)
+
+  Updates the current record of the file object with the values of the variable objects specified in the record definition. The current record remains current after you call the FilUpdateRecord function. The provider must support UPDATE.
+
+  :params fileObj: The file object being updated
+  :type fileObj: File
+  :return: Boolean showing whether the function succeeded or not
+  :rtype: Boolean
+
+.. ven:function:: FilWriteString(file fileObj, variable stringObj)
+
+  Writes a string to the end of the file data source. After you call the FilWriteString function, the new record becomes the current record.
+
+  :params fileObj: The file which is being written in
+  :params stringObj: The string to be written
+  :type fileObj: File
+  :type stringObj: Variable
+  :return: Boolean showing whether the function succeeded or not
+  :rtype: Boolean

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLFilLibEx.rst

@@ -0,0 +1,41 @@
+HSLFileLibEx
+=============================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLFilLibEx.pkg
+
+HSLFilLibEx allows you to manipulate files. It adds the following functions:
+
+- :ven:func:`FilCopyFileEx`
+- :ven:func:`FilDeleteFileEx`
+- :ven:func:`FilFormatReportFileEx`
+
+.. ven:function:: FilCopyFileEx(variable SourceFilePathName, variable DestinationFilePathName)
+
+  This function creates a copy of the specified file, which will be placed in the specified new location
+
+  :params SourceFilePathName: The path to the file which you wish to copy, including the file name and extension
+  :params DestinationFilePathName: The path to which you would like to copy the file, including the file name and extension
+  :type SourceFilePathName: Variable
+  :type DestinationFilePathName: Variable 
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: FilDeleteFileEx(variable FilePathName)
+
+  This function deletes the file at the specified location
+
+  :params FilePathName: The path to the file which you wish to delete, including file name and extension
+  :type FilePathName: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: FilFormatReportFileEx(variable SourceFilePathName, variable DestinationFilePathName)
+
+  This function creates a formatted/filtered copy of the specified report file. It searches the file for the string "Element Name" and copies any subsequent lines to the new file.
+
+  :params SourceFilePathName: The path to the file which you wish to format, including file name and extension
+  :params DestinationFilePathName: The path to the file you would like to create the formatted report in, including file name and extension.
+  :type SourceFilePathName: Variable
+  :type DestinationFilePathName: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLStatistics.rst

@@ -0,0 +1,95 @@
+HSLStatistics
+===================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLStatistics.pkg
+
+The HSLStatistics library is designed to easily allow the user to perform basic statistical functions easily. It adds the following functions:
+
+  - :ven:func:`Stat_Average`
+  - :ven:func:`Stat_StdDeviation`
+  - :ven:func:`Stat_CorrelationCoefficent`
+  - :ven:func:`Stat_RSQ`
+  - :ven:func:`Stat_Slope`
+  - :ven:func:`Stat_Intercept`
+  - :ven:func:`Stat_Min`
+  - :ven:func:`Stat_Max`
+
+.. ven:function:: Stat_Average(array DataArray)
+
+  This function returns the average of a data set input as an array
+
+  :params DataArray: The input array of data from which the average is calculated
+  :type DataArray: Array
+  :return: The calculated average of the array
+  :rtype: Variable
+
+.. ven:function:: Stat_StdDeviation(array DataArray)
+
+  This function returns the standard deviation of a data set input as an array
+
+  :params DataArray: The input array of data from which the standard deviation is calculated
+  :type DataArray: Array
+  :return: The calculated standard deviation of the array
+  :rtype: Variable
+
+.. ven:function:: Stat_CorrelationCoefficient(array XArray, array YArray)
+
+  This function returns the correlation coefficient (r-value) of a paired data set
+
+  :params XArray: The array of X data values in the paired set
+  :params YArray: The array of Y data values in the paired set
+  :type XArray: Array
+  :type YArray: Array
+  :return: The r-value of the paired data set
+  :rtype: Variable
+
+.. ven:function:: Stat_RSQ(array XArray, array YArray)
+
+  This function returns the pearson coefficient (r^2) of a paired data set
+
+  :params XArray: The array of X data values in the paired set
+  :params YArray: The array of Y data values in the paired set
+  :type XArray: Array
+  :type YArray: Array
+  :return: The pearson coefficient of the paired data set
+  :rtype: Variable
+
+.. ven:function:: Stat_Slope(array XArray, array YArray)
+
+  This function returns the slope of the best fit line of a paired data set
+
+  :params XArray: The array of X data values in the paired set
+  :params YArray: The array of Y data values in the paired set
+  :type XArray: Array
+  :type YArray: Array
+  :return: The slope of the best fit line
+  :rtype: Variable
+
+.. ven:function:: Stat_Intercept(array XArray, array YArray)
+
+  This function returns the intercept of the best fit line of a paired data set
+
+  :params XArray: The array of X data values in the paired set
+  :params YArray: The array of Y data values in the paired set
+  :type XArray: Array
+  :type YArray: Array
+  :return: The intercept of the line of best fit
+  :rtype: Variable
+
+.. ven:function:: Stat_Min(array DataArray)
+
+  This function returns the lowest value of a dataset
+
+  :params DataArray: The array for the minimum to be searched in
+  :type DataArray: Array
+  :return: The lowest value of the dataset
+  :rtype: Variable
+
+.. ven:functions:: Stat_Max(array DataArray)
+
+  This function returns the hgihest value of a dataset
+
+  :params DataArray: The array for the minimum to be searched in
+  :type DataArray: Array
+  :return: The lowest value of the dataset
+  :rtype: Variable

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLStrLib.rst

@@ -0,0 +1,395 @@
+HSLStrLib
+==========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLStrLib.pkg
+
+HSL String Library provides the following functions: 
+
+- :ven:func:`StrAsciiToStr`
+- :ven:func:`StrConcat2`
+- :ven:func:`StrConcat4`
+- :ven:func:`StrConcat8`
+- :ven:func:`StrConcat12`
+- :ven:func:`StrEvaluateExpr`
+- :ven:func:`StrFillLeft`
+- :ven:func:`StrFillRight`
+- :ven:func:`StrFind`
+- :ven:func:`StrFStr`
+- :ven:func:`StrFStrEx`
+- :ven:func:`StrFVal`
+- :ven:func:`StrGetLength`
+- :ven:func:`StrGetType`
+- :ven:func:`StrHexIStr`
+- :ven:func:`StrIsDigit`
+- :ven:func:`StrIStr`
+- :ven:func:`StrIVal`
+- :ven:func:`StrLeft`
+- :ven:func:`StrMakeLower`
+- :ven:func:`StrMakeLowerCopy`
+- :ven:func:`StrMakeUpper`
+- :ven:func:`StrMakeUpperCopy`
+- :ven:func:`StrMid`
+- :ven:func:`StrReplace`
+- :ven:func:`StrReverseFind`
+- :ven:func:`StrRight`
+- :ven:func:`StrSpanExcluding`
+- :ven:func:`StrStrToAscii`
+- :ven:func:`StrTrimLeft`
+- :ven:func:`StrTrimRight`
+
+..  ven:function:: StrAsciiToStr(variable asciiCode)
+
+    Converts the given ASCII Code (an integer) to a character (string).
+
+    :param asciiCode: The ASCII code to convert
+    :type asciiCode: Integer
+    :return: The ASCII code as a string
+    :rtype: String
+
+.. ven:function:: StrConcat2(variable Var1, variable Var2)
+
+    Combines two strings into a new string
+
+    :param Var1: The first string to be combined
+    :param Var2: The second string to be combined
+    :type Var1: String
+    :type Var2: String
+    :return: The combined string of Var1 + Var2
+    :rtype: String
+
+.. ven:function:: StrConcat4(variable Var1, variable Var2, variable Var3, variable Var4)
+
+    Combines four strings into a new string
+
+    :param Var1: The first string to be combined
+    :param Var2: The second string to be combined
+    :param Var3: The third string to be combined
+    :param Var4: The fourth string to be combined
+    :type Var1: String
+    :type Var2: String
+    :type Var3: String
+    :type Var4: String
+    :return: The combined string of Var1 + Var2 + Var3 + Var4
+    :rtype: String
+
+.. ven:function:: StrConcat8(variable Var1, variable Var2, variable Var3, variable Var4, variable Var5, variable Var6, variable Var7, variable Var8)
+
+    Combines eight strings into a new string
+
+    :param Var1: The first string to be combined
+    :param Var2: The second string to be combined
+    :param Var3: The third string to be combined
+    :param Var4: The fourth string to be combined
+    :param Var5: The fifth string to be combined
+    :param Var6: The sixth string to be combined
+    :param Var7: The seventh string to be combined
+    :param Var8: The eighth string to be combined
+    :type Var1: Variable
+    :type Var2: Variable
+    :type Var3: Variable
+    :type Var4: Variable
+    :type Var5: Variable
+    :type Var6: Variable
+    :type Var7: Variable
+    :type Var8: Variable
+    :return: The combined string of Var1 + Var2 + Var3 + Var4 + Var5 + Var6 + Var7 + Var8
+    :rtype: String
+
+.. ven:function:: StrConcat12(variable Var1, variable Var2, variable Var3, variable Var4, variable Var5, variable Var6, variable Var7, variable Var8, variable Var9, variable var10, variable var11, variable var12)
+
+    Combines twelve strings into a new string
+
+    :param Var1: The first string to be combined
+    :param Var2: The second string to be combined
+    :param Var3: The third string to be combined
+    :param Var4: The fourth string to be combined
+    :param Var5: The fifth string to be combined
+    :param Var6: The sixth string to be combined
+    :param Var7: The seventh string to be combined
+    :param Var8: The eighth string to be combined
+    :param Var9: The ninth string to be combined
+    :param Var10: The tenth string to be combined
+    :param Var11: The eleventh string to be combined
+    :param Var12: The twelfth string to be combined
+    :type Var1: Variable
+    :type Var2: Variable
+    :type Var3: Variable
+    :type Var4: Variable
+    :type Var5: Variable
+    :type Var6: Variable
+    :type Var7: Variable
+    :type Var8: Variable
+    :type Var9: Variable
+    :type Var10: Variable
+    :type Var11: Variable
+    :type Var12: Variable
+    :return: The combined string of Var1 + Var2 + Var3 + Var4 + Var5 + Var6 + Var7 + Var8 + Var9 + Var10 + Var11 + Var12
+    :rtype: Variable
+
+.. ven:function:: StrEvaluateExpr(variable expression)
+
+    This function evaluates an expression within a string. All variables involved must have global scope. 
+
+    :params expression: The expression to evaluate as a string
+    :type expression: Variable
+    :return: The value of the expression if the function succeeds, otherwise a runtime error
+    :rtype: Variable
+
+.. ven:function:: StrFillLeft(variable str, variable character, variable width)
+
+    This function fills leading characters to the string
+
+    :params str: The string to be modified
+    :params character: The user-defined character to be filled
+    :params width: The width to be filled
+    :type str: Variable
+    :type character: Variable
+    :type width: Integer
+    :return: The modified string
+    :rtype: Variable
+
+.. ven:function:: StrFillRight(variable str, variable character, variable width)
+
+    This function fills trailing characters to the string
+
+    :params str: The string to be modified
+    :params character: The user-defined character to be filled
+    :params width: The width to be filled
+    :type str: Variable
+    :type character: Variable
+    :type width: Integer
+    :return: The modified string
+    :rtype: Variable
+
+.. ven:function:: StrFind(variable str, variable subStr)
+
+    This function searches the string for the first match of the sub-string.
+
+    :params str: The string to be searched
+    :params subStr: The substring to be searched for
+    :type str: Variable
+    :type subStr: Variable
+    :return: The zero-based index of the first character in this string object that matches the requested sub-string or characters. -1 if the sub-string is not found.
+    :rtype: Integer
+
+.. ven:function:: StrFStr(variable number)
+
+    This function converts the floating point number input into the corresponding character string. 
+
+    :params number: The float to be converted into a string
+    :type number: Float
+    :return: The string form of the float
+    :rtype: Variable
+
+.. ven:function:: StrFStrEx(variable number, variable languageSpecific, variable precision)
+
+    This function converts the floating point number input into the corresponding character string
+
+    :params number: The float to be converted into a string.
+    :params languageSpecific: Boolean which specifies whether the decimal symbol in the Regional Settings should be used to write the string representation of the floating point number.
+    :params precision: The total number of significant digits to be used for the floating-point display
+    :type number: Float
+    :type languageSpecific: Boolean
+    :type precision: Integer
+    :return: The string representation of the floating point number
+    :rtype: Variable
+
+.. ven:function:: StrFVal(variable str)
+
+    Converts the sequence of digits, contained in the character string str, into the corresponding floating point number. Conversion aborts at the first character in str, which is not a digit or not one of the characters +, -, e, E.
+
+    :params str: The string to be converted
+    :type str: Variable
+    :return: THe float representation of the input string. Null if the string cannot be converted. DBL_MAX if the conversion results in an overflow. DBL_MIN if the conversion results in an underflow. 
+    :rtype: Float or variable
+
+.. ven:function:: StrGetLength(variable str)
+
+    Returns the number of characters in a string object (without '\0').
+
+    :params str: The string being read
+    :type str: Variable
+    :return: The length of the string
+    :rtype: Integer
+
+.. ven:function:: StrGetType(variable var)
+
+    This function retrieves the type of the value of a variable
+
+    :params var: A reference to a variable (int, float or string)
+    :type var: Variable
+    :return: One of the following string-valued constants that indicates the type of the value of a variable. i = hslInteger, f = hslFloat, s = hslString, null = no type
+    :rtype: Variable
+
+.. ven:function:: StrHexIStr(variable number)
+
+    Converts the input integer into the corresponding hexadecimal character string
+
+    :params number: The integer to be converted
+    :type: Integer
+    :return: The hexadecimal string representation of the integer
+    :rtype: String
+
+.. ven:function:: StrIsDigit(variable character)
+
+    The StrIsDigit function determines if the specified input string (which should be a character) is a digit or not.
+
+    :params character: The input character to be a tested, as a string
+    :type character: Variable
+    :return: Boolean showing whether the character is a digit (1) or not (0)
+    :rtype: Boolean
+
+.. ven:function:: StrIsStr(variable number)
+
+    The StrIStr function converts the input integer into the corresponding character string
+
+    :params number: The integer to be converted
+    :type number: Variable
+    :return: The string representation of the integer number
+    :rtype: Variable
+
+.. ven:function:: StrIVal(variable str)
+
+    The StrIVal function converts the input sequence of digits into the corresponding integer. The input string is treated as a decimal, unless it begins with an 0x in which case it is interpreted as hexadecimal.            Conversion aborts at the first character in the input which is neither a digit nor one of the characters "+" or "-".
+
+    :params str: The input sequence of digits to be converted
+    :type str: Variable
+    :return: The numeric value of the sequence of digits contained in the character string, as an integer. Null if the character string cannot be converted into a number. LONG_MAX = 2147483647 if the conversion results in an overflow. LONG_MIN = -2147483647 - 1 if the conversion results in an underflow.
+    :rtype: Variable
+
+.. ven:function:: StrLeft(variable str, variable count)
+
+    The StrLeft function extracts the first (leftmost) characters of a string and returns a copy of the extracted substring. The number of characters extracted is equal to the input variable "count". If "count" is longer than the string, the entire string is returned.
+
+    :params str: The input string from which the substring is to be extracted
+    :params count: The number of characters to be extracted
+    :type str: Variable
+    :type count: Variable
+    :return: A string containing a copy of the specified range of characters. Can be an empty string.
+    :rtype: Variable
+
+.. ven:function:: StrMakeLower(variable str)
+
+    The StrMakeLower function converts the original string to its lowercase form.
+
+    :params str: The string to be converted
+    :type str: Variable
+    :return: The original string converted to lowercase
+    :rtype: Variable
+
+.. ven:function:: StrMakeLowerCopy(variable str)
+
+    The StrMakeLowerCopy function returns a copy of the original string converted to lowercase.
+
+    :params str: The string to be copied
+    :type str: Variable
+    :return: A copy of the original string converted to lowercase
+    :rtype: Variable
+
+.. ven:function:: StrMakeUpper(variable str)
+
+    The StrMakeUpper function converts the original string to its uppercase form.
+
+    :params str: The string to be converted
+    :type str: Variable
+    :return: The original string converted to uppercase
+    :rtype: Variable
+
+.. ven:function:: StrMakeUpperCopy(variable str)
+
+    The StrMakeUpperCopy function returns a copy of the original string converted to uppercase.
+
+    :params str: The string to be copied
+    :type str: Variable
+    :return: A copy of the original string converted to uppercase
+    :rtype: Variable
+
+.. ven:function:: StrMid(variable str, variable first, variable count)
+
+    The StrMid function extracts a substring of length "count" characters from the input variable "str", starting at position "first" which is 0-based. The function returns a copy of the extracted substring.
+
+    :params str: The string from which the substring is to be extracted
+    :params first: The first character to be extracted (0-based)
+    :params count: The number of characters to be extracted
+    :type str: Variable
+    :type first: Variable
+    :type count: Variable
+    :return: A string containing a copy of the specified range of characters, can be empty
+    :rtype: Variable
+
+.. ven:function:: StrReplace(variable str, variable oldSubStr, variable newSubStr)
+
+    The StrReplace function searches a string for a specified substring and replaces it with another specified substring.
+
+    :params str: The string to be edited
+    :params oldSubStr: The substring to be replaced by newSubStr
+    :params newSubStr: The substring to replace oldSubStr
+    :type str: Variable
+    :type oldSubStr: Variable
+    :type newSubStr: Variable
+    :return: The number of replaced instances of oldSubStr. Zero if the string is unchanged.
+    :rtype: Variable
+
+.. ven:function:: StrReverseFind(variable str, variable subStr)
+
+    The StrReverseFind function searches a string object for the last match of a sub-string
+
+    :params str: The string to be searched
+    :params subStr: The substring to be searched for
+    :type str: Variable
+    :type subStr: Variable
+    :return: The zero-based index of the last character in this string that matches the requested substring or characters. -1 if the substring is not found.
+    :rtype: Variable
+
+.. ven:function:: StrRight(variable str, variable count)
+
+    The StrRight function extracts the last (rightmost) characters of a string and returns a copy of the extracted substring. The number of characters extracted is equal to the input variable "count". If "count" is longer than the string, the entire string is returned.
+
+    :params str: The input string from which the substring is to be extracted
+    :params count: The number of characters to be extracted
+    :type str: Variable
+    :type count: Variable
+    :return: A string containing a copy of the specified range of characters. Can be an empty string.
+    :rtype: Variable
+
+.. ven:function:: StrSpanExcluding(variable str, variable subStr)
+
+    The StrSpanExcluding function can be used to search the string for the first occurrence of any character in the specified set subStr. StrSpanExcluding extracts and returns all characters preceding the first occurrence of a character from subStr (in other words, the character from subStr and all characters following it in the string, are not returned). If no character from subStr is found in the string, then StrSpanExcluding returns the entire string.
+
+    :params str: The string to be searched
+    :params subStr: A string containing the set of characters to be searched for
+    :type str: Variable
+    :type subStr: Variable
+    :return: A sub-string containing characters in the string that are not in subStr, beginning with the first character in the string and ending with the first character found in the string that is also in subStr (that is, starting with the first character in the string and up to but excluding the first character in the string that is found subStr). It returns the entire string if no character in subStr is found in the string.
+    :rtype: Variable
+
+.. ven:function:: StrStrToAscii(variable character)
+
+    The StrStrToAscii function converts the given character (as a string) into an ASCII code (as an integer)
+
+    :params character: The character to convert, inputted as a string
+    :type character: Variable
+    :return: The ASCII code for the given character as an integer, -1 if the function fails
+    :rtype: Variable
+
+.. ven:function:: StrTrimLeft(variable str, variable character)
+
+    The StrTrimLeft function trims leading whitespace characters from the string (removes newline, space, tab, and user-defined characters)
+
+    :params str: The string to trim
+    :params character: A string containing user-defined characters to be trimmed (may be empty, in which case only newline, space and tabs will be trimmed)
+    :type str: Variable
+    :type character: Variable
+    :return: None
+    :rtype: N/A
+
+.. ven:function:: StrTrimRight(variable str, variable character)
+
+    The StrTrimRight function trims lagging whitespace characters from the string (removes newline, space, tab, and user-defined characters)
+
+    :params str: The string to trim
+    :params character: A string containing user-defined characters to be trimmed (may be empty, in which case only newline, space and tabs will be trimmed)
+    :type str: Variable
+    :type character: Variable
+    :return: None
+    :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/HSLZipLib.rst

@@ -0,0 +1,49 @@
+HSLZipLib
+================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSLZipLib.pkg
+
+HSLZipLib is a library that allows you to create zip folders, as well as unzip and extract folders from them. It adds the following four functions:
+
+- :ven:func:`UnpackArchive`
+- :ven:func:`AddItemToArchive`
+- :ven:func:`InitializeArchive`
+- :ven:func:`PackArchive`
+
+.. ven:function:: UnpackArchive(variable i_strArchiveName, variable i_strPathOutput)
+
+  The unpack archive function unzips a zip folder and extracts the contents to the specified location.
+
+  :params i_strArchiveName: The full name and path to the zip folder you wish to unzip, including the .zip file extension
+  :params i_strPathOutput: The full name and path of the folder you would like to create when extracting the zip file, with no extension
+  :type i_strArchiveName: Variable
+  :type i_strPathOutput: Variable
+  :return: Boolean confirming whether unzipping the archive was successful or not
+  :rtype: Boolean
+
+.. ven:function:: AddItemToArchive(variable i_strFileOrDirectoryName, variable i_strDirectoryPathInArchive)
+
+  This function specifies a file or directory which will be added to the zip file which will be generated with the :ven:func:`PackArchive` function. 
+
+  :params i_strFileOrDirectoryName: The path to the file or directory that you wish to include in the zip folder. File extension required for files, no extension required for folders.
+  :params i_strDirectoryPathInArchive: The path to the desired location of the file within the zip folder.
+  :type i_strFileOrDirectoryName: Variable
+  :type i_strDirectoryPathInArchive: Variable
+  :return: Boolean confirming whether adding the file or directory to the archive was successful
+  :rtype: Boolean
+
+.. ven:function:: InitializeArchive(variable i_strArchiveName)
+
+  This function initializes whatever archive is specified. It is required to call this function for each archive you are interacting with, in advance of calling any of the otehr functions. 
+
+  :params i_strArchiveName: The name of the desired zip file; can be a file that already exists or one that doesn't exist yet and will be created
+  :type i_strArchiveName: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: PackArchive()
+
+  This function zips/packs whichever archive was most recently initialized. 
+
+  :return: Boolean confirming whether zipping the archive was successful or not
+  :rtype: Boolean

VenusLibraryDocumentation-DocsForGPT/docs/source/HSL_SeqDailyTools.rst

@@ -0,0 +1,61 @@
+HSL_SeqDailyTools
+=======================================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/HSL_SeqDailyTools.pkg 
+
+The HSL_SeqDailyTools library adds four functions aimed at making some parts of sequence handling slightly easier. The four functions it adds are:
+
+- :ven:func:`CopyPlatePattern96ToTipRack`
+- :ven:func:`CopyPlatePatternToPlate`
+- :ven:func:`GetNumberOfPositionsLeft`
+- :ven:func:`SeqEasyEdit`
+
+.. ven:function:: CopyPlatePattern96ToTipRack(sequence plateSource, sequence tipRack)
+
+  This function copies the sequence pattern on a 96 well plate and applies it to a tip rack. It is used to ensure that the 96 head only picks up tips in the wells that the plate is going to be interacting with.
+
+  :params plateSource: The sequence pattern on the plate to be copied
+  :params tipRack: The sequence of the tip rack which will have the template applied to it
+  :type plateSource: Sequence
+  :type tipRack: Sequence
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: CopyPlatePatternToPlate(sequence plateSource, sequence plateTarget)
+
+  This function copies the pattern of wells from one plate to another plate. It is useful when a plate is being moved around on deck, or when reagents are being pipetted from one plate into the same locations on another plate.
+
+  :params plateSource: The sequence pattern from the plate to be copied
+  :params plateTarget: The sequence of the second plate which is having the template applied to it
+  :type plateSource: Sequence
+  :type plateTarget: Sequence
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: GetNumberOfPositionsLeft(sequence seq, variable numberOfPositionsLeft)
+
+  This function calculates the number of positions left in a sequence
+
+  :params seq: The sequence which is being checked
+  :params numberOfPositionsLeft: The output value of how many positions are left in the sequence
+  :type seq: Sequence
+  :type numberOfPositionsLeft: Variable
+  :return: None  
+  :rtype: N/A
+
+.. ven:function:: SeqEasyEdit(sequence seq, variable timeout, variable dialog_title, variable dialog_msg, device ML_STAR)
+
+  This function is a simplified version of SeqEdit, with only the parameters that are regularly used. It opens a dialog box from which the user can edit whichever sequence is specified in the input.
+
+  :params seq: The sequence which is being edited
+  :params timeout: How long the dialog window will stay open by itself before it closes and continues the method without editing the sequence
+  :params dialog_title: The title of the dialog window which pops up
+  :params dialog_message: The text within the dialog window which pops up
+  :params ML_STAR: The device used. Should be ML_STAR from the dropdown
+  :type seq: Sequence
+  :type timeout: Variable
+  :type dialog_title: Variable
+  :type dialog_message: Variable
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/If_And_If_Or.rst

@@ -0,0 +1,39 @@
+If_And_If_Or
+===================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/If_And_If_Or.pkg
+
+The if_and_if_or library adds two functions:
+
+- :ven:func:`if_and`
+- :ven:func:`if_or`
+
+.. ven:function:: if_and(variable iVar1, variable iVar2, variable iVar3, variable iVar4)
+	
+	This function checks variable iVar1 against iVar2 and iVar3 against iVar4; if both statements are true then the function returns a 1, otherwise it returns a 0
+
+	:params iVar1: Variable to be checked against iVar2
+	:params iVar2: Variable to be checked against iVar1
+	:params iVar3: Variable to be checked against iVar4
+	:params iVar4: Variable to be checked against iVar3
+	:type iVar1: Variable
+	:type iVar2: Variable
+	:type iVar3: Variable
+	:type iVar4: Variable
+	:return: 1 if both true, 0 otherwise
+	:rtype: Variable
+
+.. ven:function:: if_or(variable iVar1, variable iVar2, variable iVar3, variable iVar4)
+
+	This function checks variable iVar1 against iVar2 and iVar3 against iVar4; if at least one of the statements is true then the function will return a 1, otherwise it will return a 0
+
+	:params iVar1: Variable to be checked against iVar2
+	:params iVar2: Variable to be checked against iVar1
+	:params iVar3: Variable to be checked against iVar4
+	:params iVar4: Variable to be checked against iVar3
+	:type iVar1: Variable
+	:type iVar2: Variable
+	:type iVar3: Variable
+	:type iVar4: Variable
+	:return: 1 if at least one is true, 0 if false
+	:rtype: Variable

VenusLibraryDocumentation-DocsForGPT/docs/source/Inheco ODTC - unfinished.rst

@@ -0,0 +1,86 @@
+Inheco ODTC
+==========================================
+
+The Inheco ODTC library is used to operate up to 4 Inheco ODTC devices, adding both "Standard" and "Advanced" functions to manipulate them. The functions added are:
+
+Standard Functions
+-----------------------------------------
+
+- :ven:func:`Connect`
+- :ven:func:`GetStatus`
+- :ven:func:`Reset`
+- :ven:func:`Initialize`
+- :ven:func:`SetTraceLevel`
+- :ven:func:`OpenDoor`
+- :ven:func:`CloseDoor`
+- :ven:func:`DownloadProtocol`
+- :ven:func:`ExecuteMethod`
+- :ven:func:`WaitForEndOfExecuteMethod`
+- :ven:func:`StopMethod`
+- :ven:func:`Abort`
+- :ven:func:`ReadActualTemperature`
+- :ven:func:`Terminate`
+- :ven:func:`EvaluateError`
+- :ven:func:`AddAllowedReturnCode`
+
+Advanced Functions
+-----------------------------------------
+
+- :ven:func:`LockDevice`
+- :ven:func:`UnlockDevice`
+- :ven:func:`SetCSVSeparator`
+- :ven:func:`SetDateTime`
+- :ven:func:`SetNetWorkConfig`
+- :ven:func:`GetParameters`
+- :ven:func:`GetDeviceIdentification`
+- :ven:func:`GetConfiguration`
+- :ven:func:`Pause`
+- :ven:func:`DoContinue`
+- :ven:func:`SetParameters`
+- :ven:func:`SetLogLevel`
+- :ven:func:`RegisterStatusEventURL`
+- :ven:func:`UnregisterStatusEventURL`
+- :ven:func:`GetLastData`
+- :ven:func:`DisableTemperatureEvent`
+
+.. ven:function:: Connect(variable i_strLocalIP, variable i_strDeviceIP, variable i_strDevicePort, variable i_blnSimulationMode, variable o_intDeviceID, variable o_strMessage)
+
+  This function is used to connect to the Inheco ODTC device.
+
+  :params i_strLocalIP: The IP address of the computer. If this parameter is set to an empty string, the library will try to retrieve the computer's IP address automatically. If automatic IP address configuration doesn't work (i.e. two or more network cards in the system have close IP addresses), configure the IP address to a fixed one and supply this address.
+  :params i_strDeviceIP: The IP address of the ODTC device. This must be in the format of "xxx.xxx.xxx.xxx". The IP address of the device can be retrieved using the Inhecodevice finder tool located in the library directory. Start the application 'DeviceFinder (xxxxx).exe' where xxxxx represents a five-digit revision number, wait at least 20 seconds to see the retrieved ip address. If address is not found automatically, click button 'Find Device via Name/IP' and supply the string ODTC_XXXXXX where XXXXXX represents the last 6 characters of the device's MAC address. The string to provide may be found on the label SiLA Service Configuration located on the device controller. 
+  :params i_strDevicePort: The port used by the ODTC device. Should be set to "". This parameter should only be set to a specific port on official request as the device has to be configured to use this special port.
+  :params i_blnSimulationMode: Simulation mode for the library. Set to either 0 (device is not simulated) or 1 (device is simulated).
+  :params o_intDeviceID: The unique identifier for this device. Use this number as input for all subsequent function calls.
+  :params o_strMessage: Informational message
+  :type i_strLocalIP: Variable
+  :type i_strDeviceIP: Variable
+  :type i_strDevicePort: Variable
+  :type i_blnSimulationMode: Boolean
+  :type o_intDeviceID: Variable
+  :type o_strMessage: Variable
+  :return: A boolean as to whether the function returned successfully (1) or not (0).
+  :rtype: Boolean
+
+.. ven:function:: GetStatus(variable i_intDeviceID, variable o_strDeviceID, variable o_strState, variable o_blnLocked, variable o_strPMSId, variable o_strCurrentTime, variable o_intSILAReturnValue, variable o_strSILAMessage)
+
+  This function is used to retrieve the status of the device.
+
+  :params i_intDeviceID: The unique identifier for the device as returned by the :ven:func:`Connect` function. 
+  :params o_strDeviceID: Internal information of the device
+  :params o_strState: State as reported by the device. One of the following values:'startup', 'resetting', 'standby', 'idle', 'busy', 'paused', 'errorhandling', 'inerror', 'asynchpaused', 'pauserequested', 'processing', 'responsewaiting'
+  :params o_blnLocked: Lock state of the device
+  :params o_strPMSId: Name of the PMS connected to the device
+  :params o_strCurrentTime: Time as reported by the device
+  :params o_intSILAReturnValue: The SILA return code of the device
+  :params o_strSILAMessage: The SILA message returned by the device
+  :type i_intDeviceID: Variable
+  :type o_strDeviceID: Variable
+  :type o_strState: Variable 
+  :type o_blnLocked: Variable
+  :type o_strPMSId: Variable
+  :type o_strCurrentTime: Variable
+  :type o_intSILAReturnValue: Variable
+  :type o_strSILAMessage: Variable
+  :return: A boolean as to whether the function returned succesfully (1) or not (0).
+  :rtype: Boolean

VenusLibraryDocumentation-DocsForGPT/docs/source/Labware_Properties.rst

@@ -0,0 +1,169 @@
+Labware Properties
+=========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Labware_Properties.pkg
+
+The labware properties library adds a variety of functions which assist with obtaining the physical data of the labware, as well as things like its ID. The functions it adds are:
+
+  - :ven:func:`GetCarrierIDandSiteID_FromLabID`
+  - :ven:func:`Get_ContainerBaseOffset`
+  - :ven:func:`Get_ContainerBaseThickness`
+  - :ven:func:`Get_Height`
+  - :ven:func:`Get_NameAndFileName`
+  - :ven:func:`Get_NumberOfColumns`
+  - :ven:func:`Get_NumberOfRows`
+  - :ven:func:`Get_RackBaseToCoverBase`
+  - :ven:func:`Get_StackHeight`
+  - :ven:func:`Get_XYZ_deckPosition`
+  - :ven:func:`Get_XY_dimensions`
+
+.. ven:function:: GetCarrierIDandSiteID_FromLabID(device io_instrument, variable i_labware_ID, variable o_carrier_ID, variable o_site_ID)
+
+  This function takes outputs the carrier ID and site ID which are associated with the given labware ID. It works on both the Nimbus and the STAR.
+
+  :params io_instrument: The instrument being used. Will either be ML_STAR or Nimbus.
+  :params i_labware_ID: The labware ID from which the other IDs are being pulled.
+  :params o_carrier_ID: The carrier ID associated with the given labware ID.
+  :params o_site_ID: The site ID associated with the given labware ID.
+  :type io_instrument: Device
+  :type i_labware_ID: Variable
+  :type o_carrier_ID: Variable
+  :type o_site_ID: Variable
+  :return: A boolean determining whether the labware ID exists (1) or not (0)
+  :rtype: Boolean
+
+.. ven:function:: Get_ContainerBaseOFfset(device io_instrument, sequence i_sequenceLabware, variable i_sequencePosition, variable o_ContainerBaseOffset)
+
+  This function outputs the distance from the rack base to the container base for the labware at the given sequence position.
+
+  :params io_instrument: The instrument being used. Will either be ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params i_sequencePosition: The position ID or index of the sequence being checked. Can be either int or str. An input of 0 will auto-select the first position.
+  :params o_ContainerBaseOFfset: The distance from the rack base to the container base at the specified position
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type i_sequencePosition: Variable
+  :type o_ContainerBaseOFfset: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_ContainerBaseThickness(device io_instrument, sequence i_sequenceLabware, variable o_containerBaseThickness)
+
+  This function outputs the base thickness of the container at the first position of a given sequence.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence asspciated with the labware being checked.
+  :params o_containerBaseThickness: The thickness of the base of the container being checked.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_containerBaseThickness: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_Height(device io_instrument, sequence i_sequenceLabware, variable o_labwareHeight)
+
+  This function outputs the height of the labware at the first position of a given sequence. This value is only the labware height, not the absolute Z position.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_labwareHeight: The height of the labware being checked.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_labwareHeight: Variable
+  :return: None  
+  :rtype: N/A
+
+.. ven:function:: Get_NameAndFileName(device io_instrument, sequence i_sequenceLabware, variable o_viewName, variable o_fileName)
+
+  This function outputs the labware view name and the file name associated with it (with path)
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware of interest.
+  :params o_viewName: The view name of the labware being checked.
+  :params o_fileName: The file name (with path) of the labware being checked.
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_NumberOfColumns(device io_instrument, sequence i_sequenceLabware, variable o_labwareColumns)
+
+  This function outputs the number of columns defined in the labware from the first position of a given sequence.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware of interest.
+  :params o_labwareColumns: The number of columns defined in the labware being checked.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_labwareColumns: Variable  
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_NumberOfRows(device io_instrument, sequence i_sequenceLabware, variable o_labwareColumns)
+
+  This function outputs the number of rows defined in the labware at the first position of a given sequence. The variable and function description both say columns; this is incorrect.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_labwareColumns: The number of rows defined in the labware being checked.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_labwareColumns: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_RackBaseToCoverBase(device io_instrument, sequence i_sequenceLabware, variable o_RackBaseToCoverBase_Height)
+
+  This function outputs the height from the base of the rack to the base of the cover/lid of the labware at the first position of a given sequence.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_RackBaseToCoverBase_Height: The distance from the rack base to the cover base.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_RackBaseToCoverBase_Height: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_StackHeight(device io_instrument, sequence i_sequenceLabware, variable o_labwareStackHeight)
+
+  This function outputs the stack height of the specified labware at the first position of a given sequence.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_labwareStackHeight: The stack height of the labware being checked, or the covered stack height if the labware is lidded.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_labwareStackHeight: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_XYZ_deckPosition(device io_instrument, sequence i_sequenceLabware, variable o_labware_deckPosition_X, variable o_labware_deckPosition_Y, variable o_labware_deckPosition_Z)
+
+  This function returns the X, Y and Z coordinates of the upper left well of the specified labware at the first position of a given sequence. The description of this function says it only does the X and Y coordinates, this is incorrect.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_labware_deckPosition_X: The X coordinate of the labware on the deck.
+  :params o_labware_deckPosition_Y: The Y coordinate of the labware on the deck.
+  :params o_labware_deckPosition_Z: The Z coordinate of the labware on the deck.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_labware_deckPosition_X: Variable
+  :type o_labware_deckPosition_Y: Variable
+  :type o_labware_deckPosition_Z: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Get_XY_dimensions(device io_instrument, sequence i_sequenceLabware, variable o_X_width, variable o_Y_depth)
+
+  This function outputs the X (width) and Y (depth) dimensions of the specified labware at the first position of a given sequence.
+
+  :params io_instrument: The instrument being used. Will be either ML_STAR or Nimbus.
+  :params i_sequenceLabware: The sequence associated with the labware being checked.
+  :params o_X_width: The width of the labware being checked.
+  :params o_Y_depth: The depth of the labware being checked.
+  :type io_instrument: Device
+  :type i_sequenceLabware: Sequence
+  :type o_X_width: Variable
+  :type o_Y_depth: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/Lookup.rst

@@ -0,0 +1,20 @@
+Lookup
+================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Lookup.pkg
+
+The lookup library provides one function which allows you to locate items in an array and get their index.
+
+- :ven:func:`Lookup`
+
+.. ven:function:: Lookup(array array, variable item)
+
+  Input an array and a value to look up. If the value occurs in the array, it will return the 1-based index. If it doesn't occur in the array, it will return a 0. 
+
+  :params array: The array to search
+  :params item: The variable to search for
+  :type array: Array
+  :type item: Variable
+  :return: 1-based index if found, 0 if not found
+  :rtype: Variable
+

VenusLibraryDocumentation-DocsForGPT/docs/source/Pipetting.rst

@@ -0,0 +1,88 @@
+Pipetting (from HSLExtensions)
+======================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Pipetting.pkg
+
+The pipetting library from HSL Extensions adds functions related to pipetting, primarily to do with sequences and channel patterns. The functions it adds are: 
+
+- :ven:func:`CreateMixedChannelPattern`
+- :ven:func:`CreateOrderedChannelPattern`
+- :ven:func:`ParseChannelPattern`
+- :ven:func:`Plate384PositionNumberToPositionText`
+- :ven:func:`Plate384PositionTextToPositionNumber`
+- :ven:func:`Plate96PositionNumberToPositionText`
+- :ven:func:`Plate96PositionTextToPositionNumber`
+
+.. ven:function:: CreateMixedChannelPattern(array i_arrUseChannel, variable i_intTotalNumberOfChannels)
+
+  This function generates a "mixed" channel pattern. The channel pattern generated will be based on the input array, and then will be filled with "0"s up to the total number of channels (normally 8). If the array size is greater than the total number of channels inputted, the channel pattern will be limited to whatever the total number of channels inputted is. E.g. if the array is [1,1,1,1,0,0,1,0,0,0,1] and the input channel number is 8, the channel pattern generated will be "11110010".
+
+  :params i_arrUseChannel: A boolean array of which channels should be used.
+  :params i_intTotalNumberOfChannels: The total number of channels being used.
+  :type i_arrUseChannel: Array
+  :type i_intTotalNumberOfChannels: Variable
+  :return: The channel pattern generated by the function 
+  :rtype: String
+
+.. ven:function:: CreateOrderedChannelPattern(variable i_intNumberOfUsedChannels, variable i_intTotalNumberOfChannels)
+
+  This function creates an ordered channel pattern, generating a string with as many "1"s in it as the inputted number of used channels, and adding "0"s until the total length of the channel pattern is equal to the total number of channels inputted. If the total number of used channels is greater than the total number of channels, the channel pattern will be truncated to the total number of channels. E.g. if the number of used channels is 3 and the total number of channels is 8, the channel pattern generated will be "11100000". If these numbers were reversed, the channel pattern generated would simply be "111".
+  :params i_intNumberOfUsedChannels: The number of "active" channels wishing to be used in the channel pattern
+  :params i_intTotalNumberOfChannels: The max number of channels available (usually 8 on a STAR)
+  :type i_intNumberOfUsedChannels: Variable
+  :type i_intTotalNumberOfChannels: Variable
+  :return: The channel pattern generated by the function
+  :rtype: String
+
+.. ven:function:: ParseChannelPattern(variable i_strChannelPattern)
+
+  This function parses a channel pattern given as a string and creates a boolean array of the channels being used. If the input has the wrong type, or contains not allowed characters, the result is an empty array.
+
+  :params i_strChannelPattern: The channel pattern to be parsed
+  :type i_strChannelPattern: Variable
+  :return: The array of booleans with the channels being used in the channel pattern
+  :rtype: Array
+
+.. ven:function:: Plate384PositionNumberToPositionText(variable i_intPositionNumber, variable o_strPositionText)
+
+  This function converts position number to position text for a 384 well plate. E.g. if given a 1 it will convert it to A1, if given a 16 it will convert it to P1, etc.
+
+  :params i_intPositionNumber: The position number to be converted. Any int in the range of 1-384.
+  :params o_strPositionText: The position text which will be the output. Will be a string of any of the well identifiers on a 384 well plate (i.e. A1-P24)
+  :type i_intPositionNumber: Variable
+  :type o_strPositionText: Variable
+  :return: A boolean of whether the conversion was successful
+  :rtype: Boolean
+
+.. ven:function:: Plate384PositionNumberToPositionText(variable i_strPositionText, variable o_intPositionNumber)
+
+  This function converts position text to position number for a 384 well plate. E.g. if given A1 it will convert it to a 1, if given P1 it will convert it to a 16, etc.
+
+  :params i_strPositionText: The position text to be converted. Will be a string of any of the well identifiers on a 384 well plate (i.e. A1-P24)
+  :params o_intPositionNumber: The position number which will be the output. Any int in the range of 1-384.
+  :type i_intPositionNumber: Variable
+  :type o_strPositionText: Variable
+  :return: A boolean of whether the conversion was successful
+  :rtype: Boolean
+
+.. ven:function:: Plate96PositionNumberToPositionText(variable i_intPositionNumber, variable o_strPositionText)
+
+  This function converts position number to position text for a 96 well plate. E.g. if given a 1 it will convert it to A1, if given an 8 it will convert it to H1, etc.
+
+  :params i_intPositionNumber: The position number to be converted. Any int in the range of 1-96.
+  :params o_strPositionText: The position text which will be the output. Will be a string of any of the well identifiers on a 96 well plate (i.e. A1-H12)
+  :type i_intPositionNumber: Variable
+  :type o_strPositionText: Variable
+  :return: A boolean of whether the conversion was successful
+  :rtype: Boolean
+
+.. ven:function:: Plate96PositionNumberToPositionText(variable i_strPositionText, variable o_intPositionNumber)
+
+  This function converts position text to position number for a 96 well plate. E.g. if given A1 it will convert it to a 1, if given H1 it will convert it to a 8, etc.
+
+  :params i_strPositionText: The position text to be converted. Will be a string of any of the well identifiers on a 96 well plate (i.e. A1-H12)
+  :params o_intPositionNumber: The position number which will be the output. Any int in the range of 1-96.
+  :type i_intPositionNumber: Variable
+  :type o_strPositionText: Variable
+  :return: A boolean of whether the conversion was successful
+  :rtype: Boolean

VenusLibraryDocumentation-DocsForGPT/docs/source/PlateEditor96 - unfinished.rst

@@ -0,0 +1,32 @@
+PlateEditor96
+==========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/PlateEditor96.pkg
+
+This library adds functions which help edit the sequences on a plate dynamically during a method, either with a dialogue or from a csv file. The functions it adds are:
+
+  - :ven:func:`EditPlate96_Custom`
+  - :ven:func:`EditPlate96`
+  - :ven:func:`EditPlate96_with_BarcodesFromCsv`
+  - :ven:func:`EditPlate96_with_BarcodesFromExcelAccess`
+
+.. ven:function:: EditPlate96_Custom(sequence o_SeqEdit, sequence i_OriginalPlateSeq, variable i_message, variable fixed_number, sequence i_forbiddenWellsSeq, sequence i_preSelectionSeq, variable i_Editable)
+
+  This function shows a GUI to select wells in a 96 plate, and returns a sequence sorted A1,B1,C1... with the selection  with addtional options.
+
+  :params o_SeqEdit: The returned plate sequence with the newly selected wells
+  :params i_OriginalPlateSeq: The original input plate sequence which isn't modified
+  :params i_message: Message to be shown in the GUI
+  :params fixed_number: Set this to 0 if you want a free choice of the number of wells, or to >0 if you want a set value of wells to be chosen
+  :params i_forbiddenWellsSeq: Any wells which are unable to be selected
+  :params i_preSelectionSeq: Any wells which are automatically selected
+  :params i_Editable: A boolean determining whether the user is able to (1) select or deselect wells or not (0). With this at 0, the plate editor effectively becomes a GUI displaying updates of which wells are selected. 
+  :type o_SeqEdit: Sequence
+  :type i_OriginalPlateSeq: Sequence
+  :type i_message: Variable
+  :type fixed_number: Variable
+  :type i_forbiddenWellsSeq: Sequence
+  :type i_preSelectionSeq: Sequence
+  :type i_Editable: Boolean
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/RemoveTextDelimitersFromAcsiiTextFile.rst

@@ -0,0 +1,18 @@
+RemoveTextDelimitersFromAsciiTextFile
+===============================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/RemoveTextDelimitersFromAsciiTextFile.pkg
+
+The RemoveTextDelimitersFromAsciiFile library adds a single function which edits a file to remove all delimiters from the Ascii file at the given file path. 
+
+- :ven:func:`RemoveTextDelimitersFromAsciiTextFile`
+
+.. ven:function:: RemoveTextDelimitersFromAsciiTextFile(variable fileName)
+
+  This function removes any text delimiters from the Ascii text file at the specified file path. It edits the file rather than outputting a copy.
+
+  :params fileName: The file path of the text file to be edited
+  :type fileName: Variable
+  :return: Boolean of whether the text file was found (hslTrue) or not found (hslFalse)
+  :rtype: Boolean
+

VenusLibraryDocumentation-DocsForGPT/docs/source/RuntimeErrors.rst

@@ -0,0 +1,752 @@
+Runtime Errors
+========================
+
+.. _RuntimeErrors:
+
+Venus errors
+--------------------
+
+- :ref:`0xa0220001 : No memory <0xa0220001>`
+- :ref:`0xa1230002 : Inserting identifier failed <0xa1230002>`
+- :ref:`0xa1230003 : Identifier not found <0xa1230003>`
+- :ref:`0xa2230004 : L-value not a number <0xa2230004>`
+- :ref:`0xa2230005 : R-value not a number <0xa2230005>`
+- :ref:`0xa1230006 : Not an identifier <0xa1230006>`
+- :ref:`0xa1220007 : Unrecognized token <0xa1220007>`
+- :ref:`0xa1230008 : R-value not bound <0xa1230008>`
+- :ref:`0xa2230009 : Bad number <0xa2230009>`
+- :ref:`0xa123000a : Bad tree <0xa123000a>`
+- :ref:`0xa123000b : Invalid entry <0xa123000b>`
+- :ref:`0xa122000c : Function identifier is protected <0xa122000c>`
+- :ref:`0xa223000d : Underspecified <0xa223000d>`
+- :ref:`0xa2230037 : Overspecified <0xa2230037>`
+- :ref:`0xa123000e : Setting value failed <0xa123000e>`
+- :ref:`0xa123000f : Function identifier not found <0xa123000f>`
+- :ref:`0xa1230010 : Bindings not found <0xa1230010>`
+- :ref:`0xa1230011 : Temporary variable not found <0xa1230011>`
+- :ref:`0xa1230012 : Unknown function type <0xa1230012>`
+- :ref:`0xa2230013 : Unable to find file <0xa2230013>`
+- :ref:`0xa1230014 : Type mismatch <0xa1230014>`
+- :ref:`0xa2230015 : Bad L-value <0xa2230015>`
+- :ref:`0xa2230016 : Bad R-value <0xa2230016>`
+- :ref:`0xa2220017 : Unrecognised type <0xa2220017>`
+- :ref:`0xa1230018 : Bad memory type <0xa1230018>`
+- :ref:`0xa1230019 : Array reference out of bound <0xa1230019>`
+- :ref:`0xa123001a : Bad array identifier type <0xa123001a>`
+- :ref:`0xa123001b : Tag insert failed <0xa123001b>`
+- :ref:`0xa123001c : Dynamic memory identifier not bound <0xa123001c>`
+- :ref:`0xa123001d : Tag identifier not bound <0xa123001d>`
+- :ref:`0xa123001e : Structure reference out of bound <0xa123001e>`
+- :ref:`0xa123001f : Bad tag identifier type <0xa123001f>`
+- :ref:`0xa1230020 : L-value is not a structure identifier <0xa1230020>`
+- :ref:`0xa1230021 : L-value is not an array identifier <0xa1230021>`
+- :ref:`0xa1230022 : Failed to lookup tag identifier in tag table <0xa1230022>`
+- :ref:`0xa1230023 : Signal break <0xa1230023>`
+- :ref:`0xa1230024 : Copy out of bound <0xa1230024>`
+- :ref:`0xa1230025 : Signal return <0xa1230025>`
+- :ref:`0xa2230026 : Array size is not an integer <0xa2230026>`
+- :ref:`0xa1230027 : Failed to copy tag table <0xa1230027>`
+- :ref:`0xa1230029 : Function has not been defined <0xa1230029>`
+- :ref:`0xa123002a : Unable to enter nesting level <0xa123002a>`
+- :ref:`0xa123002b : Unable to exit nesting level <0xa123002b>`
+- :ref:`0xa122002c : No context <0xa122002c>`
+- :ref:`0xa123002d : Failed to read file <0xa123002d>`
+- :ref:`0xa123002e : Failed to create timer <0xa123002e>`
+- :ref:`0xa123002f : Failed to set timer <0xa123002f>`
+- :ref:`0xa1230030 : Failed to wait timer <0xa1230030>`
+- :ref:`0xa1230031 : Failed to create event <0xa1230031>`
+- :ref:`0xa1230032 : Failed to set event <0xa1230032>`
+- :ref:`0xa1230033 : Failed to wait event <0xa1230033>`
+- :ref:`0xa1230034 : Bad argument <0xa1230034>`
+- :ref:`0xa2230035 : Syntax error <0xa2230035>`
+- :ref:`0xa2230036 : Integer divide by zero <0xa2230036>`
+- :ref:`0xa2230038 : Returning address of local variable or temporary <0xa2230038>`
+- :ref:`0xa2230039 <0xa2230039>`
+- :ref:`0xa223003a : Unable to find file <0xa223003a>`
+- :ref:`0xa223003b : File not updatable <0xa223003b>`
+- :ref:`0xa223003c : Recursive call <0xa223003c>`
+- :ref:`0xa223003d : Failed to wait for threads <0xa223003d>`
+- :ref:`0xa223003e : Time-out interval elapsed <0xa223003e>`
+- :ref:`0xa2220044 : Automation type not supported <0xa2220044>`
+- :ref:`0xa1230046 : Bad argument parameter <0xa1230046>`
+- :ref:`0xa123004d : Sequence property not found <0xa123004d>`
+- :ref:`0xa123004e : int64 not supported <0xa123004e>`
+
+HSLUtilLib Errors
+-----------------------------
+
+- :ref:`0xa0000001 : The parameter is incorrect <0x00000001>`
+
+HSLUtilLib2 Errors
+-----------------------------
+
+- :ref:`0xa1630001 : Unexpected error <0xa1630001>`
+- :ref:`0xa1630002 : Create object failed or Invalid parameter <0xa1630002>`
+- :ref:`0xa1630003 : Value check failed: Invalid type <0xa1630003>`
+- :ref:`0xa1630004 : Value check failed: Invalid range <0xa1630004>`
+- :ref:`0xa1630005 : Labware error <0xa1630005>`
+- :ref:`0xa1630006 : Array index not a number <0xa1630006>`
+- :ref:`0xa1630007 : Array index not an integer <0xa1630007>`
+- :ref:`0xa1630008 : Array index must not be negative <0xa1630008>`
+- :ref:`0xa1630009 : Array index must not be greater than array size <0xa1630009>`
+
+Error explanations and advice
+-----------------------------
+
+.. _0xa0220001: 
+
+  **0xa0220001: No memory**
+
+  This error means that the system cannot allocate or access enough memory or disk space for whatever operation causes the error to arise. To fix this, try:
+
+  - Opening task manager and closing down other programs that are using a lot of RAM
+  - Modify the operation to optimise for less memory usage
+  - Increase the amount of RAM that Venus has been allocated
+  - In task manager, go to details, right click the hamilton software and assign priority high
+
+.. _0xa1230002: 
+
+  **0xa1230002: Inserting identifier failed**
+
+  This error means that the parser or executer could not insert the specified identifier into the symbol table. Some examples of how this error can arise are: if the table is corrupted, if the identifier being read causes issues for the parser, or similar. To fix this, try:
+
+  - Replace the identifier with something else temporarily, to determine whether it is the identifier causing the issue or something else
+  - Check to make sure the identifier has all the data associated with it that the symbol table needs. Typically this includes name, type and attributes
+  - Check to make sure the identifier doesn't include any symbols that might interfere with the parser. These can include anything outside of standard ASCII characters from range 0xa0 - 0x7F.
+
+.. _0xa1230003:
+
+  **0xa1230003: Identifier not found**
+
+  This error means that the parser or executer could not find the specified identifier in the symbol table. This usually means something like a sequence or variable has either not been added or has been added but misspelt. To fix this, try:
+
+  - Check what the error says. It should be an error which tells you the name of what it fails to lookup, which is useful for debugging purposes.
+  - Check whether the name given in the error is spelt correctly; if not then that needs correcting
+  - Check whether the name given in the error has been initialised or defined. It may be there, it may be there but misspelt, it may not be there at all. If it isn't there, add it and try again. If it is there but misspelt, rename it to the correct item. 
+  - If the name is there and spelt correctly, make sure that the correct symbol table is being called during the method
+
+.. _0xa2230004: 
+
+  **0xa2230004: L-value not a number**
+
+  This error means that the executor has detected that the left hand side of the expression at the specified line is not a number. The error thrown will usually include the line number from which the error arose; this will be the line number in the HSL code. Look up the error to find whereabouts in the Venus code it corresponds to, but don't fix it in the HSL method editor; otherwise you can only use HSL method editor from that point onwards as Venus only compiles one way med --> hsl. This usually occurs when two values are being added and one of them is not a number but instead a string. To fix this, try:
+
+  - Checking whether you are trying to add two numbers or concatenate two strings, both have similar syntax. 
+  - If trying to add two numbers, check which one is on the left e.g. s in the equation v = s + 1
+  - Make sure the selected number is a number and not a string or similar. You can either convert it to a number manually, or you can input a step into the method which automatically converts strings to their float or int equivalents. This can be performed by the StrFVal function from HSLStrLib.
+  - If trying to concatenate two strings, then the leftmost value is still being stored as a number rather than a string
+  - Use the StrFStr function from HSLStrLib to convert a floating point number into the correpsponding character string before concatenating.
+
+.. _0xa2230005: 
+
+  **0xa2230005: R-value not a number**
+
+  This error means that the executor has detected that the right hand side of the expression at the specified line is not a number. The error thrown will usually include the line number from which the error arose; this will be the line number in the HSL code. Look up the error to find whereabouts in the Venus code it corresponds to, but don't fix it in the HSL method editor; otherwise you can only use HSL method editor from that point onwards as Venus only compiles one way med --> hsl. This usually occurs when two values are being added and one of them is not a number but instead a string. To fix this, try:
+
+  - Checking whether you are trying to add two numbers or concatenate two strings, both have similar syntax. 
+  - If trying to add two numbers, check which one is on the right e.g. 1 in the equation v = s + 1
+  - Make sure the selected number is a number and not a string or similar. You can either convert it to a number manually, or you can input a step into the method which automatically converts strings to their float or int equivalents. This can be performed by the StrFVal function from HSLStrLib.
+  - If trying to concatenate two strings, then the leftmost value is still being stored as a number rather than a string
+  - Use the StrFStr function from HSLStrLib to convert a floating point number into the correpsponding character string before concatenating.
+
+.. _0xa1230006:
+
+  **0xa1230006: Not an identifier**
+
+  This error means that the symbol table entry of the identifier at the specified line is not an identifier. To fix this, try: 
+
+  - Changing the name of the identifier being used. You can also look through the method to confirm that the identifier is being used and that you are not misspelling anything
+
+.. _0xa1220007:
+
+  **0xa1220007: Unrecognized token**
+
+  This error means that the executor detected an unrecognized token. This usually means that what it is trying to parse contains characters that are not allowed. A typical example of this is when a JSON Parser tries to parse HTML, and encounters the \"<\" character. To fix this, try:
+
+  - Identify what code line the error comes from via the HSL code, and then look at that code in Venus. 
+  - Look through the code that the executor is trying to manage and try identify any characters that might not be standard. This includes anything outside of the normal ASCII range of 0xa0 - 0x7F. Remove or replace those characters
+  - Check that any special characters that are part of strings have backslashes in front of them.
+
+.. _0xa1230008:
+
+  **0xa1230008: R-value not bound**
+
+  This error occurs when the R-value in a line is not bound to a valid value. An example would be v = a + b, where b has not been assigned to any value, or has been assigned to a sequence rather than a variable and thus cannot take part in this operation. To fix this, try:
+
+  - Identify what code line the error comes from via the HSL code, and identify what variable is on the right hand side of that line
+  - Check to see what the type of that variable is. If not obvious from reading the code, you can use the StrGetType function from HSLStrLib, or CheckValueType from HSLUtilLib2, or go through and try specific ones such as IsBoolean from HSLUtilLib.
+  - If the variable is the correct type, check to see that it has been assigned to the right value. An easy way to do this is just to add in a step which traces the variable value immediately before the error.
+  - If the variable is the right type and the correct value, check to see what value the line is expecting --> could it be mistakenly expecting a string concatenation instead of a summation.
+
+.. _0xa2230009:
+
+  **0xa2230009: Bad number**
+
+  This error means that the executor detected an error in a number at the specific line. This often occurs if a number is of the wrong format e.g. int rather than flt. To fix this, try:
+
+  - Check what number is causing the error to occur by looking at the line given in the error code. 
+  - Work out what type the line is expecting the number to be --> for example, a loop counter will be expecting an integer rather than a float
+  - Check what type the number causing the error is. This can be done using the CheckValueType from HSLUtilLib2, or the IsFloat or IsInteger functions from HSLUtilLib. 
+  - If unsure, just toggle the number type and see if swapping it from int to flt or vice versa helps. 
+
+.. _0xa123000a: 
+
+  **0xa123000a: Bad tree**
+
+  This error means that the executor detected an error in the structure of the syntax tree.
+
+.. _0xa123000b:
+
+  **0xa123000b: Invalid entry**
+
+  This error means that the executor has detected an invalid symbol table entry. This error usually occurs if there is a non-ASCII character present in the symbol table, and the executor was not the one who inserted the value into the symbol table in the first place. To fix this, try:
+
+  - Work out which characters in the symbol table are invalid
+  - Try to replace those characters with their ASCII equivalents, as well as work out where or why they were added in teh first place
+
+.. _0xa122000c:
+
+  **0xa122000c: Function identifier is protected**
+
+  This error means that the parser or executor detected a protected function identifier in the symbol table at the specified line. This happens if a device is declared in the local scope, for example. To fix this, try:
+
+  - Checking to make sure nothing is in the local scope which shouldn't be
+
+.. _0xa223000d:
+
+  **0xa223000d: Underspecified**
+
+  This error means that the executor detected underspecified formal parameters of a function at the specific line. To fix this, try:
+
+  - Check what line the error gives as the function going wrong, look at that line in HSL and work out the correct location in Venus code
+  - Look at whatever functions are present on that line and check how many input parameters the functions are meant to have vs how many they actually have
+  - Make sure all input parameters exist and are not just empty variables or arrays or sequences.
+
+.. _0xa2230037:
+
+  **0xa2230037: Overspecified**
+
+  This error means that the executor detected overspecified formal parameters ofa  function at the specific line. To fix this, try:
+
+  - Check what line the error gives as the function going wrong, look at that line in HSL and work out the correct location in Venus code
+  - Look at whatever functions are present on that line and check how many input parameters the functions are meant to have vs how many they actually have
+  - Make sure all input parameters exist and are not just empty variables or arrays or sequences.
+
+.. _0xa123000e:
+
+  **0xa123000e: Setting value failed**
+
+  This error means that the executor failed to set the value of a symbol table entry at the specified line. To fix this, try:
+
+  - Check what line the error gives as the function going wrong, look at that line in HSL and work out the correct location in Venus code
+  - See what value is trying to be set within the symbol table; make sure it has no special characters, the correct type and attributes
+
+.. _0xa123000f:
+
+  **0xa123000f: Function identifier not found**
+
+  This error occurs when the executor failed to lookup a function identifier in the symbol table at the specified line. This usually means the function has not been defined properly or has failed to import into the symbol table properly. It can also be the result of a misspelt name at any steps involving it. To fix this, try:
+
+  - See what the name of the function is that isn't being found
+  - Check to see if the function name is spelt correctly
+  - Check to see earlier in the method that the function has been defined and imported successfully into the symbol table
+  - Check to see if this happens everytime this function is called or just this one step. If it happens every time then it is likely a definition or import issue, if only once then it is likely a naming or exporting issue.
+
+.. _0xa1230010:
+
+  **0xa1230010: Bindings not found**
+
+  This error occurs when the executor failed to lookup the value bound to a formal parameter in the symbol table at the line specified. 
+
+.. _0xa1230011:
+
+  **0xa1230011: Temporary variable not found**
+
+  This error occurs when the executor failed to delete the identifier of a temporary variable in the symbol table at the line specified.
+
+.. _0xa1230012:
+
+  **0xa1230012: Unknown function type**
+
+  This error occurs when the executor detects a function which hasn't been defined at the specific line. To fix this, try:
+
+  - Work out which function hasn't been defined based on the line of code which throws the error
+  - Check whether function name is misspelt
+  - Check whether function is defined post calling rather than pre calling
+  - Check whether function has been defined at all
+
+.. _0xa2230013:
+
+  **0xa2230013: Unable to find file**
+
+  This error occurs when the executor can't find the file specified. To fix this, try:
+
+  - Check the line of code to determine what the path of the file is that is nonexistent
+  - Determine whether the path was computer specific and the method has been ported across computers e.g. was the file in C:\\Users\\tchapman and should be in C:\\Users\\Hamilton. To avoid this in the first place, save things in the Hamilton folder of the C:\\Program Files x86 instead. 
+  - Check whether the file has been moved since the path was created
+  - Check whether the file name has been misspelt
+  - If file name is a variable, check to see it has been defined correctly
+
+.. _0xa1230014: 
+
+  **0xa1230014: Type mismatch**
+
+  This error occurs when the executor detects a mismatch between the types of variable fed into a function compared to the defined parameter that the function is meant to have an as input. To fix this, try:
+
+  - Check which function is causing the error
+  - Check what type of input the function is expecting; will hopefully be in the documentation, if not you can delve into the HSL code for that function and see directly
+  - Check what type of variable you are feeding in to the function and confirm it matches the type the function is expecting
+
+.. _0xa2230015:
+
+  **0xa2230015: Bad L-value**
+
+  This error occurs when the left hand side value for an operation is incorrect for the operation. To fix this, try:
+
+  - Check what type of variable the operator is expecting
+  - Check what type of variable you are feeding into the operator equation
+  - This error could be using the wrong operator e.g. & rather than +, or by using the wrong variable type e.g. float rather than int
+
+.. _0xa2230016:
+
+  **0xa2230016: Bad R-value**
+
+    This error occurs when the right hand side value for an operation is incorrect for the operation. To fix this, try:
+
+  - Check what type of variable the operator is expecting
+  - Check what type of variable you are feeding into the operator equation
+  - This error could be using the wrong operator e.g. & rather than +, or by using the wrong variable type e.g. float rather than int
+
+.. _0xa2220017:
+
+  **0xa2220017: Unrecognized type**
+
+  This error occurs when the executor detects an unrecognized storage type at the specified line.
+
+.. _0xa1230018: 
+
+  **0xa1230018: Bad memory type**
+
+  This error occurs when the executor detects a bad memory type for an array at the specified line.
+
+.. _0xa1230019:
+
+  **0xa1230019: Array reference out of bound**
+
+  This error occurs when the executor detects an invalid index for an array at a specified line. To fix this, try:
+
+  - Check the size of the array that is being queried
+  - Check which value from the array you are expecting to call and check what index that value has
+  - Potentially add a step into the method to find that index on a dynamic basis so that you can change the array earlier in the method without messing up that step
+
+.. _0xa123001a:
+
+  **0xa123001a: Bad array identifier type**
+
+  This error occurs when the executor detects an unrecognized storage type for an array identifier at the specified line.
+
+.. _0xa123001b: 
+
+  **0xa123001b: Tag insert failed**
+
+  This error occurs when the executor fails to insert an identifier into the tag table of a structure definition at the specified line.
+
+.. _0xa123001c:
+
+  **0xa123001c: Dynamic memory identifier not bound**
+
+  This error occurs when the executor detected at the specified line an identifier of a dynamic memory object that was not bound to a valid value. This is when a variable or data structures has been allocated at runtime, and has been assigned an incorrect value, such as binding an identifier that is meant to be a variable to a submethod instead. As far as I'm aware, this is only possible to do by editing the HSL code, I don't think the method editor has any functions that allow you to bind identifiers incorrectly, I'm not 100% certain on that though. To fix this, try: 
+
+  - Locate the identifier that is causing the error (should be possible in either the method editor or the hsl method editor)
+  - Confirm what kind of object the identifier is meant to be
+  - Work out what method editor step corresponds to the incorrect HSL code, which is likely to be a block of HSL code inserted directly into the method editor
+  - Correct that code (if you have knowledge of HSL) or replace it with method editor steps that have the same functionality. If you're really attached to the HSL block of code but aren't proficient with HSL, try to make the same function with method editor steps in a separate method, look at the HSL code that generates, and copy that HSL code into the original method as an inserted block of HSL. 
+
+.. _0xa123001d:
+
+  **0xa123001d: Tag identifier not bound**
+
+  This error occurs when the executor detected at the specified line an identifier of a structure tag object that was not bound to a valid value. A structure tag object is a piece of metadata associated with a variable. In this error, a variable is expected to have some sort of tag, but the tag doesn't exist. To fix this, try:
+
+  - Determine which variable the tag is meant to be associated with based on the specified line
+  - From that, work out what kind of tag is meant to be present. This is doable by looking at the HSL code. In the HSL Method Editor Help section, you can go to HSL Reference \> Declaration of Objects \> Declaration of Structure Objects to see what the format of tag declaration is meant to be, and therefore can compare this to the code in the method associated with the object declaration
+  - Add the assignment of the tag in the method editor code, confirming via the HSL that the tag has been assigned correctly. You can also assign the tag via an HSL code insert step.
+
+.. _0xa123001e:
+
+  **0xa123001e: Structure reference out of bound**
+
+  This error occurs when the executor detects a reference to an element of a structure which is outside the allowed range. A few examples of this are integers which are too large or too small, or strings which are too long. To fix this, try:
+
+  - Determine which reference is out of bounds. This should be doable by looking at the HSL code; the error message in the trace file should show you which line is the one causing the problems. 
+  - Locate in the HSL code where the bounds of the identifier have been set; this can usually be done by searching the HSL file for "struct" functions, and then seeing what character(s) follow the "}" character. 
+  - Depending on the requirements of the reference, either adjust the reference bounds assignment to include the target value, or adjust the function which is causing the error to ensure the reference is always within the specified bounds (e.g. splitting or truncating strings, editing loops to only contain correct integers)
+
+.. _0xa123001f:
+
+  **0xa123001f: Bad tag identifier type**
+
+  This error occurs when the identifier of a structure tag object has been assigned to an incorrect type, such as a being assigned a string rather than an integer. To fix this, try:
+
+  - Determine what tag is causing the problem by looking at the HSL code associated with the line specified in the trace file
+  - Identify what type of data the tag is expecting
+  - If the tag is expecting a string rather than an int, locate the assignment and add quotation marks around the assignment
+  - If the tag is expecting an int rather than a string, locate the assignment and either use a function to convert the string to an int or remove the quotation marks around the assignment
+  - If the tag is expecting an int rather than a float or vice versa, locate the assignment and use a function to convert one to the other. 
+  - Functions to convert the variable type are present in the HSLExtensions:Core library
+
+.. _0xa1230020:
+
+  **0xa1230020: L-value is not a structure identifier**
+
+ This error occurs when the executor detects a data reference which is not a structure at the specified line, in the left hand side of the assignment.
+
+.. _0xa1230021:
+
+  **0xa1230021: L-value is not an array identifier**
+
+  This error occurs when the executor detects a data reference which is not an array at the specified line, in the left hand side of the assignment.
+
+.. _0xa1230022: 
+
+  **0xa1230022: Failed to lookup tag identifier in the tag table**
+
+  This error occurs when the executor detects a tag identifier which is not a member of the tag table. To fix this, try:
+
+ - Checking whether your tag is correctly spelled
+ - Attempt to add your tag to the tag table
+ - Change your tag to be one which is present in the tag table already
+
+.. _0xa1230023:
+
+  **0xa1230023: Signal break**
+
+  This error occurs when the executor detects an invalid break statement at the specified line.
+
+.. _0xa1230024:
+
+  **0xa1230024: Copy out of bound**
+
+  This error occurs when the executor detects a structure copy which is out of bound.
+
+.. _0xa1230025:
+
+  **0xa1230025: Signal return**
+
+  This error occurs when the executor detects an invalid return-statement.
+
+.. _0xa2230026:
+
+  **0xa2230026: Array size is not an integer**
+
+  This error occurs when the executer detects an error in the size of an array at the specified line. This is usually if an array is assigned to a float or string by accident. To fix this, try:
+
+  - Check where the size of the array was assigned. If it was done via a calculation (especially a division), it is often assigned a float even when the numbers divide exactly.
+  - If the assignment of size was done via a variable, check to ensure the variable was written as an integer and not as a string
+  - If you can't identify where the mistake is in assignment type, you can try use one of the convert-to-integer functions and see whether that works or whether it throws up a fresh error.
+  - Make sure the array size is positive
+  - Try assigning the array size dynamically, i.e. when declaring the array make it empty, and then add items to it at the end of the array rather than at specific locations
+
+.. _0xa1230027: 
+
+  **0xa1230027: Failed to copy tag table**
+
+  This error occurs when the executor fails to copy the tag table.
+
+.. _0xa1230029:
+
+  **0xa1230029: Function has not been defined**
+
+  This error occurs when a function has not been defined in the library it is being called from. To fix this, try:
+
+  - If you are the author of the target library, open the code in HSL and check whether the function has been defined at all, or if it is only defined in one namespace, or if it has been misspelled, or if it has been incorrectly commented out
+  - If you are not the author of the library but are proficient in HSL, you can do as above, but would be worth making a copy of the library and editing that instead
+  - Otherwise, remove the function from your method and find an alternative way of doing whatever you were aiming to do
+
+.. _0xa123002a: 
+
+  **0xa123002a: Unable to enter nesting level**
+
+  This error occurs when the executor failed to enter the nesting level at the specified line.
+
+.. _0xa123002b:
+
+  **0xa123002b: Unable to exit nesting level**
+
+  This error occurs when the executor failed to exit the nesting level at the specified line.
+
+.. _0xa122002c: 
+
+  **0xa122002c: No context**
+
+  This error occurs when the executor fails to create a new symbol table at the specified line.
+
+.. _0xa123002d:
+
+  **0xa123002d: Failed to read file**
+
+  This error occurs when the executor fails to read a specific file. To fix this, try:
+
+  - Ensure the file path specified is a correct and valid path
+  - Ensure the file you are trying to read exists
+  - Check whether the file has the hidden attribute. If so, you can use the File Handling library to remove that property dynamically during the run, or do it manually in file explorer
+  - Ensure that the file is in a location that Venus has access to
+
+.. _0xa123002e:
+
+  **0xa123002e: Failed to create timer**
+
+  This error occurs when the executor or parser fails to create a timer at the specified line
+
+.. _0xa123002f:
+
+  **0xa123002f: Failed to set timer**
+
+  This error occurs when the executor fails to set a timer at the specified line
+
+.. _0xa1230030:
+
+  **0xa1230030: Failed to wait timer**
+
+  This error occurs when the executor fails to wait for at timer to be signaled at the specified line
+
+.. _0xa1230031:
+
+  **0xa1230031: Failed to create event**
+
+  This error occurs when the parser or executor fails to create an event at the specified line
+
+.. _0xa1230032:
+
+  **0xa1230032: Failed to set event**
+
+  This error occurs when the executor fails to set an event at the specified line
+
+.. _0xa1230033:
+
+  **0xa1230033: Failed to wait event**
+
+  This error occurs when the executor fails to wait for an event to be signaled
+
+.. _0xa1230034:
+
+  **0xa1230034: Bad argument**
+
+  This error occurs when the executor detects an error in the function argument at the specified line. An example of this would be having a File:Set Position command with a non-integer value as the input; as positions can only take integer values. To fix this, try: 
+
+  - Determine from the trace file which line and function are causing these errors
+  - Determine the type of input the function is expecting (e.g. int, str, var)
+  - Determine any bounds the function input has (e.g. max 300uL volume for 300uL tips)
+  - Check your input and see which of the above it doesn't meet
+  - If your input is the right value but the wrong type, there are various functions that can convert variables from one type to another - for example in HSLMthLib you can convert floats to ints, ints to strings, etc.
+
+.. _0xa2230035:
+
+  **0xa2230035: Syntax error**
+
+  This error occurs when the parser detects syntax errors in the method
+
+.. _0xa2230036:
+
+  **0xa2230036: Integer divide by zero**
+
+  This error occurs when the executor detects an integer divide by zero at a specified line. To fix this, try:
+
+  - Determine which variable or integer is being treated as a zero in the calculation
+  - Check that that variable or integer has an assignment step associated with it; without one it will default to zero
+  - Check that the variable is correctly spelled; if incorrectly spelled (compared to its assignment) it will default to zero
+
+.. _0xa2230038:
+
+  **0xa2230038: Returning address of local variable or temporary**
+
+  This error occurs when the executor detects a function returning the address of a local or temporary variable. This causes problems as local variables and temporary variables are destroyed upon function return, so the address returned becomes invalid. To fix this, try:
+
+  - Converting the variable that is being returned to global or task local
+  - Removing the function return value if it isn't essentially
+
+.. _0xa2230039:
+
+  **0xa2230039**
+
+  This error occurs when a library requires an installer to be run before use and the installer hasn't yet been run. An example of this would be the Dynamic Liquid Classes library. To fix this, try:
+
+  - Contact me directly as there is a reasonable chance I have the installer and can send it over
+  - Contact your Hamilton apps specialist
+  - Go into the hsl file for the library, find the author (usually in the final line or at the top commented out) and contact them directly
+
+.. _0xa223003a:
+
+  **0xa223003a: Unable to find file**
+
+  This error occurs when the executor couldn't find the file at the specified line. To fix this, try:
+
+  - Checking that the file isn't a hidden file
+  - Checking that the file exists
+  - Checking that the file is in the location specified in the path
+  - Checking that the path is correct with no spelling mistakes and has double backslashes instead of single
+  - Check that the file is in a location that Venus has access to
+
+.. _0xa223003b:
+
+  **0xa223003b: File not updatable**
+
+  This error occurs when the executor is asked to update a non-updatable file. To fix this, try:
+
+  - Removing the read-only tag of the file, which can either be done manually in file explorer or using the File Handling library
+  - Moving the file to a location that Venus has edit access in (such as to documents instead of Program Files section)
+  - Giving venus the appropriate permissions to edit files in that area
+  - Making sure the file isn't in use by another program or open separately
+
+.. _0xa223003c:
+
+  **0xa223003c: Recursive call**
+
+  This error occurs when the executor detects a recursive or concurrent funtion call. To fix this, try:
+
+  - If the function is one from an HSL library, remove the function from your method and find an alternative way of doing whatever you were trying to do, or edit the HSL file to fix it if you are proficient in HSL
+  - If the recursion is caused by function parameter input, change the parameters to be not that function. If need be you can create two copies of a function and call one from within the other.
+  - If the concurrency is caused by a method fork in which both call the same function, you can either stop the fork or add in a "wait for event" clause to ensure that they trigger sequentially rather than concurrently
+
+.. _0xa223003d:
+
+  **0xa223003d: Failed to wait for thread(s)**
+
+  This error occurs when the executor fails to wait for one or more threads to be signaled. 
+
+.. _0xa223003e:
+
+  **0xa223003e: Time-out interval elapsed**
+
+  This error occurs when the time-out window for a specific function or error elapses without user response. To fix this, try:
+
+  - Ensure that the user is present at the STAR or that there is a way of notifying the user when a time-out dialog pops up
+  - If the dialog is one caused by a function, increase the time-out period of the dialog, or set it to an infinite timeout (usually by setting the timeout to 0)
+
+.. _0xa2220044: 
+
+  **0xa2220044: Automation type not supported**
+
+  This error occurs when there is a reference to an automation function which has a parameter that is not supported.
+
+.. _0xa1230046:
+
+  **80xa1230046: Bad argument parameter**
+
+  This error occurs when the executor detects an error in a function argument at the specified line. To fix this, try:
+
+  - Determine which argument within the function is causing the error
+  - Confirm that the argument is the correct type (e.g. a string of 0 vs an int of 0)
+  - Check that the argument has not been misspelled if it is a variable
+  - Check that the function being called is the correct one
+
+.. _0xa123004d: 
+
+  **0xa123004d: Sequence property not found**
+
+  This error occurs when the sequence property being referenced is not found. To fix this, try:
+
+  - If the sequence is one which is defined in the layout file, go into the layout file and view or edit the sequence properties there
+  - If the sequence is one which is defined during the method, confirm that the step defining the referenced property exists
+  - Confirm that the step defining the referenced property is not commented out, is called in advance of the sequence property being referenced, and is not misspelled
+
+.. _0xa123004e:
+
+  **0xa123004e: Int64 not supported**
+
+  This error occurs when a 64 bit integer is used on certain platforms. To fix this, try:
+
+  - Moving off a windows 2000 platform
+  - Changing the integer to a 32 bit integer
+
+.. _0x00000001:
+
+  **0x00000001: The parameter is incorrect**
+
+ This error occurs when the parameter input into a function is incorrect. To fix this, try:
+
+  - Check that the variable type inputted into a function is correct, for example not an integer instead of a string or float.
+  - Check that the parameter value is within the acceptable range; either length for string or upper and lower limits for int or float or bool
+
+.. _0xa1630001: 
+
+  **0xa1630001: Unexpected error**
+
+  This error occurs when there is an error in an HSLUtilLib2 step which is not covered by any of the other error messages.
+
+.. _0xa1630002: 
+
+  **0xa1630002: Create object failed or Invalid parameter**
+
+  This error is listed as Create Object Failed in the index of HSLUtilLib2, but described as invalid parameter. I'm assuming that the latter is correct, in which case the error occurs when one or more parameters for an HSLUtilLib2 step is invalid. To fix this, try: 
+
+  - Check what parameters the function called is expecting and compare to the ones you're feeding in
+  - Check whether you are feeding in the correct number of parameters
+
+.. _0xa1630003:
+
+  **0xa1630003: Value Check Failed Invalid Type**
+
+  This error occurs when the executor finds a function parameter or read from file that is not of the expected type. To fix this, try:
+
+  - Check what type of parameter you're feeding in to the function or file and make sure it is the expected type. The expected type should be findable in the documentation, if not then it should be findable in the raw HSL code. 
+  - Check that the parameter is actually being fed into the function and that it hasn't been misspelt
+  - Check that the file is present in the right location and hasn't been corrupted or moved to the incorrect place
+
+.. _0xa1630004:
+
+  **0xa1630004: Value Check Failed Invalid Range**
+
+  This error occurs when the executor finds a function parameter or read from file that is not within the expected range. To fix this, try:
+
+  - Check what the expected range of the function or file read. This should be findable in the documentation, but will be in the raw HSL code if not.
+  - Check what the value of the parameter being fed in is.
+  - Check whether the range is due to the parameter being mistakenly high or the function range being mistakenly low.
+
+.. _0xa1630005: 
+
+  **0xa1630005: Labware Error**
+
+  This error occurs when the access of labware based on LabwareID and PositionID causes an error. To fix this, try:
+
+  - Check that the labware or position IDs have been spelt correctly
+  - Check that the layout file for the method is the correct one
+  - Check that the labware still exists on the system deck and hasn't been deleted
+  - Check that the labware file still exists in the system database and hasn't been moved or deleted
+
+.. _0xa1630006:
+
+  **0xa006: Array Index Not A Number**
+
+  This error occurs when the index of the specified array is not a positive integer. To fix this, try:
+
+  - Identify what the index of the array is e.g. is it a float, a negative integer, a string
+  - If the identifier is a numeric string or a float that ends in .0, use a convert to int function
+  - If the array index is something other than that, try to assign it to a positive integer as a key code or unique identifier
+
+.. _0xa1630007:
+
+  **0xa1630007: Array Index Not An Integer**
+
+  This error occurs when the index of the specified array is a float rather than an integer. To fix this, try:
+
+  - If the index is at a .0, use a convert to int function
+  - If the index is at a non .0, either use a floor or ceiling function, or assign a positive integer as a key code or unique identifier
+
+.. _0xa1630008:
+
+  **0xa1630008: Array Index Must Not Be Negative**
+
+    This error occurs when the index of the specified array is less than 1. To fix this, try:
+
+  - If the index is less than 0, perhaps take the absolute value of the index, provided that doesn't clash with another identifier.
+  - If the index is between 0 and 1, or the abs value of the index would clash, work out where you want the value to be within the array. If it needs inserting, use an insert function from one of the array libraries. If it doesn't need inserting, get the length of the array and append the value and assign it that as the index.
+
+.. _0xa1630009:
+
+  **0xa1630009: Array Index Must Not Be Greater Than Array Size**
+
+  This error occurs when the index of the specified array is greater than the size of the array. To fix this, try:
+
+  - Check what the index of the value in the array that you are intending to call is and assign it to that
+  - If the value is not within the array correctly, adjust the size of the array to be one larger and append the value at the end of the array or use an insert function from an array library. 

VenusLibraryDocumentation-DocsForGPT/docs/source/STAR_Channel_Tools.rst

@@ -0,0 +1,595 @@
+STAR_Channel_Tools
+==================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/STAR_Channel_Tools.pkg
+
+The STAR_Channel_Tools submethod library adds a variety of functions which are related to the use of the 8 channels. The following functions are added:
+
+  - :ven:func:`CHAN_ACCESS_Sort1Sequence`
+  - :ven:func:`CHAN_ACCESS_Sort1Sequence1Array`
+  - :ven:func:`CHAN_ACCESS_Sort1Sequence2Arrays`
+  - :ven:func:`CHAN_ACCESS_Sort2Sequences`
+  - :ven:func:`CHAN_ACCESS_Sort2Sequences1Array`
+  - :ven:func:`CHAN_ACCESS_Sort2Sequences2Arrays`
+  - :ven:func:`LIQUID_LEVEL_GetLiquidLevelHeight`
+  - :ven:func:`LIQUID_LEVEL_MeasureLiquidMulti`
+  - :ven:func:`LIQUID_LEVEL_MeasureLiquidSingle`
+  - :ven:func:`LIQUID_LEVEL_ReturnVolumesFromLiquidLevel`
+  - :ven:func:`MOVE_ChannelsToSequencePosition`
+  - :ven:func:`MOVE_ChannelsToSequencePosition_5mL`
+  - :ven:func:`MOVE_CheckPlateWithTwoChannels`
+  - :ven:func:`MOVE_InitDispenseDrive`
+  - :ven:func:`MOVE_InitDispenseDrive_5mL`
+  - :ven:func:`PLATE_STACK_CountPlateStacks`
+  - :ven:func:`QUERY_GetChannelPosition`
+  - :ven:func:`QUERY_GetChannelPosition_5mL`
+  - :ven:func:`QUERY_GetTipPresentState`
+  - :ven:func:`QUERY_GetTipPresentState_5mL`
+  - :ven:func:`QUERY_GetTipVolume`
+  - :ven:func:`QUERY_GetTIpVolume_5mL`
+  - :ven:func:`SPLIT_WELLS_AddContainersToWell`
+  - :ven:func:`SPLIT_WELLS_RemoveContainers`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsToTravelLanes`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsToTravelLanes_5mL`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsToYPosition`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsToYPosition_5mL`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsWithTravelLanes`
+  - :ven:func:`TRAVEL_LANES_MoveChannelsWithTravelLanes_5mL`
+  - :ven:func:`TRAVEL_LANES_SingleSource_ChannelDisplacement`
+  - :ven:func:`TRAVEL_LANES_SingleSource_ChannelDisplacement_5mL`
+
+..  ven:function:: CHAN_ACCESS_Sort1Sequence(device ML_STAR, sequence io_Sequence_to_Sort, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, variable o_Channel_Pattern)
+
+  This submethod takes an input sequence and sorts it based on the input parameters of labware, position, and raster. Once sorted, the submethod will choose a position that the current channel can access up to the maximum. If the current channel cannot access the position, it will skip it and move to the next available position. If the current cannot access any more positions, that channel will be skipped. Make sure the channel use setting is set to "All Sequence Positions" in the pipettting step, otherwise the sequence and channel pattern will not line up.
+
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown. 
+  :params io_Sequence_to_Sort: The input sequence to be sorted.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted sorted sequence for the pipetting step
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+.. ven:function:: CHAN_ACCESS_Sort1Sequence1Array(device ML_STAR, sequence io_Sequence_to_Sort, array io_Array_of_Variables, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, array o_Sorted_Array, variable o_Channel_Pattern)
+
+  This submethod takes in input sequence and sorts it by the conditions given below.  After sorting, the submethod will choose a position that the current channel can access up to the maximum.  If the current channel cannot access the position, it wil skip it and move to the next available position.  If the current channel cannot access any more positions, that channel will be skipped.  The array will be sorted with the sequence.  The array and the sequence must be the same size. Make sure the channel use setting is set to "All sequence positions" otherwise the sequence and channel pattern will not line up.
+
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown.
+  :params io_Sequence_to_Sort: The input sequence to be sorted.
+  :params io_Array_of_Variables: The array to be sorted with the sequence. Used positions will be removed from the array.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted sorted sequence for the pipetting step
+  :params o_Sorted_Array: The outputted sorted array which matches the sequence
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type io_Array_of_Variables: Array
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Sorted_Array: Array
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+.. ven:function:: CHAN_ACCESS_Sort1Sequence2Arrays(device ML_STAR, sequence io_Sequence_to_Sort, array io_Array_of_Variables, array io_Array_of_Variables2, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, array o_Sorted_Array, array o_Sorted_Array2, variable o_Channel_Pattern)
+
+  This submethod takes in input sequence and sorts it by the conditions given below.  After sorting, the submethod will choose a position that the current channel can access up to the maximum.  If the current channel cannot access the position, it wil skip it and move to the next available position.  If the current channel cannot access any more positions, that channel will be skipped.  The arrays will be sorted with the sequence.  The arrays and the sequence must be the same size. Make sure the channel use setting is set to "All sequence positions" otherwise the sequence and channel pattern will not line up.
+
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown.
+  :params io_Sequence_to_Sort: The input sequence to be sorted.
+  :params io_Array_of_Variables: The first array to be sorted with the sequence. Used positions will be removed from the array.
+  :params io_Array_of_Variables2: The second array to be sorted with the sequence. Used positions will be removed from the array.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted sorted sequence for the pipetting step
+  :params o_Sorted_Array: The outputted sorted first array which matches the sequence
+  :params o_Sorted_Array2: The outputted sorted second array which matches the sequence
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type io_Array_of_Variables: Array
+  :type io_Array_of_Variables2: Array
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Sorted_Array: Array
+  :type o_Sorted_Array2: Array
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+..  ven:function:: CHAN_ACCESS_Sort2Sequences(device ML_STAR, sequence io_Sequence_to_Sort, sequence io_Sequence_to_Sort2, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, sequence o_Sorted_Sequence2, variable o_Channel_Pattern)
+
+  This sub method takes the in input sequences and sorts them by the conditions given below.  After sorting, the sub will choose a position that the current channel can access in both sequence positions up to the maximum.  If the current channel cannot access the positions, it wil skip it and move to the next available position.  If the current channel cannot access any more positions, that channel will be skipped. Make sure the channel use setting is set to "All sequence positions" otherwise the sequence and channel pattern will not line up. The first sequence is the driving sequence and the second sequence will be adjusted by the first sort.
+ 
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown. 
+  :params io_Sequence_to_Sort: The first input sequence to be sorted.
+  :params io_Sequence_to_Sort2: The second input sequence to be sorted.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted second sorted sequence for the pipetting step
+  :params o_Sorted_Sequence2: The outputted second sorted sequence for the pipetting step
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type io_Sequence_to_Sort2: Sequence
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Sorted_Sequence2: Sequence  
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+.. ven:function:: CHAN_ACCESS_Sort2Sequences1Array(device ML_STAR, sequence io_Sequence_to_Sort, sequence io_Sequence_to_Sort2, array io_Array_of_Variables, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, sequence o_Sorted_Sequence2, array o_Sorted_Array, variable o_Channel_Pattern)
+
+  This sub method takes the in input sequences and sorts them by the conditions given below.  After sorting, the sub will choose a position that the current channel can access in both sequence positions up to the maximum.  If the current channel cannot access the positions, it wil skip it and move to the next available position.  If the current channel cannot access any more positions, that channel will be skipped. Make sure the channel use setting is set to "All sequence positions" otherwise the sequence and channel pattern will not line up. The first sequence is the driving sequence and the second sequence will be adjusted by the first sort.
+ 
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown. 
+  :params io_Sequence_to_Sort: The first input sequence to be sorted.
+  :params io_Sequence_to_Sort2: The second input sequence to be sorted.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted second sorted sequence for the pipetting step
+  :params o_Sorted_Sequence2: The outputted second sorted sequence for the pipetting step
+  :params o_Sorted_Array: The sorted array. The array will be the size of the maximum channel.
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type io_Sequence_to_Sort2: Sequence
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Sorted_Sequence2: Sequence  
+  :type o_Sorted_Array: Array
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+.. ven:function:: CHAN_ACCESS_Sort2Sequences2Arrays(device ML_STAR, sequence io_Sequence_to_Sort, sequence io_Sequence_to_Sort2, array io_Array_of_Variables, array io_Array_of_Variables2, variable i_Channel_Type, boolean i_Sort_by_Labware, boolean i_Sort_by_XY, boolean i_Sort_for_Channel_Raster, variable i_Max_Channel, sequence o_Sorted_Sequence, sequence o_Sorted_Sequence2, array o_Sorted_Array, array o_Sorted_Array2, variable o_Channel_Pattern)
+
+  This sub method takes the in input sequences and sorts them by the conditions given below.  After sorting, the sub will choose a position that the current channel can access in both sequence positions up to the maximum.  If the current channel cannot access the positions, it wil skip it and move to the next available position.  If the current channel cannot access any more positions, that channel will be skipped. Make sure the channel use setting is set to "All sequence positions" otherwise the sequence and channel pattern will not line up. The first sequence is the driving sequence and the second sequence will be adjusted by the first sort.
+ 
+  :params ML_STAR: The ML_STAR itself, which will be the only option in the dropdown. 
+  :params io_Sequence_to_Sort: The first input sequence to be sorted. This positions removed will be removed from this sequence.
+  :params io_Sequence_to_Sort2: The second input sequence to be sorted. The positions used will be removed from this sequence.
+  :params io_Array_of_Variables: The input array of variables which will be sorted with the first sequence. The positions used will be removed from the array.
+  :params io_Array_of_Variables2: The input array of variables which will be sorted with the second sequence. The positions used will be removed from the array.
+  :params i_Channel_Type: The channel type associated with the pipetting step (1mL, 5mL, labware handler). 0 = 1mL, 1 = 5mL, 2 = Labware handler.
+  :params i_Sort_by_Labware: A boolean determining whether the sequence is to be sorted by labware in ascending order
+  :params i_Sort_by_XY: A boolean determining whether the sequence is to be sorted by position (X ascending, Y descending)
+  :params i_Sort_for_Channel_Raster: A boolean determining whether the next position will be at least the raster distance unless no other positions are available
+  :params i_Max_Channel: The maximum channel that you want to be used from 1 to 16. 0 turns this option off and the maximum number of channels will be used. 
+  :params o_Sorted_Sequence: The outputted second sorted sequence for the pipetting step
+  :params o_Sorted_Sequence2: The outputted second sorted sequence for the pipetting step
+  :params o_Sorted_Array: The sorted array. The array will be the size of the maximum channel.
+  :params o_Sorted_Array2: The second sorted array. The array will be the size of the maximum channel.
+  :params o_Channel_Pattern: The outputted channel pattern for the pipetting step
+  :type ML_STAR: Device
+  :type io_Sequence_to_Sort: Sequence
+  :type io_Sequence_to_Sort2: Sequence
+  :type i_Channel_Type: Variable
+  :type i_Sort_by_Labware: Boolean
+  :type i_Sort_by_XY: Boolean
+  :type i_Sort_for_Channel_Raster: Boolean
+  :type i_Max_Channel: Variable
+  :type o_Sorted_Sequence: Sequence
+  :type o_Sorted_Sequence2: Sequence  
+  :type o_Sorted_Array: Array
+  :type o_Sorted_Array2: Array
+  :type o_Channel_Pattern: Variable
+  :return: The number of sequence positions remaining in the sequence
+  :rtype: Variable
+
+.. ven:function:: LIQUID_LEVEL_GetLiquidLevelHeight(device ML_STAR, variable i_str_LiquidLevelReturn, sequence i_seq_Labware, variable i_int_Channel, variable o_flt_LiquidHeight)
+
+  This function will return the liquid level height relative to the container bottem.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown.
+  :params i_str_LiquidLevelReturn: The return value of the liquid level detect from the pipetting step. 
+  :params i_seq_Labware: The input sequence from which the height is to be determined
+  :params i_int_Channel: The channel which will be used to determine the liquid level height
+  :params o_flt_LiquidHeight: The detected liquid level height
+  :type ML_STAR: Device
+  :type i_str_LiquidLevelReturn: Variable
+  :type i_seq_Labware: Sequence
+  :type i_int_Channel: Integer
+  :type o_flt_LiquidHeight: Float
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: LIQUID_LEVEL_MeasureLiquidMulti(device ML_STAR, array i_arrseq_FullReservoirSequences, sequence i_seq_TipsToUse, sequence i_seq_TipWaste, variable i_str_TipCounter, variable i_int_LLD_Sensitivity, variable i_bool_ConvertTouL, array o_arr_VolumesMeasured)
+
+  This function will pick up the desired tips and will measure the liquid level at the center most well of the desired reservoirs and will return the volumes in uL. Ensure the sequence used for the reservoir contains the FULL number of positions of the reservoir, otherwise volume estimation will be incomplete! The tip types supported are: 50uL Filter, 50uL, 300uL Filter, 300uL, 1000uL Filter, and 1000uL.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown.
+  :params i_arrseq_FullReservoirSequences: The array of full reservoir sequences to be checked.
+  :params i_seq_TipsToUse: The sequence of the tips to be used to measure the liquid level.
+  :params i_seq_TipWaste: The sequence of the waste used to eject the tips.
+  :params i_str_TipCounter: The tip counter to be used for the tips on pickup. Place "" if no tip counter will be used.
+  :params i_int_LLD_Sensitivity: Integer representing the liquid level sensitivity to be used. 1 is very high, 4 is low, 5 is from labware definition.
+  :params i_bool_ConvertTouL: Boolean determining whether it converts to uL (hslTrue) or stays as mL (hslFalse).
+  :params o_arr_VolumesMeasured: The array of volumes that were measured.
+  :type ML_STAR: Device
+  :type i_arrseq_FullReservoirSequences: Array
+  :type i_seq_TipsToUse: Sequence
+  :type i_seq_TipWaste: Sequence
+  :type i_str_TipCounter: Variable
+  :type i_int_LLD_Sensitivity: Variable
+  :type i_bool_ConvertTouL: Boolean
+  :type o_arr_VolumesMeasured: Array
+  :return: Whether the measurement has been successful or not
+  :rtype: Boolean
+
+.. ven:function:: LIQUID_LEVEL_MeasureLiquidSingle(device ML_STAR, sequence i_seq_FullReservoirSequence, sequence i_seq_TipsToUse, sequence i_seq_TipWaste, variable i_str_TipCounter, variable i_bool_IncrementTipSequence, variable i_int_LLD_Sensitivity, variable i_bool_ConvertTouL, variable o_flt_VolumeMeasured)
+
+  This function will pick up the desired tip and will measure the liquid level at the center most well of the desired reservoir and will return the volume in uL. Ensure the sequence used for the reservoir contains the FULL number of positions of the reservoir, otherwise volume estimation will be incomplete! The tip types supported are: 50uL Filter, 50uL, 300uL Filter, 300uL, 1000uL Filter, and 1000uL.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown.
+  :params i_seq_FullReservoirSequences: The full reservoir sequence to be checked.
+  :params i_seq_TipsToUse: The sequence of the tips to be used to measure the liquid level.
+  :params i_seq_TipWaste: The sequence of the waste used to eject the tips.
+  :params i_str_TipCounter: The tip counter to be used for the tips on pickup. Place "" if no tip counter will be used.
+  :params i_bool_IncrementTipSequence: Boolean determining whether the tip sequence should be incremented after pickup or not.
+  :params i_int_LLD_Sensitivity: Integer representing the liquid level sensitivity to be used. 1 is very high, 4 is low, 5 is from labware definition.
+  :params i_bool_ConvertTouL: Boolean determining whether it converts to uL (hslTrue) or stays as mL (hslFalse).
+  :params o_flt_VolumeMeasured: A float of the volume that was measured.
+  :type ML_STAR: Device
+  :type i_seq_FullReservoirSequences: Sequence
+  :type i_seq_TipsToUse: Sequence
+  :type i_seq_TipWaste: Sequence
+  :type i_str_TipCounter: Variable
+  :type i_bool_IncrementTipSequence: Boolean
+  :type i_int_LLD_Sensitivity: Variable
+  :type i_bool_ConvertTouL: Boolean
+  :type o_flt_VolumeMeasured: Float
+  :return: Whether the measurement has been successful or not
+  :rtype: Boolean
+
+.. ven:function:: LIQUID_LEVEL_ReturnVolumesFromLiquidLevel(device ML_STAR, variable i_str_PipettingReturn, variable i_str_LiquidLevelReturn, variable i_bool_ConvertTouL, array o_arr_VolumesMeasured)
+
+  This function will return the volumes that were measured from a previous aspiration step.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_str_PipettingReturn: The return value of the pipetting step to measure liquid level
+  :params i_str_LiquidLevelReturn: The return value of the liquid level detect
+  :params i_bool_ConvertTouL: Boolean determining whether it converts to uL (hslTrue) or stays as mL (hslFalse)
+  :params o_arr_VolumesMeasured: An array of the volumes which were measured for each channel
+  :type ML_STAR: Device
+  :type i_str_PipettingReturn: Variable
+  :type i_str_LiquidLevelReturn: Variable
+  :type i_bool_ConvertTouL: Boolean
+  :type o_arr_VolumesMeasured: Array
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: MOVE_ChannelsToSequencePosition(device ML_STAR, variable i_str_ChPattern, sequence i_seq_Positions, variable i_flt_ZHeight)
+
+  This function moves the 1mL channels to set positions. This function will only move the channels that are activated by the channel pattern.  The positions in the sequence will skip over the positions where the channel is turned off.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_str_ChPattern: The channel pattern of the pipettes to move  
+  :params i_seq_Positions: The X Y positions to move the channels to
+  :params i_flt_ZHeight: The Z positions to end the channels in
+  :type ML_STAR: Device
+  :type i_str_ChPattern: Variable
+  :type i_seq_Positions: Sequence
+  :type i_flt_ZHeight: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: MOVE_ChannelsToSequencePosition_5mL(device ML_STAR, variable i_str_ChPattern, sequence i_seq_Positions, variable i_flt_ZHeight)
+
+  This function moves the 5mL channels to set positions. This function will only move the channels that are activated by the channel pattern.  The positions in the sequence will skip over the positions where the channel is turned off.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_str_ChPattern: The channel pattern of the pipettes to move  
+  :params i_seq_Positions: The X Y positions to move the channels to
+  :params i_flt_ZHeight: The Z positions to end the channels in
+  :type ML_STAR: Device
+  :type i_str_ChPattern: Variable
+  :type i_seq_Positions: Sequence
+  :type i_flt_ZHeight: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: MOVE_CheckPlateWithTwoChannels(device ML_STAR, variable i_int_FrontMostChannel, sequence i_seq_PlateToCheck, variable i_flt_TapWidth)
+
+  This function will take the front most channel and the channel behind it to tap the labware at the sequence position.  This function requires both channels to either have a tip or tool loaded on them before calling.  
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_FrontMostChannel: The front-most channel being used to check plates
+  :params i_seq_PlateToCheck: The sequence position to perform a tap to check for plate existence
+  :params i_flt_TapWidth: The distance in mm for the channels to be separated before tapping
+  :type ML_STAR: Device
+  :type i_int_FrontMostChannel: Variable
+  :type i_seq_PlateToCheck: Sequence
+  :type i_flt_TapWidth: Variable
+  :return: Boolean determining whether plate was found (hslTrue) or not (hslFalse)
+  :rtype: Boolean
+
+.. ven:function:: MOVE_InitDispenseDrive(device ML_STAR, variable i_int_ChannelNumber)
+
+  This function moves the dispense drive for the specified 1mL channel to its home position
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChannelNumber: The channel to initialise the dispense drive
+  :type ML_STAR: Device
+  :type i_int_ChannelNumber: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: MOVE_InitDispenseDrive_5mL(device ML_STAR, variable i_int_ChannelNumber)
+
+  This function moves the dispense drive for the specified 5mL channel to its home position
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChannelNumber: The channel to initialise the dispense drive
+  :type ML_STAR: Device
+  :type i_int_ChannelNumber: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: PLATE_STACK_CountPlateStacks(device ML_STAR, sequence i_seq_PlateStack_Full, sequence o_seq_PlateStack_Count, variable o_int_PlateCount)
+
+  This function will use the channels to measure the number of plates in a plate stack
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_PlateStack_Full: The full sequence of the plate stack to measure
+  :params o_seq_PlateStack_Count: The sequence of the plate stack measured
+  :params o_int_PlateCount: The total number of plates measured in the plate stack
+  :type ML_STAR: Device
+  :type i_seq_PlateStack_Full: Sequence
+  :type o_seq_PlateStack_Count: Sequence
+  :type o_int_PlateCount: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetChannelPosition(device ML_STAR, variable i_int_ChNumber, variable o_flt_XCoord, variable o_flt_YCoord, variable o_flt_ZCoord)
+
+  This function will return the current coordinate of the specified 1mL channel
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel whose position is being checked
+  :params o_flt_XCoord: The X coordinate of the channel
+  :params o_flt_YCoord: The Y coordinate of the channel
+  :params o_flt_ZCoord: The Z coordinate of the channel
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_flt_XCoord: Variable
+  :type o_flt_YCoord: Variable
+  :type o_flt_ZCoord: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetChannelPosition_5mL(device ML_STAR, variable i_int_ChNumber, variable o_flt_XCoord, variable o_flt_YCoord, variable o_flt_ZCoord)
+
+  This function will return the current coordinate of the specified 5mL channel
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel whose position is being checked
+  :params o_flt_XCoord: The X coordinate of the channel
+  :params o_flt_YCoord: The Y coordinate of the channel
+  :params o_flt_ZCoord: The Z coordinate of the channel
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_flt_XCoord: Variable
+  :type o_flt_YCoord: Variable
+  :type o_flt_ZCoord: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetTipPresentState(device ML_STAR, variable i_int_ChNumber, variable o_bln_TipPresent)
+
+  This function outputs true if a tip is loaded and false if a tip is not loaded on the specified 1mL channel
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel which is being checked
+  :params o_bln_TipPresent: A boolean output of whether the tip is present (hslTrue) or not (hslFalse)
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_bln_TipPresent: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetTipPresentState_5mL(device ML_STAR, variable i_int_ChNumber, variable o_bln_TipPresent)
+
+  This function outputs true if a tip is loaded and false if a tip is not loaded on the specified 5mL channel
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel which is being checked
+  :params o_bln_TipPresent: A boolean output of whether the tip is present (hslTrue) or not (hslFalse)
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_bln_TipPresent: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetTipVolume(device ML_STAR, variable i_int_ChNumber, variable o_flt_MaxVolume, variable o_flt_CurrentChannelVolume)
+
+  This function queries the specified 1mL channel to get the max and the current channel volume.  This volume includes the air gap and the conversion made by the correction curve.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel which is being checked
+  :params o_flt_MaxVolume: The maximum volume of the channel
+  :params o_flt_CurrentChannelVolume: The current volume in the channel
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_flt_MaxVolume: Variable
+  :type o_flt_CurrentChannelVolume: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: QUERY_GetTipVolume(device ML_STAR, variable i_int_ChNumber, variable o_flt_MaxVolume, variable o_flt_CurrentChannelVolume)
+
+  This function queries the specified 5mL channel to get the max and the current channel volume.  This volume includes the air gap and the conversion made by the correction curve.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_int_ChNumber: The number of the channel which is being checked
+  :params o_flt_MaxVolume: The maximum volume of the channel
+  :params o_flt_CurrentChannelVolume: The current volume in the channel
+  :type ML_STAR: Device
+  :type i_int_ChNumber: Variable
+  :type o_flt_MaxVolume: Variable
+  :type o_flt_CurrentChannelVolume: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: SPLIT_WELLS_AddContainersToWell(device ML_STAR, sequence i_seq_SequenceToSplit, variable i_int_SequenceIndex, variable i_int_MaxSplitNumber, sequence io_seq_SplitSequence)
+
+  This function will split a well into a sequence of multiple containers, each of which can be aspirated from individually. 
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_SequenceToSplit: The sequence that contains the well to be split into multiple containers
+  :params i_int_SequenceIndex: The index of the sequence that is to be split into multiple containers
+  :params i_int_MaxSplitNumber: The number of times that the selected container will be split. Won't exceed the width of the well
+  :params io_seq_SplitSequence: The sequence containing the split wells. Will append to the end of the sequence. 
+  :type ML_STAR: Device
+  :type i_seq_SequenceToSplit: Sequence
+  :type i_int_SequenceIndex: Variable
+  :type i_int_MaxSplitNumber: Variable
+  :type io_seq_SplitSequence: Sequence
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: SPLIT_WELLS_Remove_Containers(device ML_STAR, variable i_bool_UpdateVolumes)
+
+  This function will remove the containers added by the split wells function
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_bool_UpdateVolume: A boolean determining whether to update the split source volume with the volume set in sample tracking. 
+  :type ML_STAR: Device
+  :type i_bool_UpdateVolume: Boolean
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsToTravelLanes(device ML_STAR)
+
+  This function will move the 1mL channels to the travel lanes
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsToTravelLanes_5mL(device ML_STAR)
+
+  This function will move the 5mL channels to the travel lanes
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :type ML_STAR: Device
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsToYPosition(device ML_STAR, sequence i_seq_TargetSequence, variable i_flt_XOffsetFromOrigin)
+
+  Parameters include the Instrument, a destination sequence, and whether or not a shift in the x-direction is wanted before moving the 1mL channels in y-direction (to doubly ensure no crossver of open wells).  Channels will be moved to their Y coordinates at the X origin of the next labware in the sequence plus the X offset. The channels will move to the current position of the input Sequence.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_TargetSequence: The sequence to move the channels to
+  :params i_flt_XOffsetFromOrigin: The distance from the plate's origin to start the channel approach
+  :type ML_STAR: Device
+  :type i_seq_TargetSequence: Sequence
+  :type i_flt_XOffsetFromOrigin: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsToYPosition_5mL(device ML_STAR, sequence i_seq_TargetSequence, variable i_flt_XOffsetFromOrigin)
+
+  Parameters include the Instrument, a destination sequence, and whether or not a shift in the x-direction is wanted before moving the 5mL channels in y-direction (to doubly ensure no crossver of open wells).  Channels will be moved to their Y coordinates at the X origin of the next labware in the sequence plus the X offset. The channels will move to the current position of the input Sequence.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_TargetSequence: The sequence to move the channels to
+  :params i_flt_XOffsetFromOrigin: The distance from the plate's origin to start the channel approach
+  :type ML_STAR: Device
+  :type i_seq_TargetSequence: Sequence
+  :type i_flt_XOffsetFromOrigin: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsWithTravelLanes(device ML_STAR, sequence i_seq_TargetSequence, variable i_flt_XOffsetFromOrigin)
+
+  This command is designed to shift all the 1mL channels on the instrument to either the front and/or the back of the instrument in a layout that ensures tips will not crossover any carriers. Parameters include the Instrument, a destination sequence, and whether or not a shift in the x-direction is wanted before moving the channels in y-direction (to doubly ensure no crossver of open wells).  Channels will be moved to their Y coordinates at the X origin of the next labware in the sequence plus the X offset. The channels will move to the current position of the input Sequence.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_TargetSequence: The sequence to move the channels to
+  :params i_flt_XOffsetFromOrigin: The distance from the plate's origin to start the channel approach
+  :type ML_STAR: Device
+  :type i_seq_TargetSequence: Sequence
+  :type i_flt_XOffsetFromOrigin: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_MoveChannelsWithTravelLanes_5mL(device ML_STAR, sequence i_seq_TargetSequence, variable i_flt_XOffsetFromOrigin)
+
+  This command is designed to shift all the 5mL channels on the instrument to either the front and/or the back of the instrument in a layout that ensures tips will not crossover any carriers. Parameters include the Instrument, a destination sequence, and whether or not a shift in the x-direction is wanted before moving the channels in y-direction (to doubly ensure no crossver of open wells).  Channels will be moved to their Y coordinates at the X origin of the next labware in the sequence plus the X offset. The channels will move to the current position of the input Sequence.
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_seq_TargetSequence: The sequence to move the channels to
+  :params i_flt_XOffsetFromOrigin: The distance from the plate's origin to start the channel approach
+  :type ML_STAR: Device
+  :type i_seq_TargetSequence: Sequence
+  :type i_flt_XOffsetFromOrigin: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_SingleSource_ChannelDisplacement(device ML_STAR, variable i_strStepReturn)
+
+  This command is designed to move unused 1mL channels to the back of the instrument when pipetting one well at a time while more than one channel has tips/liquid. It requires the Instrument type and Step Return variable from the Aspirate/Dispense step (this is used to determine which channel needs to be moved).
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_strStepReturn: The bound step return from given desired pipetting step
+  :type ML_STAR: Device
+  :type i_strStepReturn: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TRAVEL_LANES_SingleSource_ChannelDisplacement_5mL(device ML_STAR, variable i_strStepReturn)
+
+  This command is designed to move unused 5mL channels to the back of the instrument when pipetting one well at a time while more than one channel has tips/liquid. It requires the Instrument type and Step Return variable from the Aspirate/Dispense step (this is used to determine which channel needs to be moved).
+
+  :params ML_STAR: The ML_STAR itself, will be the only option in the dropdown
+  :params i_strStepReturn: The bound step return from given desired pipetting step
+  :type ML_STAR: Device
+  :type i_strStepReturn: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/StrTokenize.rst

@@ -0,0 +1,23 @@
+StrTokenize
+=====================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/StrTokenize.pkg
+
+The string tokenize library allows you to split a string into an array based on delimiters. It adds one function:
+
+- :ven:func:`StrTokenize`
+
+.. ven:function:: StrTokenize(variable strIn, variable strDelimiter, array arrTokens, boolean bAttendEmptyTokens)
+
+	This function takes the input string and splits it at any point where it finds the specified delimiter, returning the substrings as members of an array. Can be told to add empty strings or not (occurs when the delimiter appears twice in a row).
+
+	:params strIn: The input string to be split
+	:params strDelimiter: The character to be used as the delimiter
+	:params arrTokens: The output array of split-substrings
+	:params bAttendEmptyTokens: Boolean determining whether to include empty substrings or not in the array
+	:type strIn: Variable
+	:type strDelimiter: Variable
+	:type arrTokens: Array
+	:type bAttendEmptyTokens: Variable
+	:return: None
+	:rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/String.rst

@@ -0,0 +1,83 @@
+String (from HSLExtensions)
+===================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/String.pkg
+
+The String library from HSLExtensions adds a few functions to facilitate easier manipulation of strings. It adds the following functions:
+
+  - :ven:func:`ConvertToAsciiArray`
+  - :ven:func:`ConvertToCharArray`
+  - :ven:func:`FromAsciiArray`
+  - :ven:func:`Join`
+  - :ven:func:`JoinWithDelimiter`
+  - :ven:func:`Split`
+  - :ven:func:`Trim`
+
+.. ven:function:: ConvertToAsciiArray(variable i_strValue)
+
+  This function converts the input string into an array with the regarding ASCII codes. If the input parameter is not a string the function returns an empty array.
+
+  :params i_strValue: The input string to be converted into an array
+  :type i_strValue: Variable
+  :return: An array of ASCII codes, or an empty array if the input parameter is not a string
+  :rtype: Array
+
+.. ven:function:: ConvertToCharArray(variable i_strValue)
+
+  This function converts the input string into an array with the regarding characters. If the input parameter is not a string the function returns an empty array.
+
+  :params i_strValue: The input string to be converted into an array
+  :type i_strValue: Variable
+  :return: An array of characters (strings with length 1), or an empty array if the input parameter is not a string
+  :rtype: Array
+
+.. ven:function:: FromAsciiArray(array i_arrAsciiValues)
+
+  This function converts an input array with ASCII codes into a string. If the input parameter is not an array with ASCII codes, the function returns an empty string.
+
+  :params i_arrAsciiValues: The input array of ASCII codes to be converted into a string
+  :type i_arrAsciiValues: Array
+  :return: The output string formed by the concatenation of the converted versions of the ASCII codes. An empty string if the input parameter is not an array with ASCII codes.
+  :rtype: Variable
+
+.. ven:function:: Join(array i_arrValues)
+
+  This function joins an array of strings into a single string. Can be used to concatenate any number of strings into a single one. If the input parameter is not an array with strings, the function returns an empty string.
+
+  :params i_arrValues: The array of strings to be concatenated
+  :type i_arrValues: Array
+  :return: The concatenated form of all the strings in the array, or an empty string if the input parameter is not an array of strings
+  :rtype: Variable
+
+.. ven:function:: JoinWithDelimiter(array i_arrValues, variable i_strDelimiter)
+
+  This function joins an array of strings into a single string and adds a delimiter between each substring. If the input parameter is not an array with strings, the function returns an empty string.
+
+  :params i_arrValues: The input array of strings to be concatenated
+  :params i_strDelimiter: The delimiter to be inserted between each substring
+  :type i_arrValues: Array
+  :type i_strDelimiter: Variable
+  :return: The concatenated strings from the array, with delimiters between each substring. An empty string if the input parameter is not an array of strings.
+  :rtype: Variable
+
+.. ven:function:: Split(variable i_strValue, variable i_strDelimiter, variable i_bTrimWhitespaces)
+
+  This function splits a string into substrings, forming an array of strings. The input string is split based on a delimiter that the user inputs. 
+
+  :params i_strValue: The input string to be split into substrings
+  :params i_strDelimiter: The delimiter to be used to split the string
+  :params i_bTrimWhitespaces: Boolean determining whether leading and trailing whitespaces will be removed or not
+  :type i_strValue: Variable
+  :type i_strDelimiter: Variable
+  :type i_bTrimWhitespaces: Boolean
+  :return: An array of strings containing each substring formed from splitting the original string
+  :rtype: Array
+
+.. ven:function:: Trim(variable i_strValue)
+
+  This function trims leading and trailing whitespace characters from the input string. If the input parameter is not a string the function returns an empty string.
+
+  :params i_strValue: The input string to trim
+  :type i_strValue: Variable
+  :return: The trimmed string
+  :rtype: Variable

VenusLibraryDocumentation-DocsForGPT/docs/source/SyntaxErrors.rst

@@ -0,0 +1,97 @@
+Syntax Errors
+=========================
+
+Syntax errors will show up during the analysis of the method and should prevent the method from running. The error code for a syntax error is 4 digits long and should show up along with the line of the HSL file causing the syntax error, whether that is the method or the library. This will then be followed by a line with the runtime error code for syntax errors being present, namely 0x23 - 0x2 - 0x35 (0xa2230035)
+
+Venus Errors
+------------------------
+
+- :ref:`1001 : Syntax error <1001>`
+- :ref:`1002 : Syntax error before <1002>`
+- :ref:`1101 : Missing period <1101>`
+- :ref:`1102 : Missing semicolon <1102>`
+- :ref:`1103 : Missing assignment <1103>`
+- :ref:`1104 : Missing opening parenthesis <1104>`
+- :ref:`1105 : Missing closing parenthesis <1105>`
+- :ref:`1106 : Missing opening brace <1106>`
+- :ref:`1107 : Missing closing brace <1107>`
+- :ref:`1108 : Missing opening bracket <1108>`
+- :ref:`1109 : Missing closing bracket <1109>`
+- :ref:`1110 : Missing comma or closing parenthesis <1110>`
+- :ref:`1111 : Missing comma or semicolon <1111>`
+- :ref:`1112 : Missing statement <1112>`
+- :ref:`1201 : Bad variable declaration <1201>`
+- :ref:`1202 : Bad argument list <1202>`
+- :ref:`1203 : Bad function name <1203>`
+- :ref:`1204 : Bad member function name <1204>`
+- :ref:`1205 : Bad argument name <1205>`
+- :ref:`1206 : Bad statement <1206>`
+- :ref:`1207 : Bad structure name <1207>`
+- :ref:`1208 : Bad variable name <1208>`
+- :ref:`1209 : Bad subscript expression <1209>`
+- :ref:`1210 : Bad member selection <1210>`
+- :ref:`1211 : Bad argument statement <1211>`
+- :ref:`1212 : Bad member declaration list <1212>`
+- :ref:`1213 : Bad variable list <1213>`
+- :ref:`1214 : Bad for expression <1214>`
+- :ref:`1215 : Bad expression <1215>`
+- :ref:`1216 : Bad file name <1216>`
+- :ref:`1217 : Bad member declaration <1217>`
+- :ref:`1218 : Bad block <1218>`
+- :ref:`1219 : Bad number <1219>`
+- :ref:`1220 : Bad program <1220>`
+- :ref:`1221 : Bad array size <1221>`
+- :ref:`1222 : Bad string expression <1222>`
+- :ref:`1223 : Bad function reference <1223>`
+- :ref:`1224 : Bad sequence expression <1224>`
+- :ref:`1225 : Bad array expression <1225>`
+- :ref:`1226 : Bad array type <1226>`
+- :ref:`1227 : Bad constant <1227>`
+- :ref:`1228 : Bad namespace name <1228>`
+- :ref:`1229 : Bad object expression <1229>`
+- :ref:`1230 : Bad timer expression <1230>`
+- :ref:`1231 : Bad event expression <1231>`
+- :ref:`1302 : Undeclared identifier <1302>`
+- :ref:`1303 : Redefined identifier <1303>`
+- :ref:`1304 : Redefined formal parameter <1304>`
+- :ref:`1305 : Nested function definition <1305>`
+- :ref:`1306 : Nested comments <1306>`
+- :ref:`1307 : Unterminated character constant <1307>`
+- :ref:`1308 : Unterminated string <1308>`
+- :ref:`1309 : No method <1309>`
+- :ref:`1310 : Redefined method <1310>`
+- :ref:`1311 : Unexpected end of file <1311>`
+- :ref:`1312 : Include file not found <1312>`
+- :ref:`1313 : Internal error <1313>`
+- :ref:`1314 : Empty statement <1314>`
+- :ref:`1315 : Too many arguments <1315>`
+- :ref:`1316 : Not a member function <1316>`
+- :ref:`1317 : Wrong member function <1317>`
+- :ref:`1318 : Not a data member <1318>`
+- :ref:`1319 : L-value is not a structure identifier <1319>`
+- :ref:`1320 : L-value is not an array identifier <1320>`
+- :ref:`1321 : L-value is an array identifier <1321>`
+- :ref:`1322 : L-value is structure identifier <1322>`
+- :ref:`1323 : Integer divide by zero <1323>`
+- :ref:`1324 : Not an L-value <1324>`
+- :ref:`1325 : Handler undefined <1325>`
+- :ref:`1326 : Handler redefined <1326>`
+- :ref:`1327 : Type mismatch <1327>`
+- :ref:`1328 : Layout file not found <1328>`
+- :ref:`1329 : Too few arguments <1329>`
+- :ref:`1330 : Instrument not registered <1330>`
+- :ref:`1331 : Instrument needs a deck layout <1331>`
+- :ref:`1332 : Instrument needs no deck layout <1332>`
+- :ref:`1334 : Skipped block initialisation <1334>`
+- :ref:`1335 : Parser token buffer overflow <1335>`
+- :ref:`1336 : Name too long <1336>`
+- :ref:`1337 : Type mismatch in formal parameter <1337>`
+- :ref:`1338 : Type mismatch in return value <1338>`
+- :ref:`1339 : Must return a value <1339>`
+- :ref:`1340 : Redefined workflow <1340>`
+- :ref:`1341 : Not schedulable <1341>`
+- :ref:`1342 : Private object reference <1342>`
+- :ref:`1343 : Private function reference <1343>`
+- :ref:`1344 : Analyzing completed with error <1344>`
+- :ref:`1345 : Lexer string buffer overflow <1345>`
+- :ref:`1346 : Obsolete statement <1346>`

VenusLibraryDocumentation-DocsForGPT/docs/source/Tools_Library.rst

@@ -0,0 +1,64 @@
+Tools Library
+============================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Tools_Library.pkg
+
+The tools library is designed to add some QoL functions to Venus. It adds the following functions.
+
+- :ven:func:`CalculateNumberOfTubesAndVolumePerTube`
+- :ven:func:`Reformat_Sequence`
+- :ven:func:`Reformat_ValuesForDialog`
+
+.. ven:function:: CalculateNumberOfTubesAndVolumePerTube(variable i_str_ReagentName, variable i_int_NumberOfSamples, variable i_flt_VolumePerSample, variable i_flt_MaximumContainerVolume, variable i_flt_DeadLabwareVolume, variable i_flt_DeadVolumeReagent, variable o_int_NumberOfContainersNeeded, array o_arr_VolumesPerContainer, array o_arr_DescriptionForDialog)
+
+	This function calculates the number of containers needed for a reagent and the volume per container.
+
+	:params i_str_ReagentName: The name of the reagent being calculated
+	:params i_int_NumberOfSamples: The number of samples requiring the reagent
+	:params i_flt_VolumePerSample: The volume of reagent required for each sample
+	:params i_flt_MaximumContainerVolume: The maximum volume a single container can hold
+	:params i_flt_DeadVolumeLabware: The dead volume in the labware
+	:params i_flt_DeadVolumeReagent: The percentage dead volume of the reagent
+	:params o_int_NumberOfContainersNeeded: The calculated number of containers needed
+	:params o_arr_VolumesPerContainer: An array of the volumes required for each tube
+	:params o_arr_DescriptionForDialog: An array of the descriptions for the dialog
+	:type i_str_ReagentName: Variable
+ 	:type i_int_NumberOfSamples: Variable
+  	:type i_flt_VolumePerSample: Variable
+ 	:type i_flt_MaximumContainerVolume: Variable
+  	:type i_flt_DeadVolumeLabware: Variable
+  	:type i_flt_DeadVolumeReagent: Variable
+  	:type o_int_NumberOfContainersNeeded: Variable
+  	:type o_arr_VolumesPerContainer: Array of variables
+  	:type o_arr_DescriptionForDialog: Array of variables
+  	:return: None
+  	:rtype: N/A
+
+.. ven:function:: Reformat_Sequence(sequence io_sequenceInput, variable i_intNumberOfPositions)
+
+  This function reformats a sequence to have as many positions as needed:
+  Source Sequence:
+  A1, B1
+
+  Total Number of positions needed = 4
+
+  Output Sequence:
+  A1, B1, A1, B1
+
+  :params io_sequenceInput: The sequence of interest
+  :params i_intNumberOfPositions: The number of positions required
+  :type io_sequenceInput: Sequence
+  :type i_intNumberOfPositions: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Reformat_ValuesForDialog(variable i_flt_valueToReformat, variable o_str_valueFormatted)
+
+  This function translates floats into strings and gets rid of any trailing 0s. Use the output value to display volumes in dialogs only.
+
+  :params i_flt_valueToReformat: The float to turn into a string
+  :params o_str_valueFormatted: The output string after it has been converted from a float
+  :type i_flt_valueToReformat: Variable
+  :type o_str_valueFormatted: Variable
+  :return: None
+  :rtype: N/A

VenusLibraryDocumentation-DocsForGPT/docs/source/TraceLevel.txt

@@ -0,0 +1,262 @@
+TraceLevel
+=================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/TraceLevel.pkg
+
+The TraceLevel library adds a variety of functions related to the trace file. The functions it adds are:
+
+- :ven:func:`GetTraceLevel`
+- :ven:func:`SetTraceLevel`
+- :ven:func:`SetStringIndicator`
+- :ven:func:`Trace_02`
+- :ven:func:`Trace_04`
+- :ven:func:`Trace_06`
+- :ven:func:`Trace_08`
+- :ven:func:`Trace_10`
+- :ven:func:`TraceArray`
+- :ven:func:`TraceArrayHorizontally`
+- :ven:func:`TraceArraysFaceToFace`
+- :ven:func:`TraceSequence`
+- :ven:func:`TraceSequenceParameter`
+- :ven:func:`TraceSequencePositions`
+- :ven:func:`TraceAction`
+- :ven:func:`SetActionIndicator`
+
+.. ven:function:: GetTraceLevel()
+
+  This function returns the current trace level.
+
+  :return: This function returns one of the following predefined constants; TRACE_LEVEL_NONE (0), which corresponds to no traces at all. TRACE_LEVEL_RELEASE (1), which corresponds to only items with release trace level being traced. TRACE_LEVEL_DEBUG (2), which corresponds to everything being traced.
+  :rtype: Variable
+
+.. ven:function:: SetTraceLevel(variable i_intTraceLevel)
+
+  This function is used to set the trace level for the method or library.
+
+  :params i_intTraceLevel: The trace level for the library. Set to one of the following constants; TRACE_LEVEL_NONE (0), which corresponds to no traces at all. TRACE_LEVEL_RELEASE (1), which corresponds to only items with release trace level being traced. TRACE_LEVEL_DEBUG (2), which corresponds to everything being traced.
+  :type i_intTraceLevel: Variable (integer)
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: SetStringIndicator(variable i_strStringIndicatorCharacter)
+
+  This function is used to set one or more characters to indicate strings (by flanking them) in all traces. It can be useful to identify leading or trailing spaces in strings. You can do this by setting i_strStringIndicatorCharacter to \' or \*.
+
+  :params i_strStringIndicatorCharacter: Characters that are being added at the beginning and the end of each string trace.
+  :type i_strStringIndicatorCharacter: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Trace_02(variable i_intTraceLevel, variable i_varToTrace_01, variable i_varToTrace_02)
+
+  This function is used to trace the value of 2 variables in one line. Will not automatically insert a space between the two variables.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_varToTrace_01: The first variable to trace.
+  :params i_varToTrace_02: The second variable to trace.
+  :type i_intTraceLevel: Variable
+  :type i_varToTrace_01: Variable
+  :type i_varToTrace_02: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Trace_04(variable i_intTraceLevel, variable i_varToTrace_01, variable i_varToTrace_02, variable i_varToTrace_03, variable i_varToTrace_04)
+
+  This function is used to trace the value of 4 variables in one line. Will not automatically insert a space between the variables.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_varToTrace_01: The first variable to trace.
+  :params i_varToTrace_02: The second variable to trace.
+  :params i_varToTrace_03: The third variable to trace.
+  :params i_varToTrace_04: The fourth variable to trace.
+  :type i_intTraceLevel: Variable
+  :type i_varToTrace_01: Variable
+  :type i_varToTrace_02: Variable
+  :type i_varToTrace_03: Variable
+  :type i_varToTrace_04: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Trace_06(variable i_intTraceLevel, variable i_varToTrace_01, variable i_varToTrace_02, variable i_varToTrace_03, variable i_varToTrace_04, variable i_varToTrace_05, variable i_varToTrace_06)
+
+  This function is used to trace the value of 6 variables in one line. Will not automatically insert a space between the variables.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_varToTrace_01: The first variable to trace.
+  :params i_varToTrace_02: The second variable to trace.
+  :params i_varToTrace_03: The third variable to trace.
+  :params i_varToTrace_04: The fourth variable to trace.
+  :params i_varToTrace_05: The fifth variable to trace.
+  :params i_varToTrace_06: The sixth variable to trace.
+  :type i_intTraceLevel: Variable
+  :type i_varToTrace_01: Variable
+  :type i_varToTrace_02: Variable
+  :type i_varToTrace_03: Variable
+  :type i_varToTrace_04: Variable
+  :type i_varToTrace_05: Variable
+  :type i_varToTrace_06: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Trace_08(variable i_intTraceLevel, variable i_varToTrace_01, variable i_varToTrace_02, variable i_varToTrace_03, variable i_varToTrace_04, variable i_varToTrace_05, variable i_varToTrace_06, variable i_varToTrace_07, variable i_varToTrace_08)
+
+  This function is used to trace the value of 8 variables in one line. Will not automatically insert a space between the variables.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_varToTrace_01: The first variable to trace.
+  :params i_varToTrace_02: The second variable to trace.
+  :params i_varToTrace_03: The third variable to trace.
+  :params i_varToTrace_04: The fourth variable to trace.
+  :params i_varToTrace_05: The fifth variable to trace.
+  :params i_varToTrace_06: The sixth variable to trace.
+  :params i_varToTrace_07: The seventh variable to trace.
+  :params i_varToTrace_08: The eighth variable to trace.
+  :type i_intTraceLevel: Variable
+  :type i_varToTrace_01: Variable
+  :type i_varToTrace_02: Variable
+  :type i_varToTrace_03: Variable
+  :type i_varToTrace_04: Variable
+  :type i_varToTrace_05: Variable
+  :type i_varToTrace_06: Variable
+  :type i_varToTrace_07: Variable
+  :type i_varToTrace_08: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: Trace_10(variable i_intTraceLevel, variable i_varToTrace_01, variable i_varToTrace_02, variable i_varToTrace_03, variable i_varToTrace_04, variable i_varToTrace_05, variable i_varToTrace_06, variable i_varToTrace_07, variable i_varToTrace_08, variable i_varToTrace_09, variable i_varToTrace_10)
+
+  This function is used to trace the value of 10 variables in one line. Will not automatically insert a space between the variables.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_varToTrace_01: The first variable to trace.
+  :params i_varToTrace_02: The second variable to trace.
+  :params i_varToTrace_03: The third variable to trace.
+  :params i_varToTrace_04: The fourth variable to trace.
+  :params i_varToTrace_05: The fifth variable to trace.
+  :params i_varToTrace_06: The sixth variable to trace.
+  :params i_varToTrace_07: The seventh variable to trace.
+  :params i_varToTrace_08: The eighth variable to trace.
+  :params i_varToTrace_09: The ninth variable to trace.
+  :params i_varToTrace_10: The tenth variable to trace.
+  :type i_intTraceLevel: Variable
+  :type i_varToTrace_01: Variable
+  :type i_varToTrace_02: Variable
+  :type i_varToTrace_03: Variable
+  :type i_varToTrace_04: Variable
+  :type i_varToTrace_05: Variable
+  :type i_varToTrace_06: Variable
+  :type i_varToTrace_07: Variable
+  :type i_varToTrace_08: Variable  
+  :type i_varToTrace_09: Variable
+  :type i_varToTrace_10: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceArray(variable i_intTraceLevel, variable i_strDescription, array i_arrvarToTrace)
+
+  This function is used to trace an array of variables. It will trace each value of the array in its own line, along with the array description and the index of the value.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_strDescription: A description of the array, which will be at the start of each line of the array trace.
+  :params i_arrvarToTrace: The array to be traced.
+  :type i_intTraceLevel: Variable
+  :type i_strDescription: Variable
+  :type i_arrvarToTrace: Array (of variables)
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceArrayHorizontally(variable i_intTraceLevel, variable i_strDescription, array i_arrvarToTrace)
+
+  This function is used to trace an array of variables. It will trace the array description, followed by each array index and value pair, all on one line.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_strDescription: A description of the array, which will be at the start of the array trace.
+  :params i_arrvarToTrace: The array to be traced.
+  :type i_intTraceLevel: Variable
+  :type i_strDescription: Variable
+  :type i_arrvarToTrace: Array (of variables)
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceArraysFaceToFace(variable i_intTraceLevel, variable i_strDescription_1, variable i_strDescription_2, array i_arrvarToTrace_1, array i_arrvarToTrace_2)
+
+  This function is used to trace two arrays of variables at the same time, with values at the same index being shown on the same line as one another.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_strDescription_1: A description of the first array, which will be at the start of the array trace.
+  :params i_strDescription_2: A description of the second array, which will be at the start of the array trace.
+  :params i_arrvarToTrace_1: The first array to be traced.
+  :params i_arrvarToTrace_2: The second array to be traced.
+  :type i_intTraceLevel: Variable
+  :type i_strDescription_1: Variable
+  :type i_strDescription_2: Variable
+  :type i_arrvarToTrace_1: Array (of variables)
+  :type i_arrvarToTrace_2: Array (of variables)
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceSequence(variable i_intTraceLevel, sequence i_seqToTrace)
+
+  This function is used to trace a sequence. It will list the sequence name, current position, the count and total positions in the sequence, the max number of positions available, and the number of used positions. It will then list the labware ID and position ID for each value of the sequence.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_seqToTrace: The sequence to be traced
+  :type i_intTraceLevel: Variable
+  :type i_seqToTrace: Sequence
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceSequenceParameter(variable i_intTraceLevel, sequence i_seqToTrace)
+
+  This function is used to trace the parameters of a sequence. It will list the sequence name, current position, the count and total positions in the sequence, the max number of positions available, and the number of used positions.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_seqToTrace: The sequence to be traced
+  :type i_intTraceLevel: Variable
+  :type i_seqToTrace: Sequence
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceSequencePositions(device ML_STAR, variable i_intTraceLevel, sequence i_seqToTrace, variable i_blnCurrentPositionOnly)
+
+  This function is used to trace the deck positions of a sequence. It will trace the sequence name, then for each part of the sequence it will trace the position ID and the x, y, z, and r coordinates of the position.
+
+  :params ML_STAR: The STAR device.
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_seqToTrace: The sequence to be traced
+  :params i_blnCurrentPositionOnly: A boolean determining whether the function will trace positions for all sequence positions (0) or just the current sequence position (1).  
+  :type ML_STAR: Device
+  :type i_intTraceLevel: Variable
+  :type i_seqToTrace: Sequence
+  :type i_blnCurrentPositionOnly: Boolean
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: TraceAction(variable i_intTraceLevel, variable i_intAction, variable i_strFunctionName, variable i_strMethodName, variable i_strComment)
+
+  This function is used to trace different action states for a module. :ven:func:`SetActionIndicator` can be used to help identify actions in log files more easily.
+
+  :params i_intTraceLevel: The trace level for the entry. Can be set to either TRACE_LEVEL_RELEASE (1) or TRACE_LEVEL_DEBUG (2). If set to 1, the function will show up in the trace when the trace level is set to either TRACE_LEVEL_RELEASE or TRACE_LEVEL_DEBUG, if set to 2, the function will only show up when the trace level is TRACE_LEVEL_DEBUG.
+  :params i_intAction: The action to be traced. Set to one of the following constants. START (1) corresponds to the entry being traced as starting. COMPLETE (2) corresponds to the entry being traced as finished successfully. ERROR (3) corresponds to the entry being traced as error occurred. PROGRESS (4) corresponds to the entry being traced as progressing. COMPLETE_WITH_ERROR (5) corresponds to the entry being traced as finished unsuccessfully.
+  :params i_strFunctionName: The function name for the action trace. Can be set to the return value of the HSL function *GetFunctionName*, which will automatically be formatted correctly.
+  :params i_strMethodName: The method name for the action trace. Can be set to the return value of the HSL function *GetMethodFileName*, which will automatically be formatted correctly.
+  :params i_strComment: A comment to be traced with the action trace.
+  :type i_intTraceLevel: Variable
+  :type i_intAction: Variable
+  :type i_strFunctionName: Variable
+  :type i_strMethodName: Variable
+  :type i_strComment: Variable
+  :return: None
+  :rtype: N/A
+
+.. ven:function:: SetActionIndicator(variable i_intAction, variable i_strIndicator)
+
+  This function is used to set one or more characters to indicate actions. By setting *i_strIndicator* to different characters you can make it easy to identify different actions in the trace.
+
+  :params i_intAction: The action to be traced. Set to one of the following constants. START (1) corresponds to the entry being traced as starting. COMPLETE (2) corresponds to the entry being traced as finished successfully. ERROR (3) corresponds to the entry being traced as error occurred. PROGRESS (4) corresponds to the entry being traced as progressing. COMPLETE_WITH_ERROR (5) corresponds to the entry being traced as finished unsuccessfully.
+  :params i_strIndicator: Character(s) that are being repeated at a total length of up to 100 and traced before and after the action trace.
+  :type: i_intAction: Variable
+  :type i_strIndicator: Variable
+  :return: None
+  :rtype: N/A
+

VenusLibraryDocumentation-DocsForGPT/docs/source/Windows.txt

@@ -0,0 +1,50 @@
+Windows (from HSLExtensions)
+=========================================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/Windows.pkg
+
+The windows library from HSLExtensions adds functions related to registries and special directories. The functions it adds are as follows:
+
+- :ven:func:`GetRegistryValue`
+- :ven:func:`GetSpecialDirectory`
+- :ven:func:`SetRegistryValue`
+
+.. ven:function:: GetRegistryValue(variable i_intHKey, variable i_strKey, variable i_strValueName, variable o_varValue)
+
+  This function reads a value from the specified registry
+
+  :params i_intHKey: The main key of the registry. 1 = ClassesRoot, 2 = CurrentUser, 3 = LocalMachine, 4 = Users, 5 = CurrentConfig.
+  :params i_strKey: The key to the path (e.g. SOFTWARE\Phoenix\Directories\Methods)
+  :params i_strValueName: The name of the value to be read
+  :params o_varValue: The value which was read (type according to value type)
+  :type i_intHKey: Integer
+  :type i_strKey: String
+  :type i_strValueName: String
+  :type o_varValue: Variable
+  :return: Boolean showing whether the key exists (hslTrue) or not (hslFalse)
+  :rtype: Boolean
+
+.. ven:function:: GetSpecialDirectory(variable i_intSpecialDirectory)
+
+  This function gets the specified special directory
+
+  :params i_intSpecialDirectory: The type of the special directory. 1 = WindowsDirectory, 2 = SystemDirectory, 3 = TemporaryDirectory.
+  :type i_intSpecialDirectory: Integer
+  :return: The special directory
+  :rtype: String
+
+.. ven:function:: SetRegistryValue(variable i_intHKey, variable i_strKey, variable i_strValueName, variable i_varValue, variable i_intValueType)
+
+  This function writes a value to the specified registry
+
+  :params i_intHKey: The main key of the registry. 1 = ClassesRoot, 2 = CurrentUser, 3 = LocalMachine, 4 = Users, 5 = CurrentConfig.
+  :params i_strKey: The key to the path (e.g. SOFTWARE\Phoenix\Directories\Methods)
+  :params i_strValueName: The name of the value to be read
+  :params i_varValue: The value which was will be written in
+  :params i_intValueType: The type of the value. 1 = String, 2 = Number, 3 = Binary, 4 = ExpandableString
+  :type i_intHKey: Integer
+  :type i_strKey: String
+  :type i_strValueName: String
+  :type o_varValue: Variable
+  :return: Boolean showing whether the function was successful (hslTrue) or not (hslFalse)
+  :rtype: Boolean

VenusLibraryDocumentation-DocsForGPT/docs/source/ZerouLScanner.txt

@@ -0,0 +1,15 @@
+Zero uL Scanner
+=========================
+
+https://github.com/theonetruenerd/VenusPackages/blob/main/ZerouLScanner.pkg
+
+The zero uL scanner library adds a single function which is designed to be added at the end of a method. It scans the trace file for any steps in which 0uL was pipetted and returns the number of times that happened. This is to check for steps where (for example) it is pipetting a volume based on a variable, and there is a spelling mistake in the variable, or the variable isn't defined correctly. It will work in both simulation mode and normal mode.
+
+- :ven:func:`CheckFor0s`
+
+.. ven:function:: CheckFor0s()
+
+  This function checks for any steps in which 0uL has been pipetted and returns the number of times that has happened.
+
+  :return: Number of times 0uL has been pipetted
+  :rtype: Variable

VenusLibraryDocumentation-DocsForGPT/docs/source/conf.py

@@ -0,0 +1,36 @@
+# Configuration file for the Sphinx documentation builder.
+
+# -- Project information
+
+project = 'Venus Documentation'
+# copyright = 'None'
+author = 'TChapman'
+
+release = '0.1'
+version = '0.1.0'
+
+# -- General configuration
+
+extensions = [
+    'sphinx.ext.duration',
+    'sphinx.ext.doctest',
+    'sphinx.ext.autodoc',
+    'sphinx.ext.autosummary',
+    'sphinx.ext.intersphinx',
+]
+
+intersphinx_mapping = {
+    'python': ('https://docs.python.org/3/', None),
+    'sphinx': ('https://www.sphinx-doc.org/en/master/', None),
+}
+intersphinx_disabled_domains = ['std']
+
+templates_path = ['_templates']
+
+# -- Options for HTML output
+
+html_theme = 'sphinx_rtd_theme'
+
+html_theme_options = {'body_max_width': '40%'}
+
+epub_show_urls = 'footnote'

VenusLibraryDocumentation-DocsForGPT/docs/source/index.rst

@@ -0,0 +1,52 @@
+Welcome to Venus's documentation!
+===================================
+
+**Venus** is a coding language wrapper used in the coding of Hamilton Microlab STARs and similar devices.
+This is the consolidated unofficial documentation for Venus 4 as well as its libraries, compiled from official sources as well as personal troubleshooting. 
+
+**This is not an official Hamilton resource**
+
+.. note::
+
+   This project is under active development. If any issues or mistakes are found, please comment or contact me directly at tarunchapman@hotmail.com.
+   General place to download libraries: https://github.com/theonetruenerd/VenusPackages
+
+.. toctree::
+
+   :caption: Documented Libraries
+   :titlesonly:
+
+   venus
+   ErrorCodes
+   ASWGlobal
+   Aliquot_for_EasySteps_v2
+   Aliquot_with_EasySteps
+   Array
+   ArrayTools
+   CheckCarrierPresence_v2
+   ColourSchemeLibrary
+   ConvertFileToASCII
+   DebugAssist
+   EditFileAttributes
+   ErrorReportLibrary
+   ErrorSimulator
+   Framework
+   HSLDeckVisualize
+   HSLFilLib
+   HSLFilLibEx
+   HSLStatistics
+   HSLStrLib
+   HSLZipLib
+   HSL_SeqDailyTools
+   If_And_If_Or
+   Labware_Properties
+   Lookup
+   Pipetting
+   RemoveTextDelimitersFromAsciiTextFile
+   STAR_Channel_Tools
+   StrTokenize
+   String
+   Tools_Library
+   TraceLevel
+   Windows
+   ZerouLScanner

VenusLibraryDocumentation-DocsForGPT/docs/source/venus.txt

@@ -0,0 +1,279 @@
+Venus
+==============================================
+
+This section aims to cover the *functions* that Venus can run. Documentation on more general principles of Venus, including things like the liquid editor and labware editor, will be found separately.
+
+Venus functions are organised into several sections. These are the following:
+
+
+  - :ref:`General Steps`
+  - :ref:`Scheduler Steps`
+  - :ref:`Custom Dialog Steps`
+  - :ref:`Favourites`
+  - :ref:`Templates`
+
+There are also instrument specific functions in their own categories:
+
+  - :ref:`ML_STAR`
+  - :ref:`Microlab STAR Smart Steps`
+
+.. General Steps
+
+  The general steps are composed of relatively standard coding functions that will be present in many other coding languages. These are not associated with the hardware of any instrument and are present on Venus regardless of whether you are using a STAR, a STARLet, or any other instrument which uses Venus. The functions which fall under general steps are listed below:
+
+  - :ven:func:`Comment`
+  - :ven:func:`Assignment`
+  - :ven:func:`Assignment with Calculation`
+  - :ven:func:`Loop`
+  - :ven:func:`Loop: Break`
+  - :ven:func:`If, Else`
+  - :ven:func:`Array: Declare / Set Size`
+  - :ven:func:`Array: Set At`
+  - :ven:func:`Array: Get At`
+  - :ven:func:`Array: Get Size`
+  - :ven:func:`Array: Copy`
+  - :ven:func:`Sequence: Get Current Position`
+  - :ven:func:`Sequence: Set Current Position`
+  - :ven:func:`Sequence: Get End Position`
+  - :ven:func:`Sequence: Set End Position`
+  - :ven:func:`Adjust Sequences`
+  - :ven:func:`File: Open`
+  - :ven:func:`File: Read`
+  - :ven:func:`File: Write`
+  - :ven:func:`File: Set Position`
+  - :ven:func:`File: Close`
+  - :ven:func:`Timer: Start`
+  - :ven:func:`Timer: Wait for`
+  - :ven:func:`Timer: Read Elapsed Time`
+  - :ven:func:`Timer: Restart`
+  - :ven:func:`User Input`
+  - :ven:func:`User Output`
+  - :ven:func:`Shell`
+  - :ven:func:`Set Event`
+  - :ven:func:`Wait for Event`
+  - :ven:func:`Return`
+  - :ven:func:`Abort`
+  - :ven:func:`Error Handling by the User`
+  - :ven:func:`Begin Parallel`
+  - :ven:func:`End Parallel`
+
+.. Scheduler Steps
+
+  The scheduler steps are functions which arrange the method to be executed on a number of resources and submitted to capacity, time and precedence relations in a way that fulfils the optimality criteria. The methods and its activation criterions are defined in a workflow.
+
+The Schedule process is divided into two phases: scheduling and executing. The scheduler functions are listed below:
+
+  - :ven:func:`Select Method`
+  - :ven:func:`Activate Task`
+  - :ven:func:`Cancel Task`
+  - :ven:func:`Schedule Block`
+  - :ven:func:`Reschedule`
+
+.. Custom Dialog Steps
+
+  The custom dialog steps only adds the :ven:func:`Custom Dialog` function, which allows creation of more complicated dialogs than the standard :ven:func:`User Input` and :ven:func:`User Output` functions. 
+
+.. Favourites
+
+  The favourites drop-down allows you to select functions which you use frequently to be in their own separate tab so that they are easier to find. These steps will be favourited on every method.
+
+.. Templates
+
+  Templates add the ability to preprogram commonly used functions and processes/sets of functions so that the user doesn't have to write them freshly every time. An example might be a tip pickup step with all the parameters for pickup already programmed in so you don't have to fill them in, or a bulk creation of arrays for an ASW Dialog.
+
+.. ML_STAR
+
+  The ML_STAR section adds the core functions which interact with the ML_STAR itself, which is anything that interacts with the hardware or firmware of the STAR. They are split into the power steps and single steps. The single steps are then split into liquid handling functions, preparation functions, transport functions, and miscellaneous functions. The functions which come under the ML_STAR tab are:
+
+- :ven:func:`1000ul Channel Aspirate`
+- :ven:func:`1000ul Channel Dispense`
+- :ven:func:`CO-RE 96 Head Aspirate`
+- :ven:func:`CO-RE 96 Head Dispense`
+- :ven:func:`iSWAP Transport`
+- :ven:func:`1000ul Channel CO-RE Grip Transport`
+- :ven:func:`1000ul Channel Tip Pick Up (Single Step)`
+- :ven:func:`1000ul Channel Aspirate (Single Step)`
+- :ven:func:`1000ul Channel Dispense (Single Step)`
+- :ven:func:`1000ul Channel Dispense on the Fly (Single Step)`
+- :ven:func:`1000ul Channel Tip Eject (Single Step)`
+- :ven:func:`1000ul Channel Get Last Liquid Level (Single Step)`
+- :ven:func:`1000ul Channel Aspirate 2nd Phase (Single Step)`
+- :ven:func:`CO-RE 96 Head Tip Pick Up (Single Step)`
+- :ven:func:`CO-RE 96 Head Aspirate (Single Step)`
+- :ven:func:`CO-RE 96 Head Dispense (Single Step)`
+- :ven:func:`CO-RE 96 Head Tip Eject (Single Step)`
+- :ven:func:`Initialize (Single Step)`
+- :ven:func:`Calibrate Carrier (Single Step)`
+- :ven:func:`Lock/Unlock Front Cover (Single Step)`
+- :ven:func:`iSWAP Get Plate (Single Step)`
+- :ven:func:`iSWAP Place Plate (Single Step)`
+- :ven:func:`iSWAP Move Plate (Single Step)`
+- :ven:func:`iSWAP Open Gripper (Single Step)`
+- :ven:func:`iSWAP Close Gripper (Single Step)`
+- :ven:func:`iSWAP Get First Plate Position (Single Step)`
+- :ven:func:`iSWAP Park (Single Step)`
+- :ven:func:`1000ul Channel CO-RE Grip Get Plate (Single Step)`
+- :ven:func:`1000ul Channel CO-RE Grip Place Plate (Single Step)`
+- :ven:func:`1000ul Channel CO-RE Grip Move Plate (Single Step)`
+
+.. Microlab STAR Smart Steps
+
+  Smart steps are functions which are preprogrammed single steps which are combined to be ready for specific tasks such as doing both aspiration and dispensing of a reagent in the same function. The Smart Step functions are:
+
+- :ven:func:`Advanced Load Settings`
+- :ven:func:`Load`
+- :ven:func:`Load and Match`
+- :ven:func:`1000ul Channel Pipette - Simple (1-1)`
+- :ven:func:`1000ul Channel Pipette - Replica (1-n)`
+- :ven:func:`1000ul Channel Pipette - Pooling (n-1)`
+- :ven:func:`1000ul Channel Pipette - Aliquot`
+- :ven:func:`Unload`
+- :ven:func:`1000ul Channel Needle Wash Settings`
+- :ven:func:`1000ul Channel Needle Pick Up`
+- :ven:func:`1000ul Channel Needle Eject`
+- :ven:func:`1000ul Channel Tip Pick Up`
+- :ven:func:`1000ul Channel Tip Eject`
+
+How venus works
+-------------------------------------------------------
+
+Venus is a drag-and-drop wrapper for a separate coding language called HSL, standing for Hamilton Standard Language. When coding a method in Venus, all the available functions (core and any from imported libraries) are listed on the left hand side of the screen in a tree view. When you want to add a step to your method, you drag and drop that function from the left hand side and drop it wherever you want it to be in your method. This will then open a dialog box which allows you to input your desired parameters. The method is saved as a .med file, which can be run through a software called HxRunControl.exe. The run control software can run simulations of the code as well as the code on an actual robot. In the run control software window, you can see the deck layout dynamically changing, an open view of the method showing what step you are on, and a trace file which is a type of log which displays the data from every step that is occuring and is timestamped for each step. The trace file is saved to the Log Files folder within the main Hamilton folder in Program Files (x86). Method files (.med) can compile into HSL files (.hsl) which can also be edited and run through the run control software. Instead of being drag-and-drop, HSL is a more standard coding language, with C++ like syntax. HSL files cannot be converted into .med files; as such, it is usually recommended to insert snippets of HSL code into the main .med file rather than coding in HSL itself, or to only use HSL for creation of fresh libraries. 
+
+Libraries are groups of functions which reside in the library folder within the main Hamilton folder. They can be imported into specific methods, at which point the functions associated with that library will appear in the function tree on the left hand side of the method editor. Libraries can either be written in HSL (and are thus .hsl files) or can be "sub-method libraries", which is a series of steps coded in Venus that are stored in a way that works like a function. Sub-method libraries are .smt files. You can have submethods in a normal method file, and it is often encouraged so that your code is "parcelled" into blocks which contain the main blocks of your method. These submethods are just like the normal method but reside in a separate tab in the method editor. 
+
+The following function groups are not libraries and instead are "core" groups which do not need importing; every other function referenced is part of a library.
+  - General Steps
+  - Scheduler Steps
+  - Custom Dialog Steps
+  - Favourites
+  - Templates
+  - ML_STAR
+  - Microlab STAR Smart Steps
+
+When pipetting using the 1000ul channels, there are 8 channels total. Channel patterns (which determine which channels are in use at any given point in time) are written in the form of a string of 1s and 0s, where 0 is not in use and 1 is in use. For example, if using channels 2, 3, and 5, the channel pattern would be "01101000". All pipetting steps require a channel pattern input as one of the parameters. Unless specified, the priority of the channels should always be to use the channels with lower indices. 
+
+There are several different tip types available for an ML_STAR, the most commonly used are 300ul (Standard volume, tip id 0), and 50ul (tip id 22). You can also get 10ul tips and 1000ul tips. All tips have the option of being normal, stackable, or filtered. No tip can take up more liquid than its type (i.e. a 300uL tip cannot ever have more than 300ul total volume in it). The 300ul tips should not be used to go below 10ul as they become very inaccurate. When pipetting, the total volume in a channel is the amount of liquid that has been aspirated by that channel minus the amount of liquid that has been dispensed by that channel. 
+
+For arrays in venus, you have to declare the size of the array (which can be empty) and then add items one by one; with the core functions you can't add more than one item at once. To add an item you can either specify an index or add to the end of the array; when adding to an empty array you can only add to the end of the array. Arrays in venus are 1-based rather than 0-based.
+
+For variable naming in venus, the following convention should be followed. If a variable is an integer, it should be prefixed with "int_". If it is a float, it should be prefixed with "flt_". If it is a timer, it should be prefixed with "timer_". If it is a loop counter, it should be prefixed with "loop_". If it is an array, it should be prefixed with "arr_". If it is an array of sequences, it should be prefixed with "arrseq_". If it is a sequence, it should be prefixed with "seq_". If it is an unknown variable type, it should be prefixed with "var_". If it is known to be a variable only used as input to functions, it should have an "i_" between the prefix and the variable name. If it is known to be a variable only used to store outputs from functions, it should have an "o_" between the prefix and the variable name. If it is known to be both an input and output variable, i.e. something which is input into a function and modified during the function and then the modified value is returned, it should have an "io_" between the prefix and variable name. If it is unknown whether it is an input or output variable, there is nothing extra between the prefix and variable name. 
+
+For creation of reaction mixes, if unspecified, you should add in the following order:
+  - Water
+  - Buffers
+  - Beads
+  - DNA
+  - ATP
+  - Enzymes.
+
+If the substance type is unknown, then prioritise adding high volumes before low volumes. In the code, functions do not have the :ven:func` prefix. 
+
+Microlab STARs have something called TADM; this is a pressure monitoring system of within pipetting steps, standing for Total Air Displacement Monitoring. The pressure data is saved in 10ms timepoints in a microsoft access database, along with the channel number, timestamp, and liquid class being used for the specific pipetting step that the TADM data was generated from. With the TADMCurveExport library, you can export the TADM data from the Microsoft Access Database file into an Excel file or a set of CSV files automatically. The TADM data can also be uploaded into the liquid class database to be associated with the specific liquid classes involved. You can set TADM tolerance bands within the liquid class database, which can cause the method to abort if TADM pressure data goes outside of the tolerance bands. The TADM data can also be used to analyze success of pipetting steps as incorrect/flawed pipetting (e.g. generating bubbles) will cause noticeable changes in the TADM data. 
+
+By default, make timers have the "is stoppable" parameter set to True. 
+
+Venus functions are denoted in the documentation by the ven:function:: prefix in the function definition and :ven:func: in the function references. 
+
+General Steps
+-------------------------------------------------------
+
+.. ven:function:: Comment
+
+  The comment function allows you to input a comment into the method. The comment can be chosen to be a Trace comment or not. If it is a Trace comment, it will be printed in the Trace during simulated or real runtime. Comment steps can also be chosen to be a specific colour in the editor, unlike most functions. The comment function doesn't have any input parameters, just a popup text box which you can input ASCII characters into. Pressing <Ctrl> + <Enter> will insert a new line. Pressing <Ctrl> + <Tab> will indent the text.
+
+.. ven:function:: Assignment
+
+  The assignment function allows you to specify a variable and assign a value to it. It does not have any input parameters but instead a box in which you can input the name of your variable and the value you wish to assign to it. The variable name can be a fresh name, or can be an existing one which you are reassigning a value to, or an element from an array. The value to be assigned can be a signed number, a string, an entry from a given list, another variable name, or an element from an array. If entering a string, the option to have it as a Translatable string is available, which can be translated into different languages using the Translation Support System provided by the Hamilton Company.
+
+Scheduler Steps
+-------------------------------------------------
+
+Custom Dialog Steps
+-------------------------------------------------
+
+Favourites
+-------------------------------------------------
+
+Templates
+-------------------------------------------------
+
+ML_STAR
+-------------------------------------------------
+
+.. ven:function:: 1000ul Channel Tip Pick Up (Single Step)
+
+  The 1000ul Channel Tip Pick Up (Single Step) function tells the Microlab STAR to pick up tips with the 1000ul channels. It asks for the input sequence where it can find the tips and whether the sequence counting is automatic (i.e. the starting position of the sequence increments when tips are picked up) or manual (no increments). It also allows you to select which channels are being used to pick up tips by assigning it a channel pattern, which can either be input directly in the dialog box or as a variable. It allows you to set custom error handling in response to specific errors that will potentially occur during the step, such as automatically testing the next spot in the sequence if no tips are found.
+
+.. ven:function:: 1000ul Channel Aspirate (Single Step)
+
+  The 1000ul Channel Aspirate (Single Step) function tells the Microlab STAR to use the specified channels to aspirate liquid from the specified sequence. It requires an input sequence telling it where to locate the desired liquid, as well as a boolean determining whether sequence counting is automatic (i.e. increments starting position after aspiration) or manual (i.e. no increment). It asks for a volume input, which can be a variable, and allows individual volumes to be set for each channel if desired. It also allows you to switch between three types of aspiration; normal, consecutive aspiration, and aspirate all. Aspirate all will attempt to aspirate a set volume, and if not enough is present it won't throw an error, it will simply take whatever is present. 
+  For the pipetting cycle settings, you can pick what tip type you want to use from the dropdown, as well as what dispense mode you wish to use. The dispense mode selected will then act as a filter for what liquid classes are available in the next drop-down. You can select your desired liquid class from the dropdown, either as a string name from the liquid class database, or as a variable. 
+  The aspirate position settings allow you to control the height in which the pipette will try aspirate, through a variety of different settings and options. The default is to use capacitive liquid level detection (cLLD) at the sensitivity defined by the labware definition (5). You can also change this sensitivity to be higher or lower. You can also turn on pressure liquid level detection (pLLD) which measures increases in pressure in the tip and uses that to determine liquid level height. You can set a submerge depth in mm, which tells the pipettes how far below the surface they are to go once they have identified the liquid height. If both pLLD and cLLD are on, you can set a maximum height difference, in which case if the values do not agree and are outside this set range, the method will abort. If neither pLLD or cLLD is on, you can set it to either aspirate a fixed height from the bottom of the labware, or to touch off the bottom of the labware and then rise a little bit.
+  The channel settings available allow you to select which channels are being used in the aspiration, which can be either selected via tickboxes, input directly into the dialog box, or input as a variable. The advanced settings let you control whether or not the pipette tips follow the changing liquid height during aspiration and mixing, as well as letting you add mixing cycles to the pipetting step, of a specified volume, position, and number of cycles. The error section lets you set custom error handling responses to specific errors that will potentially occur during the process, and the responses are automatically triggered upon the error. 
+
+.. ven:function:: 1000ul Channel Dispense (Single Step)
+
+  The 1000ul Channel Dispense (Single Step) function tells the Microlab STAR to use the specified channels to aspirate liquid from the specified sequence. It requires an input sequence telling it which piece of labware to dispense the desired liquid into, as well as a boolean determining whether sequence counting is automatic (i.e. increments starting position after aspiration) or manual (i.e. no increment). It asks for a volume input, which can be a variable, and allows individual volumes to be set for each channel if desired. The dispense mode can be chosen from a dropdown, and the default value is 8, which means it will use the liquid class specified in the previous aspiration step.
+  The dispense position settings allow you to control the height in which the pipette will try to dispense, through a variety of different settings and options. The default is to use capacitive liquid level detection (cLLD) at the sensitivity defined by the labware definition (5). You can also change this sensitivity to be higher or lower. You can also turn on pressure liquid level detection (pLLD) which measures increases in pressure in the tip and uses that to determine liquid level height. You can set a submerge depth in mm, which tells the pipettes how far below the surface they are to go once they have identified the liquid height. If both pLLD and cLLD are on, you can set a maximum height difference, in which case if the values do not agree and are outside this set range, the method will abort. If neither pLLD or cLLD is on, you can set it to either dispense a fixed height from the bottom of the labware, or to touch off the bottom of the labware and then rise a little bit. If the labware has been defined with the "Side Touch" characteristic, the channels can also do a side touch dispense, in which it will enter the well and then move the pipette tip to touch the side of the well at the specified height, allowing it to dispense on the side of the well, usually for the benefits of not making contact with the well bottom, or for the wicking effect. 
+  The channel settings available allow you to select which channels are being used in the dispense, which can be either selected via tickboxes, input directly into the dialog box, or input as a variable. The advanced settings let you control whether or not the pipette tips follow the changing liquid height during aspiration and mixing, as well as letting you add mixing cycles to the pipetting step, of a specified volume, position, and number of cycles. The error section lets you set custom error handling responses to specific errors that will potentially occur during the process, and the responses are automatically triggered upon the error. 
+
+.. ven:function:: 1000ul Channel Dispense on the Fly (Single Step)
+
+  The 1000ul Channel Dispense on the Fly (Single Step) function tells the Microlab STAR to dispense liquid continuously from the specified channel whilst moving at a set speed and distance, usually defined as a complete plate. You input the destination sequence, as well as whether sequence counting is automatic (1) or manual (0). If sequence counting is automatic, the next time it interacts with the sequence, it will treat the next untouched posiiton in the sequence as the first position in the sequence. You can input your desired total dispense volume, either as a variable or raw value, and you can also specify different volumes for each channel, which can be variables, elements from an array, or raw values. The dispense on the fly mode can either be set to complete plate (0) or sequence order (1). You can set the dispense position with two parameters; the labware surface distance in mm (which can either be input as a variable or raw value), and the Start X-offset in mm (which can also be input as a variable or raw value). In the pipetting arm section you can input the X-speed during the dispense, in mm/s (which can be input as a variable or raw value). 
+  The channel settings available allow you to select which channels are being used in the dispense, which can be either selected via tickboxes, input directly into the dialog box, or input as a variable. The advanced settings let you control whether the liquid class being used is the same as in the first aspiration of the cycle, and if not then it lets you pick a fresh liquid class. It also allows you to determine the X-acceleration distance before the first shoot in mm, the dispense direction (with 0 being serpentine and 1 being from the left only), as well as specifying any excluded labware positions. The error section lets you set custom error handling responses to specific errors that will potentially occur during the process, and the responses are automatically triggered upon the error. 
+
+.. ven:function:: 1000ul Channel Tip Eject (Single Step)
+
+  The 1000ul Channel Tip Eject (Single Step) function tells the Microlab STAR to eject tips from the specified channels. You input the eject destination, which is any piece of labware, but by default is (1) which corresponds to the default waste location on the Microlab STAR. If a separate eject destination is chosen, sequence counting can be turned to automatic (i.e. increment sequence after ejecting tips) or manual (no increment).
+  The channel settings allow you to select which channels the tips are being ejected from, whcih can either be selected via tickboxes, input directly into the dialog box, or input as a variable. The error settings let you set custom error handling responses to specific errors that will potentially occur during the process, and the responses are automatically triggered upon the error.
+
+.. ven:function:: 1000ul Channel Get Last Liquid Level (Single Step)
+
+  The 1000ul Channel Get Last Liquid Level (Single Step) function returns the liquid level height detected during the most recently performed aspirate or dispense step with liquid level detection enabled. There is no dialog box that appears as there are no parameters to input. It returns three values; the channel number, the detected liquid level height in mm relative to the deck coordinates of the Microlab STAR, and the block data for each channel.
+
+.. ven:function:: 1000ul Channel Aspirate 2nd Phase (Single Step)
+
+  The 1000ul Channel Aspirate 2nd Phase (Single Step) function allows you to aspirate a second phase of liquid into a tip that already has liquid in it. You input a target sequence for it to aspirate from, and input whether sequence counting is automatic (1) or manual (0). If automatic, the next time it interacts with a sequence it will treat the first untouched well as the start of the sequence. You can input the volume in ul either as a variable or raw value, or can input individual volumes for each channel as variables, raw values, or array elements. You can set the aspiration mode to 0 (aspiration) or 2 (aspirate all). Aspirate all will remove all available liquid in the well up to the specified volume without throwing errors if there is too little liquid. 
+  In the pipetting cycle settings you can input what tip type you are using and the dispense mode, which will then provide a filter for the liquid classes that are available for you to select to use, which are chosen from the liquid class database. You can also set the aspiration position. You can use capacitive liquid level detection (cLLD) to determine the liquid level height, at a variety of sensitivities, with 5 being the default (which means "set in the labware definition" for the specific piece of labware being interacted with). You can have pressure liquid level detection (pLLD) on instead of or as well as cLLD. This uses pressure changes in the tip to determine what the liquid level is. If using both pLLD and cLLD, you can input a max height difference in mm, which will cause an error if the detected height from the cLLD and pLLD differ by more than the set value. You also input a submerge depth in mm which determines how far below the detected liquid level the tip goes before beginning the aspiration. 
+  The channel settings available allow you to select which channels are being used in the dispense, which can be either selected via tickboxes, input directly into the dialog box, or input as a variable. The advanced settings let you control the immersion depth for the aspiration in mm, and whether liquid following during aspiration is on (1) or off (0). The advanced settings also let you input the Z speed of Search Level, in mm/s, and the dispenser stream of Search Level, in ul/s. Lastly, the advanced settings let you control the dispense back parameters, allowing you to input a retract distance in mm and a dispense stream in ul/s. The error section lets you set custom error handling responses to specific errors that will potentially occur during the process, and the responses are automatically triggered upon the error. 
+
+.. ven:function:: Initialize (Single Step)
+
+  The Initialize (Single Step) function initializes the Microlab STAR. It is required to be called the first time the STAR is used after being turned on. It is sensible to put it at the beginning of every method. It can either always initialize (1) or only initialize for the first run when turned on (0). The error settings dialog allows you to input automatic responses to certain errors. 
+
+.. ven:function:: Lock/Unlock Front Cover (Single Step)
+
+  The Lock/Unlock Front Cover (Single Step) function locks or unlocks the protective cover of the Microlab STAR. It can either be set to 1 (locked) or 0 (unlocked). The error settings dialog allows you to input automatic responses to certain errors.
+
+.. ven:function:: iSWAP Get Plate (Single Step)
+
+  The iSWAP Get Plate (Single Step) function uses the iSWAP (if the instrument has one installed) to pick up a plate from a specified position, in preparation for either an iSWAP Move Plate or iSWAP Place Plate function to be called. You specify the sequence of the plate to be picked up, as well as the lid sequence if it has a lid. You specify whether sequence counting is automatic (1) or manual (0); usually it is manual, it is automatic if you plan on moving multiple plates which are in the same sequence. You can set the iSWAP grip parameters, which are the grip height in mm, measured from the top of the labware, and the grip mode - this can be gripping the labware on the small side (0; the default) or the long side (1). Most labware comes with data in the labware file as to what grip width is required and the opening width before access, but this function has the option to override that, in which case you can put in the grip width and opening width before access, both in mm. The movement can either be just to a carrier (0; default) or a complex movement (1). The transport mode can be set to 0 (plate only), 1 (lid only) or 2 (plate and lid). If complex movement is chosen, three more parameters have to be input: the retract distance in mm, the lift-up height in mm, and the labware orientation, which can either be 1, 2, 3 or 4, based on which of the cardinal directions the iSWAP is pickup up the labware from. 
+  The advanced setting dialog allows you to set the iSWAP grip force (default 5, goes between 0 and 10), as well as the tolerance in mm, whether the grip is inverse (1) or normal (0), and whether collision control is on (1) or off (0). The error settings dialog allows you to program in automatic responses to specific errors. 
+
+.. ven:function:: iSWAP Place Plate (Single Step)
+
+  The iSWAP Place Plate (Single Step) function allows the iSWAP to move to a specified location and place down a plate if it is holding one. You input the target sequence which is the location you wish the iSWAP place the plate in, as well as the lid sequence if the plate has a lid. The movement can either be just to a carrier (0; default) or a complex movement (1). The transport mode can be set to 0 (plate only), 1 (lid only) or 2 (plate and lid). If complex movement is chosen, three more parameters have to be input: the retract distance in mm, the lift-up height in mm, and the labware orientation, which can either be 1, 2, 3 or 4, based on which of the cardinal directions the iSWAP is pickup up the labware from. You specify whether sequence counting is automatic (1) or manual (0); usually it is manual, it is automatic if you plan on placing multiple plates which are in the same sequence.
+  The advanced option dialog allows you to determine whether collision control is on (1) or off (0). The error settings dialog allows you to program in automatic responses to specific errors. 
+
+.. ven:function:: iSWAP Move Plate (Single Step)
+
+  The iSWAP Move Plate (Single Step) function allows the iSWAP to move to a specified location. You input the target sequence which is the location you wish the iSWAP to be moved to. The advanced option dialog allows you to determine whether the labware is gripped on the small side (0) or long side (1), as well as whether collision control is on (1) or off (0). The error settings dialog allows you to program in automatic responses to specific errors. 
+
+.. ven:function:: iSWAP Open Gripper (Single Step)
+
+  The iSWAP Open Gripper (Single Step) function allows the iSWAP to open the gripper and release the plate without placing it down; usually to drop it into the operator's hands or to drop the plate from a slight height onto the carrier with the intention of causing the liquid inside it to be disturbed by the motion. You can control whether the transport mode is for the plate only (0), the lid only (1), or the plate and lid together (2). You also pick the plate sequence, and can pick the lid sequence if relevant. You can determine whether sequence counting is manual (0) or automatic (1); unless you are doing it to multiple plates then sequence counting should be manual. You can specify whether the labware is gripped on the small side (0) or the long side (1), as well as whether or not to overwrite the grip data from the labware definition. If you do, then you specify the grip opening width. The error settings dialog allows you to program in automatic responses to specific errors.
+
+.. ven:function:: iSWAP Close Gripper (Single Step)
+
+  The iSWAP Close Gripper (Single Step) function allows the iSWAP to close the gripper and hold the plate without picking it up. You can control whether the transport mode is for the plate only (0), the lid only (1), or the plate and lid together (2). You also pick the plate sequence, and can pick the lid sequence if relevant. You can determine whether sequence counting is manual (0) or automatic (1); unless you are doing it to multiple plates then sequence counting should be manual. You specify the grip height of the labware, which is the number of mm that the iSWAP is gripping below the top of the labware. By default it is 3mm. You can specify whether the labware is gripped on the small side (0) or the long side (1), as well as whether or not to overwrite the grip data from the labware definition. If you do, then you specify the grip opening width. The advanced dialog option allows you to specify the grip force being used on a scale of 0 to 10, with 0 being low and 10 being high. The default is 5. In the advanced dialog you also specify the grip tolerance in mm. The error settings dialog allows you to program in automatic responses to specific errors.
+
+.. ven:function:: iSWAP Get First Plate Position (Single Step)
+
+  The documentation for this function has not yet been written.
+
+.. ven:function:: Wait for TADM Upload (Single Step)
+
+  The Wait for TADM Upload (Single Step) function forces the method to wait until the TADM data for specified pipetting tool (either the 1000ul channels (0), the 5ml channels (1), or the 96 head (2)) has been uploaded to a microsoft access database. 
+
+Microlab STAR Smart Steps
+-------------------------------------------------