Compositor SoftwareCompositor Software

Category : Algorithmic Composition

By ruslany

What you think you are doing vs. What you are really doing

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.

By ruslany

Compositor Software extended services set

Compositor Software extended services set

Compositor Software server has confirmed its success in supporting the remote workflow. Even the set of services that was named in a previous post ensured the smooth operation of all network resources. However, for a full-fledged work, this was not enough. I resumed work on the implementation of all services from the Network Real-Time Operating System (NRTOS) versions 3.0.3 – 9.0.2. Since the main task of the server is to create a network map with a high depth of topological viewing, I implemented two more MDL12 services and feeders of the 3rd version, such as AI-RT1024, FF8, N9000, TC25, which allow working with corporate PDH and SDH network hierarchies and broadcast them in VLAN using ARP for the analog IP radio interface.

Thus, a common set of services now:

7 RAD36 servers
2 MDL12 servers for radio telescope and IPTV
1 VoIP server
4 FF8 Feeders for ARP Protocol
4 AI-RT1024 Feeders for SDH
4 N9000 Feeders for PDH
4 TC25 Feeders for VLAN
1 RAD96 server extension to work with the Niagara igniter (VPN)
1 RAD96 Autonomous System

Protocols:

STC2k – X.25
RTC4k – RIPv1, IS-IS Layer 1
RTC8k – RIPv2, IS-IS Layer 2
RT-z8 – OSPF
RT-z16 – OSPFv3
RT-z32 – BGP
RT-z64 – RIPng
RT-z128 – EIGRP

All services are compiled and operate at the kernel level of the operating system. Only this approach allows maintaining the scalability of services in a hyperconverged environment. It do not lack of services, everything looks very worthy at the level of a serious manufacturing company. This approach provides the server with the emitted database and allows you to generate new links on the fly without the need to record and enter them through the injector.

By ruslany

Compositor Software expands the number of existing DRM servers

Compositor Software expands the number of existing DRM servers

After an important step of building standalone applications using Compositor Software code, it became possible to organize the work of a new DRM server. That is, the physical server CP-6137-960FX began to be commissioned. As mentioned earlier, at the development stage it was possible to launch just one RAD36 virtual DRM server and it took about 4 hours to compile at runtime. This made it possible to provide up to 12 licenses for concurrent work of Compositor Max for Live or SASER Max for Live devices in the year 2017. Having exported the code and assembled 7 RAD36 virtual servers for the Windows platform independently of MaxMSP, we managed to start the workstation and successfully perform basic operations of text editing in Microsoft Word 2013 and working with Compositor Software Max for Live devices in Ableton 10 using it. It allowed expanding the total core density to 252 “Compositor” hybrid cores on a physical machine, increasing the number of simultaneously operating licenses of Compositor Software for Compositor Max for Live and SASER Max for Live up to 84 virtual machines, which equals 84 real-time cores or 84 three-layer cores. The uptime has increased significantly – the bootstrap process takes only 5 minutes to load CP-6137-960FX server fully. Niagara modem-radar and various Ethernet injections are used as an ignition, when workstation operates in Ethernet network.

Thus, the workstation converts Niagara injections and makes all server modes work, and there are currently 13 of them, including 7 RAD36 servers. Next, I’ll give a complete list of collected and working Compositor Software services for the Windows platform on the CP-6137-960FX server:

VoIP Service – NIM Chat Voice Service
STC2k Service – Sonar for Civilian Control of underwater and surface ships
RTC4k Service – Radar for Civilian Airspace Control
RAD36 1-7 Services – digital rights management servers for launching Compositor cores (total of 252 hybrid cores).
RAD96 Service – Standalone Rotator System for Docking RAD36 Virtual Servers
RAD96 Ext. Service – expansion of the autonomous system for working with external Ethernet connections of third-party equipment
Telescope Service – Telescopic Near Space Signal Approach Service

So, after the introduction of the CP-6137-960FX server into full operation, it was possible to provide working time for up to 84 Compositor users working in single-layer and two-, three-layer Compositor Software programs concurrently. In addition, this applies to standalone applications and Max for Live devices, such as Compositor Max for Live, SASER Max for Live and Compositor 4 Max for Live. I’ll also clarify that three aforementioned Max for Live devices are fully compatible with Ableton 10 and Max 8.1.3 Max for Live, which opens up the possibility of expanding the presence of Compositor users in NIM chat on MAC OSX and Windows platforms.

