Now introducing actual implementations of the long awaited and very tightly kept UDCN scripts. The infinites refer to our vector ability of infinitely traversing numbers, quantifiers, and other vectors without end. Traversing upwards of mathematical exponents of exponents with reasonable and readable representation we’ll learn that even the most robust and expansive of mathematical operation become less effective at changing the glyph quantifier the larger the quantifier. The current implementations are very fluid and responsive. Later versions include a functional approach to cross script mathematics for truly infinite range and Relativity.
Introduction to the R3 iteration method.
As outlined in the R3 UCDn Infinite Project Documentation, Training, & Script Comments. the R3 method utilizes a very clever methodology consisting of referencing the values of each quantifier as separate parts of a complete quantifier whereas each of the smaller quantifiers act as identifiers of their value separated in 3 Quantifier Groups. [Rate, Range, & Relativity.]
According the above test and documentation; the Rate, Range, & Relativity referring to the 3 separate Groups of the main Quantifier being the (left number [rate]), the (glyph-symbol) [range] and lastly (the right number or non-value). [Relativity].
The Rate is simply the first value to count quantification against or for. This means that the first value is the smallest of the quantifiers but represent all or no value of the rest of the quantifier Groups. At base this may seem complex but indeed is extremely simple.
Example:
If the [Rate] is 1.5
1.5
In the above figure the [Range] is -1 or non-existent this simply means that there is no range or quantifier for our first Quantifier group to match against.
1.5K
In the above figure the [Range] is 0. This simply means that the range or quantifier group is present but has not iterated so it is within the thousand range
1.5M
In the above figure the [Range] is 1. This simply means that the range or quantifier group is present and has iterated once it is within the first illion range [Million] aka 1-illion.
1.5B within the second illion or 2-illion billion etc…
As shown in the UDCn Tests this number/quantifier method can really move seriously fast and efficiently. Accuracy could be debated however key developers within the project are adamant that the numbers are as precise as the user outlines in the residual numbering sequence algorithm. Though not document nor necessarily explained they contest and based on the current results… I’m leaning toward believing them. Regardless of them not completely explaining the loss of numbers they tell me that within the source is the input parsed into numbers using a programming feature called regex. Using this feature the devs explained that they capture validations rather it is a valid data type and the data type is then parsed.
What is a data type and what is parsing?
A data-type is simply a type of data. There is a number of data types to name a few. We’ll only go with what I could retain which was that INT or integer refers to a whole number. FLOAT or floating point refers to a decimal or a DOUBLE which is the same as a decimal except that it only goes to 2 decimals such as 1.00 and a STRING is letters like a message. Between the different data-types is how they could be parsed. Parsing is simply translating the date to be read. So to put it all into perspective. The UDCn Test uses advanced regex technique to parse what data type the user input and translate it into a readable glyph. If that makes sense.