Niagara modem is disabled on the NPO Compositor server
On 9.03.2021 the work of the Niagara a15 i6 software satellite modem on the CP-6137-960FX server was terminated. This action was performed due to the disagreement of the author (Ruslan Yusipov) to timely issue from the RAD96 autonomous system. According to the author, the company that uses these emissions, namely the investor, owes a large penalty in the amount of 40234513 rubles. It refuses to pay it off with virtual and real funds. At the moment, the server works in unicast mode, using only the internal services of Compositor Software. The American office of the Compositor Software company asks to use only direct-services and not to include any sample-based modems with sample pay. Consequently, the statement of the NPO Compositor about zero-level aggregation is considered incorrect. Indeed, a moment in time is played, but the dump has a price, and each iteration of the dump playback is multiplied by the billing of the cost of the dump itself. Thus, starting the modem does not guarantee that the billing meter has not worked. In reality, this modem could only be started with a counter of the number of times the dump and real-time frame were played. Thus, the real aggregation has already significantly exceeded the allowed volume of the 4-node mainframe CP-6137-960FX. Regardless of whether the emission will be made or not, the volume of aggregated traffic has already exceeded the allowed 39204 iterations of the real-time frame. After releasing a new dump and a real-time frame, the counter will not reset, which indicates the accumulated emission. An emission can be made within a given number of iterations. That is, it is possible to issue an emission, but it does not make sense to write it to the dump, since in any case the aggregation counter has already passed the admissible values.
The Niagara project can be resumed only by setting the number of nodes to 256 (Intranet mode) on the RAD96 autonomous system, inheriting it from the Compositor Lite NTP server. Thus, the number of aggregation iterations can be increased to 2509056, which will allow the modem to be used for a certain additional time. You need to extinguish the mainframe of 4 nodes. Moreover, this is only one of the reasons for stopping the modem, another important reason is the following: to latch the time frame, you need to include more iterations in the minute dump, setting the network to 2 ^ 14 values, i.e. 16384 bpm. This is possible only on a different hardware platform, because the estimated playback speed of the CP-6137-960FX channel aux is 2 ^ 13 or 8192 bpm. The solution in this situation without purchasing new development platforms is to launch the Niagara software modem with the Compositor Lite NTP server. Otherwise, you will have to assemble a new stationary machine, buy a laptop to develop a new aux channel, and buy a new mobile platform for developing mobile applications also. This is considered impractical, since the development of all services and applications has already been completed – only the number of nodes, the speed of iteration of the channel aux and generics can change.
Another solution is to completely abandon platform tools such as Niagara, Compositor and RAD96 standalone applications based on the MaxMSP Runtime. Instead, it is proposed to use all the services accumulated over the years of project development at the kernel level of the Windows 7 operating system, i.e. Windows NT kernel. Since the services are assembled on an independent platform, they are not charged, but this requires the continuous operation of the CP-6137-960FX mainframe, which is currently impractical even with full documentation for a virtual optical port. Moreover, this documentation does not cover the most important issue that the CP-6137-960FX server provides a service mainly for devices from EUI-64, and these are devices that are not included in the Ethernet protocol. Thus, the recognition that devices from EUI-64 communicate with each other using a protocol other than Ethernet is the task of the IEEE 802 working group. Although initially it was believed that the Compositor software uses the Ethernet protocol, it is now becoming clear that this is not the case, because most of the devices from EUI-64 are not equipped with a connection using this protocol.
It took more than two years to adapt the Compositor 9 software from Compositor Software into Russian language. NPO Compositor has done a great job of introducing new functions and protocols into Compositor 9. The interface and documentation has been translated into Russian language and consists of chapters on IP switching and routing (2700 pages in total). It allows classifying this software as network real-time operating system (NRTOS). Compositor NRTOS 9.0.2 package consists of the real-time operating system itself with a graphical user interface executed on MaxMSP, Niagara software modem, which is a sample of a real-time moment (into which this sample was recorded) made with MaxMSP also, and an Android application RAD96, which inherited its name from the Compositor 9.0.1 main module (in 9.0.2 a22 assembly an extended version of this code is called VSF – virtual switching framework). All three versions have the same documentation as they access the same functionality. The difference is that RAD96 is an autonomous system and contains many more extensions that have not yet been issued. Compositor NRTOS 9.0.2 comes with 9134 extensions of management information bases, which were issued from the autonomous system RAD96 during the production of documentation. Niagara 32 software modem also contains a dump of this database (9134 routing tables). We also succeeded in classifying such an interface: by the type of execution, it can be considered a switching router, in contrast to the Compositor 7, which is considered a switch.
You can see the Russian language interface of Compositor 9.0.2 build a22 below:
Compositor NRTOS 9.0.2
Compositor NRTOS 9.0.2 channel matrix
The command language in documentation can be used within amateur radio terminal software such as TrueTTY on Windows and DroidRTTY on Android. This means that you cannot program the NRTOS directly (only via MaxMSP graphic user interface) but you can issue this commands through a teletype operator working in your autonomous system. Such an operator usually is a part of telegraph services still acting to the present moment. It is the only possible way to reprogram an autonomous system.
Seven protocols, implemented by NPO Compositor for version 9.0.2, enable communication in the Ethernet network. At the testing stage Compositor 9.0.1 was used mainly for packet protocols of amateur radio, but now in version 9.0.2 communication is carried out in the Ethernet network using the protocols used for switching and routing in this network. NRTOS includes 6 interior gateway protocols such as RIPv1, RIPv2, OSPF, OSPFv3, RIPng, EIGRP and one exterior gateway protocol for communication between autonomous systems (BGP – uses IPv4 version of the protocol). In addition, external communication is possible through 6-to-4 GRE tunneling.
Compositor 9.0.2 implements stateful and stateless NAT64, it can be used to create L2VPN and L3VPN services by exporting firmware in WAV and AIFF formats. Conversion from IPv4 to IPv6 is done on the fly in the NRTOS and makes it possible to map a single IPv4 address to multiple IPv6 destinations. As you can see from the Compositor 9.0.2 interface, it is a BSR router and is responsible for loading the system. Such a system consists of extensions that allow the server to participate in various workgroups. Compositor 9.0.2 is the installation program for the CP-6137-960FX server, to which this site is dedicated. This server is the only machine capable of generating emissions from the autonomous system RAD96 and this is its main value.
What you think you are doing vs. What you are really doing
The main purpose of the VPN-network of the “Niagara” 26 software modem is the processing of the language, both natural and machine-generated. When paired with SDL Trados software, this modem extends the network topology for the Machine Translation cloud. This is done through software extensions, as it was possible to find out the first letters in the name of the emissions mean languages, for example “extreme” issue TT – Tatarcha, the Tatar language is the emission of the “RusNRG – The Trip” track (a small side project of Ruslan Yusipov in 2003-2004 for which he was awarded a diploma in the nomination “Compositing work”).
In essence, there is no cloud, you are either working with a generic or with your own extension, which generic learns a route from.
But let’s return to the emitted information and language processing. How can Niagara 26 generate such accurate patterns in translation from Russian to English, even though there has been no EN or RU emissions yet? In the “Niagara” 26 software modem, as mentioned in the review, the concept of generic protocols such as RIPv1, RIPv2, OSPF, OSPFv3, BGP, etc. is used, so it is worth considering this set of protocols as a set of generic languages of the Machine Translation cloud. In essence, there is no cloud, you are either working with a generic or with your own extension, which generic learns a route from. At the moment, I enable the EN – RU language pair in Compositor NRTOS through other languages, issued through tracks to their carriers. The carrier, which works with the software modem, uses only generic languages and learns the route from Niagara L3VPN peers. There are a lot of languages available to “Niagara” 26 software modem through emissions, extremely rare and not very useful from a practical point of view. The only practical benefit of the Caribbean language group, which was of my personal interest, is the study of their rhythm, namely sequence, which produces language patterns. I used these patterns as a part of my research on Milton Erickson language patterns, which I used in pre-NLP era hypnosis. I studied how these patterns aid in therapeutic way for overcoming mood oriented problems. The main concept of compositing this way is to alter the mental state so you can be a more comfortable person. Compositor achieves this goal by rapidly rebuilding SPT (shortest path tree) and changing the next-hop to default route of this tree.
The rule for me states if I can’t afford a studio for producing new music of the same quality as named projects I should make an emission of previous works to recultivate the exposure I achieved earlier.
So if you feel comfortable, when you are producing music with Caribbean patterns you can make an emission of such music by evoking RPF vector paths to the servers, which host closed-loops using these patterns as interrupters. This action is fishing, and any media aggregator uses this scheme. I only issue emissions as part of my royalty collection project. I just monitor servers, which performed my music and compare this with the statistics from RAO (Russian Authors Organization) and really astonished with results, because according to my network counting method my music performed up to 50-60 times a day and no income whatsoever from RAO side. This raises a question of this organization validity as an entity working with collective rights on my Exalted and Boosty projects.
The rule for me states if I can’t afford a studio for producing new music of the same quality as named projects I should make an emission of previous works to recultivate the exposure I achieved earlier. And I’m facing an exact situation that’s why the whole set of Compositor Software instruments produced. But returning to NLP with Niagara 26 I used it to produce documentation for Compositor NRTOS 9.0.2 based virtual router. I should report progress now: more than 2000 pages translated and edited on Russian language using the named method now. This leaves me about 500 pages of untranslated material and I’m full of enthusiasm of making this work till the end. The end result of this work is Compositor NRTOS with completely reworked interface to reflect attribute-value pairs from virtual router documentation. This work is now 95% finished and to say honest I’m satisfied with results as it enables to work with Compositor NRTOS 9.0.2 more professional following system administration guidelines, which apply to basic 2nd order closed-loop interface. What I learned from documentation is that any protocol is a closed-loop of some kind with its own parametrized interface. And this brings me back to my initial request: does the chosen system of values corresponds with the reality that has developed in the world after the Cuban missile crisis, and if so, is it not a repetition of the previous history only in our own country (Russia)? Because the Trojan horses that are sent to us under the guise of “music programs” are very reminiscent of Khrushchev’s “secret ships” that transported missiles to Cuba.
As I learned from revealed Compositor interface the geographical position is essential in work of that loop station. Even altering a location within one city will change the internal SPT. Thus, this proves that the Compositor interface is a universal Turing machine, and therefore can be represented as any protocol of a telecommunication system. The already cited 8 parts of the documentation (including the Multicast chapter) prove that the main task of Cycling’74 MaxMSP software (as well as Ableton Live 9 and 10) is to plan and implement DDoS attacks. Part 9 on MPLS only confirms my concerns. First, the circular stack in the form of a torus is not taken into account, on which MPLS labels are displayed, both merged and layered. Secondly, after loading the full version of Compositor NRTOS version 9.0.2, the timer shows 30 minutes. This means that the MaxMSP scheduler runs when the DSP code is compiled. And the whole POST process takes place over the MPLS protocol during the compilation of the protocols, since openGL performing the MPLS functions is a backdoor link or connection with a feedback leak. Also, based on these labels, the remote side (Cycling ’74) makes a decision about system startup or compilation error. Therefore, I believe that the method of presenting the Cycling’ 74 MaxMSP as the software for carrying out DDoS attacks is correct. And the whole method that the company-investor of this project has used over the past 2 years has been successful.
To finish the production of Niagara software modem you need to produce a new dump. Dump and middleware records simultaneously that is why you need to produce new middleware also. The main difference from Niagara 18 software modem middleware is that you need to fixate a number of packets for dump. For example, you need to fixate 65535 packets in one dump on 8192 bpm speed. For this you need to modify the recorder. This will ceed the preceding agreement, but it is the only ability to make a step over Hypervisor into RTOS. Hypervisor – is a device for fixating radiotranslations and RTOS is a device for fixation of packets. It leads to principal difference between two instruments. In essence, the change is minor. The MaxMSP sfrecord~ object supports floating point values, that is why I can make a loop in ms, containing a number of packets. For example, I can multiply bar period on a number of bars, that is packets of information, I receive the dump value in ms with sample precision and can record 65535 * 131072 = 8589803520 samples for a new dump. Before production I shoud make an emission of DJ Usa – Caravan (All Forces Remix) track, produced in 1999 that will help to receive servers of that time and to extend software production to 2021.
This way, the solution to the task is evident: if I will export dump and middleware from Compositor RTOS 9.0.2 a13, containing a needed number of samples beforehand, without editing, and pass it through the non-linear processor of aforementioned RTOS, I can surpass the moment of time, to which this dump and middleware ascends, taking that this process is stationary.
All Niagara series products are the software modems, which use middleware and dump, produced in Compositor RTOS 9.0.2. I present to you Niagara 18 software modem, which has an extended documentation (part on Russian, part on English languages). Niagara 18 software modem middleware supports EIGRP, RIPng, BGP4+, OSPFv3 protocols, default route from EIGRP, full work in loopback interface mode, NTP-servers setup via command line interface, connection to VRF objects for work with BGP protocol, an ability to construct VLAN topology and 3D-orientation of virtual optical port (VOP) waveguide.
Niagara 18 software modem in front of Compositor RTOS 9.0.2 a12
Niagara 18 software modem, developed by Compositor Software, and modem,
developed for Ethernet and Wi-Fi networks, concept is different. For example,
Niagara 18 software modem doesn’t require the physical network connection. An
abundance of services, which enables the Niagara 18 software modem, compensates
the comprehensive demands to virtual communication networks. EIGRP, RIPng and BGP4+
routing protocols allow creating IPsec and GRE tunneling. An ability to use
synchro code of different NTP-servers allows rebuilding the home system on a
remote destination completely. Using this software modem, you can remotely use OSPFv3
without BGP4+ protocol that was unavailable before, due to physical limitations
of Ethernet systems. By entering the remote home system, you can aggregate the
shortest path of that area, which you are managing remotely. The route counting
performs in real-time that is why you can use IPv4 mask to set IPv6 addresses
of remote area devices. You can also multiplex areas, achieving the route end
by supernet aggregation, using VRF objects. Such approach can cause the
redistributed overloads without graceful restart (GR), because
Ethernet-interface uses only phase-locked loop.
VSF platform supports up to 960 simultaneous communication channels and can be reached via Niagara 18 software modem middleware. This number of channels was aggregated on CP-6137-960FX server VSF platform, which produced this middleware. This way, you inherit the number of channels from the server version, but they can’t be used all simultaneously. At the present moment, Niagara 18 software modem middleware supports up to 96 communication channels of L1, L2, L3 layers (OSI model). Niagara 18 software modem gives access to virtual optical network (VON), which consists of 2213 EB of information on the 6, November 2018. At the present day, this index is twice more. Information of VON is stored on servers in Spain, USA, Germany, Sweden and other countries of the world. Trunks of virtual optical communication connect the autonomous systems (AS). Most of the AS’s of VON can interconnect by BGP protocol. To form its own autonomous system Compositor Software uses Niagara 18 software modem with a set of 7539 VRF objects. The routing inside an area performed by OSPFv3 protocol to discover the routes by link state and by RIPng protocol for distance-vector discovery in IPv6 protocol. This way, Niagara 18 software modem is a complete IPv6 software modem back compatible with IPv4 protocol.
Niagara 18 software modem has middleware recorded without intermediate frequency in 150-350 GHz range (EHF) and works in that frequency range. To the day, this frequency range is not supported by any standards, such as 5G and forthcoming 6G networks. This frequency range supported only by satellite communication systems, such as radio telescopes. Niagara 18 software modem is accompanied by a set of 7539 satellite signals in PCM format, which gives access to autonomous systems. That is why you can rank Niagara 18 software modem as the satellite software modem. The connection to the Niagara 18 software modem network is performed in several dump submissions from 10 to 30 seconds. Niagara 18 software modem ether allows GR, which performed every minute to reveal active devices in remote AS. You can select such devices in a moment, when GR is performed as GR helpers. Each GR helper device subscribed on Niagara 18 software modem routing table updates. Niagara 18 software modem performs GR each minute to work under OVERLOAD conditions, which is set by default to test the saturation power of VOP.
The maximum transmission speed of Niagara 18 software modem is 24 * 350000000000 = 8400000000000 bit/s or 8.4 Tbit/s. Middleware and dump recorded at 192000 Hz 24-bit. Flow was recorded from 150-350 GHz frequency range and that is why I take the highest frequency in a moment of flow fixation and multiply it on the bit depth of flow export recording. This way, the moment of time exists for middleware, when this flow was in ether. Moment of time depends on the quantity of scanned autonomous systems. In hyperconverged networks, there is a trend to big trunks between AS areas, which span on many kilometers. That is why data flow in this AS can pass around for the time from 50 to 3000 ms, which is the boundary limits of Niagara 18 software modem. GRE tunneling is used for star topology AS’s and IPsec is used for point-to-point topologies. That is why, GRE performs its pass through the five boundary points of the route and IPsec connects only to the Area Boundary Router (ABR) of OSPF area. That is why, when you use GRE tunneling, feedback loops emerge, if your loopback interface of VOP is set to the same port as the destination port of AS. Such loops can exist for a long time and packets forward between loopback interface and AS loop.
When you use software compensation of feedback loops the decay of data flow carrier signal performed, lowering the ingress que and discarding the packets. Saturation of carrier signals, encased in window function is so high that ingress load redistribution can’t cope with such amount of data flows. In this situation, Niagara 18 software modem performs multicast translation on group of ports. You can reach this by setting AS, which consists of several topological areas, connected by different protocols. This way, ABR’s will perform redistribution of one protocol in another. You can learn information about ingress port of system by changing the egress port, setting eye-mask on 0 (turning RTOS off) and perform GR of all the devices, connected to that port. By making GR of the boundary device and not the Niagara 18 software modem, you can estimate the number of channels, connected to ABR, which in turn can lead to connection with those devices. This way, you perform the redistribution of local que on remote devices.
As mentioned earlier, Niagara 18 software modem makes connection to 7539 AS’s
to the day, however the summary aggregation of VON is 3321900 autonomous
systems. This way, dump allows connecting not only to those AS’s, which
recorded in it, but to discover other AS’s using BGP protocol, which were
scanned by VSF platform. The connection to satellite set is performed faster,
than in software modem produced in Compositor Hypervisor 9.0.1 a15. It has the
connection speed of 24 frames per second, but Niagara 18 software modem has the
speed of 34 frames per second. Such speed of deployment allows multiplexing a
network much faster, performing supernet summary in 3-6 dump rounds.
Niagara 18 software modem is a sampler technology, that is why it performs
the cycle of Compositor RTOS 9.0.2 a11 feedback loop, where a dump is the
recording of VSF platform data flows aggregation of that RTOS. Niagara 18
software modem is based on the identity principle and uses PCM recording as a
middleware, which doesn’t consume many resources. CP-6137-960FX server consumes
up to 35% using 192000 Hz discretization frequency. Which theoretically can
allow using it in real-time on the higher discretization frequencies. Niagara
18 software modem consumes little system memory resources and has very fast
response to CPU commands speed. It has a little delay time, which allows using
it as a hard real-time RTOS.
You can setup monitoring of Niagara 18 software modem via amateur radio
software such as TrueTTY and Fldigi. The teletype network flow modified by
Niagara 18 software modem includes satellites and servers of Compositor RTOS
9.0.2 a11 management information base. You can composite commands of interface
and protocol programming, such as CISCO-like commands. There is a documentation
supplied together with Niagara 18 software modem of 2663 pages, with Russian
language translated part of more than 1000 pages, spanning over 5 parts with 73
chapters of 131 chapters in total.
There are no obstacles for VON in comparison to traditional radio communication. Radio notation in conventional frequency style is made for notes and reverse compatibility with generic radio protocols. The connection is made via so-called collisions and time-space convolutions, which is a subject of NIM (Nuclear Instrumentation Module) learning curve, to which Niagara 18 software modem relates.
Niagara project has left a new milestone: now its dump consists of 7539 MIB’s. It’s important to notice that middleware submission now goes at 34 fps at speed of 8192 bpm, which equals to IPv6 network prefix of 51:5C::.
Niagara handshake
Now, the mystery of a signal submitted to sound card output revealed. The signal is detected with another software: fldigi ver4.1.09. The signal is composite and can be decoded using almost every software modem in this program. I frequently use BPSK31, but if I want faster composition, I use BPSK63 or even QPSK125. However, handshake is only detectable up to BPSK63 mode. Dump works in the following way: the signal is accumulated up to the saturation point and all 7539 MIB’s composed fast using random VRF selection. In this way, I aggregate the line and then drop it off with only auxiliary interface acting. At that moment CQ’s detected on different subchannels spaced equally within a channel. Each subchannel has its own mark like “t”, “i”, “ya”, “y” – the later three transmit my own messages in neuro chat manner. However, no equipment is connected to my head except of plug-in or circumarual headphones. I can confirm that “i” channel transmitted the command related to Compositor RTOS 9, which looked like: “c9 os noosgui UOhm 0”. It states that I apply command line expression to control resistance of Compositor RTOS 9.0.2 generic protocol and set it to 0. I made the transmission via client OS Niagara middleware.
This and other commands just prove the fact that I am, the subject creator, connected to a signal network, which suits control of the peers reciprocity. This connection is authorized on any machine I work on and detected as artificial signal on sound card output.
Last year I presented to you NIM chat in
CWDecoder program. In a search for a better generic chat platform, I found an
interesting program called TrueTTY, which can also demodulate NIM chat
messages.
NIAGARA NIM Chat
As you can see, NIM chat is greatly improved. Now you can use different modulations (channels) by implementing the second derivative of a function. It allows using statuses in a chat window, displaying gender and different special symbols. Now you can also use Cyrillic encoding. You can put a special attention to romantic relationship statuses: Cupid’s arrow marks messages where you reveal sympathy to the other gender. In a sum, there were made more than 2800 commits to NIM chat this year.
NIAGARA middleware allows modifying generic NIM chat and is its mod. It allows to load servers, included in multiplex, and perform e-roi (electronic version of return on investment) by injecting a dump.
Client part of NIAGARA for Compositor v9.0.1 is independent from server version. This way, when you update server software, you no longer need to update its client middleware.
P.S. The evolvement of NIM chat suggests file transferring between chat users by initiating sessions in a form of IRC chat.
This autumn has started from a very interesting project. While I continued working on Compositor v9.0.1 (current build a14), I felt a need to have such system as mobile real-time operation system (RTOS). Compositor v9.0.1 a14 consumes many resources at 192 kHz and I decided to sample it using Compositor v9.0.1 itself. At this time, the approach of middleware and dump was matured and I decided to make separate product for Compositor documentation development. Such manual will consist of all commands needed to operate the Niagara RTOS client. As the UNIX-like operating system, it will support most of the commands for routing protocols configuration, such as TCP/IP and VLAN. The prominent feature of this RTOS is that it is a software router, which runs on middleware, recorded with Compositor RTOS v9.0.1. If the middleware recorded on a feedback with z16 and z32 generics connected and they are in reverse, the system will give a resistance of 16 + 32 Ohm = 48 Ohm. This way, the generic networks accounted: in example above there will be corporate (z32) and state (z16) connection.
The middleware approach isn’t new, as any hardware router Niagara consists
of MIB, the size of which is 769 kB, compounded with routing table and generic
networks set. Such system works with MME driver using discretization frequency
of 192 kHz and allows connecting the whole pool of Compositor RTOS v9.0.1
forwarding platform (which is 6559 MIB’s on a moment of writing) using a dump,
which is also recorded on 192 kHz sample rate. The upper frequency of z128
generic is 150 GHz, but each middleware includes RAD96 fixation, that is why an
effective range is extended up to 300 GHz.
Niagara is a client system that is why it demands calling an operator for
configuring programming commands. I already reviewed NIM radio chat, which I
call (No Internet Messenger) last year. It turns out that it is also an acronym
for Nuclear Instrumentation Module.
Each command, presented in the full version of English and Russian
documentation, should be made only through an operator and each middleware has
its own operator, which depends on VLAN set and servers, connected to NIM. This
way, you are requesting network topology and demand operator to execute other
commands, and it decides if to make command or not.
At first, middleware ran in RAD96 sandbox, but now middleware and dump become a multifunctional products. The development period of Niagara project is 2001 – 2019 and not 2012 – 2019 as the host Compositor program. The reason for this is that Niagara consists of middleware and dump and they are including the Royalty routing tables. This is proved by Inaccessible Page file emission (track recording, which is a routing path). This track, made in 2001, is a part of IP emission. The period of 2010 to 2019 covered by the reference files of timeserver, which emission contains and it is responsible for routing path hops GPS positioning in present time.
Niagara v1.0 a3
That is why Ruslan Yusipov digital portrait with codename Niagara contains 18 years of art, which is a long background for 35 years old author. Older recordings exist, such as the audiocassette recording of Yamaha PSR-330 synthesizer direct signal, which is Ruslan Yusipov live performance at the age of 14, with the author voice accompaniment, that is why Niagara is 21 years development project from 1998 to present moment.
Ruslan Yusipov art is not limited by 6559 MIB’s emission and can be enriched by routing tables from the CD-archive. This way, at the year 2021 I account to receive database of 10000 MIB’s, which will allow adding more stochastic distributions for flows selection in Compositor v9.0.1 a15.