Compositor v9 in the studio

By ruslany

RTOS version 9.0.2 a16 assembled

RTOS version 9.0.2 a16 assembled

It took more than 1.5 years to work on solving the problem of Compositor AV Extended interface break-through (which is the main interface of RTOS). This problem occurred during the dial-up of routing tables for establishing a tunnel connection. The way to recreate it: first, RTOS protocols are dialed by injecting routing tables into them, and then RTOS interface is turned off and on again. When the interface turns on, the entire database of the routing tables, which fills the buffer, floods into the interface, which cause a man in the middle attack, that is, an attacker gained access to the interface and induced it to inherit the route of its device. During this time, I made emissions in an attempt to understand how to solve this problem and, finally, it is solved. Now it is possible to configure each protocol from the passive interface state and take a pause while turning interface off in order to listen to the remote channel, and then go into passive mode again. Thus, you can achieve resolution from each of the seven RTOS protocols.

In Compositor RTOS 9.0.2 a16 it is possible to set one interface identifier for the entire protocol configuration session, and to do the training only in passive mode, as previously assumed. The next task in debugging RTOS is the fight against constants. It is one of the most important tasks of both radio security and cybersecurity. Through the introduction of constants, Ethernet devices position themselves, occupying the most convenient places in the network topology. This mainly applies to devices that frequently change IP addresses, such as smartphones and laptops. In order for the RTOS core to take priority of the host, the device must serve as a host for many devices. This is confirmed by Compositor Software database, which has been expanded to 8156 management information bases (MIB). Now that the Compositor RTOS manages a database of more than 8,000 devices, CP-6137-960FX server can be considered as a host, regardless of its physical connection to the network, through the Internet service provider. In fact, what I’m doing now is the continuation of the development to include more VLAN’s and create a VPN network segment. In the latest build, I have already managed to “shoot” the packets in several sessions. You can hear one of them below:

This method of feeding wave tables is a priority for communication devices, because it helps to break the synthetic ether by packet transmission. Since there are many packets, and each of them carries different information at different moments of time, the semantic base of the Compositor RTOS language is explained. In view of this, it makes no sense to enter the names of packets in the main interface, and I need to leave them in a VRF tables section only, focusing specifically on the tunnel windows. In addition, this approach allows using the Compositor RTOS interface as a tunnel interface with the ability to connect to multi-channel protocols, such as OSPF.

By ruslany

Niagara 18 software modem review

Niagara 18 software modem review

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 18 software modem review:

  1. Split Horizon support
  2. 3321900 AS’s in VSF platform
  3. EHF frequency range (150-300 GHz)
  4. 8.4 Tbit/s transmission speed
  5. OVERLOAD work mode
  6. Poisoned reverse with -rm ability
  7. 34 fps connection speed
  8. No delay time
  9. Management and monitoring via teletype network

By ruslany

Compositor reached the fastest bpm in music sequencer

Compositor reached the fastest bpm in music sequencer

8192 is the number of beats per minute Compositor AV Extended radio channel reached in Compostior v9.0.2 Hypervisor. The number is not taken random. It is 2^13 and forms 13 bits of first hextet of IPv6-address. The next 3 bits are taken from the multiplier. So, yes now Compositor officially supports IPv6 addresses. For this, auxiliary speeds of up to 214 omega reached, which is 14 omega larger than highest generic protocol deployment speed.

Compositor v9.0.2 Hypervisor (Mainframe)

Now, all generics assigned to protocols. Here is the full list of Compositor v9.0.2 Hypervisor supported protocols:

RTC4k = RIPv1
RTC8k = RIPv2
RT-z8 = OSPF
RT-z16 = OSPFv3
RT-z32 = BGP
RT-z64 = RIPng
RT-z128 = EIGRP
RAD96 = VSF

Compositor v9.0.2 Hypervisor (TCP/IP window)

As you can see, it is a major achievement in revealing Compositor technology, which stems in its implementation as Ethernet router software, namely Compositor RTOS.

By ruslany

Great renaming is coming in Compositor project

Great renaming is coming in Compositor project

Dear reader, it is time to report the coming changes in Compositor Software project. For the five years, I performed the comparison of telecommunication industry technology and the one developed by me. Here what I’ve already found:

