Access extended data types within Krunch Pipeline

When extending or creating a data type required by Krunch Pipeline, proceed as follows:

1. After extending the RealTime database (RTDB), perform the command with the -b option when generating a new database model to give it a unique namespace.

    Example:
    set-silo RealTime
    GenerateDatabaseModel -b OASySDNA.RealTime.Data.Model.Extensions

2. Modify the project .csproj file accessing the data type to reference both the baseline and extended versions of the data model. 

     Example (both of these files are referenced by the .csproj file):
     OASySDNA.RealTime.Data.Model.dll
     OASySDNA.RealTime.Data.Model.Extensions.dll

3. Override any Krunch Pipeline step or data converter accessing the extended data type within the applicable pipeline .json file.

     For further information, see either Override a step within the Krunch Pipeline Data Stream or Override a baseline Data Type Converter.

4. Modify the step or converter to reference the new namespace, in addition to the baseline data model namespace.

     Example:
     The namespace of both the baseline and extended model namespaces are declared at the top of the file:

     using OASySDNA.RealTime.Data.Model;
     using OASySDNA.RealTime.Data.Model.Extensions;

5. Modify the code to explicitly reference the extended data model for the extended type.

     Example:
     If the analogtype enumeration was extended, change the code to explicitly reference the OASySDNA.RealTime.Data.Model.Extensions data model when accessing
     an Analogtype in the code:

     var analogInputType = (Data.Model.Extensions.Analogtype)setRecord.ReadField<Byte>("anain.type");