Compositor Pro = NTP-server

Compositor Max for Live = SNTP-server

Accordingly, Compositor Pro and Compositor Max for Live will be reworked to reveal this paradigm. There are 24 official UTC time zones as well as 24 bands in Compositor Pro and Compositor Max for Live. The function by which these bands are distributed is time-invariant non-linear function (read the full documentation here). Therefore, bands of Compositor are time zones. Stratum parameter of NTP-server is permutation. There are 12 Stratums in my NTP-server. Using kick parameter, you can set subnetwork mask. This parameter, together with clap and hat, forms modulation, which installed in parallel to time zones deployment tempo.

NTP-server can create time collisions by granulating the central flag of modulation interrupter. When injected collision comes to the input of the receiving device, this device establishes a connection with NTP-server and takes its synchro-code, which is translated by sub-bass instrument. It is the modulation interrupter flag. The mangling takes place in time component, which is the time-displacement (substitution of time).

Tempo is the first octet of IPv4 address, and multiplier forms the next three octets. There are only IPv4 addresses in NTP-server. NTP-server doesn’t have access to broadcast addresses and to an address of local machine, but uses the range of 54.1.54.0 to 140.3.0.0. Therefore, the role of Compositor Pro was to install the stochastic distribution with the route of 120.1.54.0 to 120.2.24.0 and to perform collisions with the devices of that range.

The reason I made the NTP-server is “creation of artificial intelligence using non-invasive method”. By this, I mean active use of ACL lists and flows filtration when loading Ethernet servers (kernel extensions, which are recorded in MIB’s database of Compositor Software). Compositor Software clients produce traffic when working with software, which is exported into flows, using the half-duplex MDL12 modem. These flows contribute to device pool of Compositor RTOS kernel extensions.

NIAGARA NIM Chat

By ruslany

NIAGARA NIM Chat

NIAGARA NIM Chat

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.

By ruslany

Niagara project

Niagara project

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.

By ruslany

Zero-Layer Aggregation

Zero-Layer Aggregation

Exactly a year ago, when all modules of Compositor RTOS were formed, I was confronted with the task: to make such aggregation, which would not have committed the emission in the RAM memory of the computer (server). A year later, the problem is solved.

RAD96 vRouter L1-L3 96 node aggregation

It was required to complete assembly of Compositor RTOS 9.0.1 a14 with an extended work of the feeders, that is, the feeders now work from 11 kHz to 192 kHz of audio driver sampling frequency. This allows the upper generic z=128 to operate at frequencies comparable to the aggregator frequencies, namely from 150 GHz to 300 GHz.

Also, the management information base was expanded to 6041 VLAN’s and 13 dumps were produced. As a result, the final version of Compositor RTOS 9.0.1 a14 includes a channel pass-through (bypassing the second derivative of a function) that allows you to make exhaust (digital exhaust) to reduce the emissions of traffic inside the system. According to this two dumps were made of VLAN 6041 with digital exhaust and one firmware at 192 kHz was recorded on feedback after dialing, which involves 8 hidden servers. Since the firmware was recorded with an aggregator and is the snapshot of the system, it includes 96 ports of aggregation of the three layers: 32 ports of physical layer, 32 ports of data link layer and 32 ports of the network layer, which corresponds to L1-L3 aggregation.

Since such aggregation in reality throws out the large amounts of data in to the operating system memory, the snapshot utilizes resources in the other way – it corresponds to the MAC-address table of EUI48 without the OUI and do not throws resources in the computer memory. The network service in this case is the firmware, which includes the autonomous system with zero emissions. One system does not produce any action, but in a pair with snapshot this system aggregates resources and at the same time, disposes them, which happens so quickly in real-time that discards in the RAM memory cannot simply emerge.

Thus, the aggregation problem with zero emission is solved. Of course, for someone may seem, that 96 aggregation nodes is insufficient and the 32 L3 nodes is the standard for the aggregation of routing equipment of well-known manufacturers. But if you take into account the fact that the real link aggregation on these devices produces output, and requires a service restart, I can say that this resources composition technology can be very useful now.

1 2 3 11
Compositor v9 in the studio
RTOS version 9.0.2 a16 assembled
NIAGARA NIM Chat
NIAGARA NIM Chat