nyuuzyou/kompy huggingface dataset:
Андижон - download

| Андижон машинасозлик институти T – 250” avtomobilini oldi o‘ng boshqaruv richag qismini yig‘ish va payvandlash texnologik jarayonini loyixalash 1,53 Mb. 24 | o'qib |
| Ўзбекистон Республикаси Олий ва Ўрта Махсус Таълим Вазирлиги Андижон машинасозлик институти Loyihalash o‘zining uslubiyatiga ko‘ra, tarkibiga omillar va meyorlar faoliyati 413,16 Kb. 4 | o'qib |
| Ўзбекистон республикаси олий ва ўрта махсус таълим вазирлиги андижон машинасозлик институти Qo’chqarova Durdona Ilhomjon qizi, Soliyev Maxammadjon Ismatullayevich, Ergashev 0,85 Mb. 14 | o'qib |
| Hayvonlar ekologiyasi андижон 2021 O‘zbekiston Respublikasi Oliy va o‘rta maxsus ta’lim vazirligining 2021 yil 25 dekabrdagi 2,36 Mb. 58 | o'qib |
| Пахта селекцияси, уруғчилиги ва етиштириш агротехнологиялари илмий-тадқИҚот институти, тупроқшунослик ва агрокимё илмий-тадқИҚот институти ва андижон қишлоқ ХЎжалик институти ҳузуридаги 14 Scientific and methodological foundations of electrotechnology for the disinfection 1,72 Mb. 44 | o'qib |
| Ўзбекистон республикаси олий ва ўрта махсус таълим вазирлиги андижон машинасозлик институти ўзбек тили ва адабиёти кафедраси ўкитувчиси Hemis дастурига I- ii семестр учун фанлар мавзулари, дарс ресурслари, оралик ва якуний назоратлар учун топшириклар ишлаб чикилди ва ўз вақтида жойлаштирилди 20,38 Kb. 1 | o'qib |
| Ўзбекистон Республикаси Олий ва ўрта махсус таълим вазирлигит Андижон давлат университети ф-2-28. – лойиха мавзуси “Легирланган кремний сирти ва ҳажмидаги квант Ular yuqori temperaturali jarayonlar kechadigan qurilmalar qatoriga kiradi. Masalan, metallarni marten pechlarida eritish uchun 1800-2000 c temperatura zarur 1,94 Mb. 1 | o'qib |
| Ўзбекистон Республикаси Олий ва ўрта махсус таълим вазирлигит Андижон давлат университети ф-2-28. – лойиха мавзуси “Легирланган кремний сирти ва ҳажмидаги квант Sanoat pechi bu yoqilg'ining yonishi yoki elektr energiyasini sanoat ishlab chiqarishida materiallar yoki ish qismlarini issiqlikka aylantirish uchun issiqlikdan foydalanadigan issiqlik uskunasi 3,96 Mb. 4 | o'qib |
Receiving a Call - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 17/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
5.1.2 Receiving a Call
An incoming call will only be received if the application is not currently participating in a call. When a system attempts to establish an incoming call, the incoming-call window is displayed as you can see from Diagram 8 to the right, the window will display the IP address of the calling system and buttons to accept the call and reject the call. If the call is accepted the in-call window will be displayed and the call is initiated. However, if the reject button is pressed the call will be cancelled and the dialling window will be redisplayed.
Diagram 8, illustrates the incoming-call window.
|
| |
Placing a Call - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 16/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
5.1.1 Placing a Call.
For the user to make a call they will be required to enter the other systems IP address using the keypad provided on the dialler window which will be displayed when the application is executed (see diagram 6). Once an IP address has been entered and the dial button has been pressed, the IP address will be validated and if invalid an Error Message will be displayed.
Diagram 6 illustrates the dialler window.
Once the dial button has been pressed with a valid IP address the in-call window is displayed see diagram 7. This window will display the IP address of the other machine along with the current status of the call. For a successfully established call, the user will be able to being talking with the other user until the hang up button is pressed and the call is terminated and the original dialling screen is redisplayed. However, for an unsuccessful call a message illustrating the reason the call failed is displayed.
Diagram 7 illustrates the in-call window.
|
| |
Audio Subsystem - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 24/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.1 Audio Subsystem
The Audio Subsystem utilizes the Microsoft Waveform API to communicate with both the Audio input and output drivers. The Audio subsystem has a number off public functions;
audio_open() initialises both the audio input and audio output drivers, at the same time a circular queue structure of 64 empty audio blocks is initialised for each of the audio drivers.
audio_close() closes both the audio input and output drivers, at the same time the circular queue structure for each driver is torn down and the allocated memory is freed.
audio_play_block(unsigned char *block) passes the audio block parameter to the output driver for playback. After the first call of this function if the device becomes starved off blocks, which is where all available blocks are played, then to prevent clicks where the audio output driver stops playing, the call back function which is called after each successfully played block, checks the status of the queue and if empty, passes an empty block to the audio driver to play white noise.
audio_record() starts the input device recording blocks, as a block is filled a call back function is executed which passes the block to the codec subsystem for processing, the block within the queue once copied is cleared to be refilled later.
audio_stop() stops both the input and output drivers from playing/recording successive blocks, then clears and re-initialises the circular queue ready for the next call.
There where a number of problems faced with the implementation of the audio subsystem, first it was only discovered that the Arcom x86 Windows CE boards was not capable of recording sound after the initial 5 weeks of the project. This meant that the application had to be developed directly upon the Compaq IPAQ Pocket PC; this set the implementation back 3 weeks whilst attempting to find updates for the Arcom Board before moving on to the Pocket PC. Developing for the Pocket PC hindered the implementation since their where no easy methods available to output data to the screen without programming a user interface which made debugging difficult.
The lack off documentation and developer support for windows CE made developing the Audio subsystem difficult and examples of this was the late discovery that most of the win32 API can not be utilized from within a call back method, once this was pointed out a lot of issues where solved.
|
| |
Packing Subsystem - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 26/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.3 Packing Subsystem
The pack subsystem was implemented successfully it uses the packet structure developed at UCL for the RAT application. The subsystem has the following functions;
pack_setup() setups up the two internal circular queues used to store the outgoing blocks and the incoming packets. The pack_process_in thread is also started which will process incoming packets.
pack_stop() stops the pack_process_in thread and tears down the two internal circular queues.
pack_audio_in(unsigned char *packet) places incoming packets onto the internal queue and once four packets have arrived, signals the pack_process_in thread that their are packets to process.
pack_audio_out(unsigned char *block) places outgoing blocks into the queue in the appropriate order, such that, once sixteen blocks have arrived four packets are then formed and passed to the communications subsystem to send the packets to the other system.
pack_process_in() once executed waits for a signal that packets are ready to be processed. Once a notification signal has been received the four packets are taken and the blocks within each packet are rearranged to the correct order and are then passed to the codec subsystem for processing.
Although the time allocated to implement the packet subsystem was reduced the packet subsystem was still implementing in full, on time.
|
| |
Learn the history and facts about websites. Prepositions of time and place. Write about plus and mines of online shopping Write and retell 30 words about online shopping

|
Learn the history and facts about websites. Prepositions of time and place. Write about plus and mines of online shopping Write and retell 30 words about online shopping
|
Sana | 17.12.2023 | Hajmi | 1,75 Mb. | | #121612 |
Bog'liq About modal verbs and how can we use them in oral and written form. Describe multimedia devices O’ZBEKISTON RESPUBLIKASI AXBOROT TEXNOLOGIYALARI VA KOMMUNIKATSIYALARINI RIVOJLANTIRISH VAZIRLIGI QARSHI FILIALI “XORIJIY TILI” FANIDAN SELF STUDY QABUL QILDI: ELMURODOVA N. About modal verbs and how can we use them in oral and written form. Describe multimedia devices
|
|
Bosh sahifa
Aloqalar
Bosh sahifa
Learn the history and facts about websites. Prepositions of time and place. Write about plus and mines of online shopping Write and retell 30 words about online shopping
|
Aloqa, axborotlashtirish va telekommunikatsiya texnologiyalari sohasida nazorat bo‘yicha davlat inspeksiyasi tomonidan 2014 yil davomida amalga oshirilgan ishlar to‘g‘risida ma’lumot

Aloqa, axborotlashtirish va telekommunikatsiya texnologiyalari sohasida nazorat bo‘yicha davlat inspeksiyasi tomonidan 2014 yil davomida amalga oshirilgan ishlar to‘g‘risida ma’lumot
2014 yilda o‘tkazilgan tekshirishlar bo‘yicha:
Nazorat qiluvchi organlar faoliyatini muvofiqlashtiruvchi Respublika kengashining 2013 yil 30 noyabrdagi 02-G- son qarori bilan tasdiqlangan
“2014 yilda o‘tkaziladigan tekshirishlar reja-jadvali”ga muvofiq, 2014 yil davomida Aloqa, axborotlashtirish va telekommunikatsiya texnologiyalari sohasida nazorat bo‘yicha davlat inspeksiyasi (kelgusi matnlarda – Inspeksiya) va uning hududiy bo‘linmalari tomonidan 21 ta (2013 yil davomida 25 ta) xo‘jalik yurituvchi sub’ekt faoliyati rejali tekshirilgan.
Mazkur rejali tekshirishlarning:
- 10 tasi - telekommunikatsiyalar yo‘nalishi bo‘yicha;
- 3 tasi - ma’lumotlar uzatish yo‘nalishi bo‘yicha;
- 1 tasi - teleradiodasturlarni tarqatish yo‘nalishi bo‘yicha;
- 7 tasi - loyihalash va qurish xizmatlarini ko‘rsatuvchi korxonalarda o‘tkazilgan.
O‘tkazilgan 21 ta tekshirishlar natijasida aniqlangan kamchiliklar yuzasidan ko‘rsatmalar berilgan.
O‘zbekiston Respublikasi Vazirlar Mahkamasining 2014 yil 14 apreldagi 92- son qarori ijrosi bo‘yicha Inspeksiya tomonidan nodavlat televidenie va radioeshittirish ob’ektlarida rejadan tashqari tekshirishlar o‘tkazish yuzasidan 2014 yil 13 maydagi 32-14/637- son buyurtma Kengashga kiritilgan hamda Kengashning 2014 yil 26 maydagi 032- son xatiga muvofiq joriy yilning iyun va iyul oylarida 80 ta tadbirkorlik sub’ektlarida rejadan tashqari tekshirishlar o‘tkazilgan.
Rejadan tashqari tekshirishlar natijalari yuzasidan qo‘riqlash va muhofaza qilish masalalari bo‘yicha aloqa sohasiga oid xulosalar O‘zbekiston Respublikasi Ichki ishlar vazirligiga taqdim etilgan.
2014 yil davomida bevosita joylarga chiqib 1718 ta (2013 yilda 1423 ta) sub’ektlar bilan tushuntirish ishlari olib borilgan, o‘tkazilgan seminarlar soni 299 tani (2013 yilda 421 ta) tashkil etib, ushbu seminarlarda 3368 nafar (2013 yilda 4657 nafar) tadbirkor va korxonalar xodimlari ishtirok etishdi.
|
Communications Problems encountered

|
Communications Problems encountered
|
bet | 30/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.4.4 Communications Problems encountered
There was one major problem with the communications subsystem which was with the Arcom board no longer being suitable for the application since there was no means to record audio, then the replacement Hewlett Packard Jornada had to be used which could not run the IPv6 stack therefore the application at to revert to IPv4. Although this was a major disappointment, with the modular characteristics of the application at a later date if the project is continued then the communications sub system could be removed and re-implemented into IPv6.
|
| |
Hybrid of Asymmetric and Symmetric Encryption

|
Hybrid of Asymmetric and Symmetric Encryption
|
bet | 12/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
4.3.3 Hybrid of Asymmetric and Symmetric Encryption
However Asymmetric and Symmetric encryption can be combined to produce a fast and efficient system. Symmetric encryption can be used to encrypt all data transmitted to the other system, keeping the process fast and secure. However Asymmetric encryption can be used to exchange secret secure symmetric keys, such that, a system could generate a secure key and then send it to the other system encrypting the key using the public key of the receiving system solving all key exchange problems.
Using this hybrid method allows for all the advantages of both the Symmetric and Asymmetric encryption and solves most of the disadvantages of each method.
The Hybrid method is the method of choice where the calling system will first request the public key of the receiving system and then will generate a private key used for symmetric encryption of the main data, and encrypt this key and send it to the receiving system which will decrypt the key and use it for all further communications. IDEA (International Data Encryption Standard) will be the symmetric encryption implementation of choice and RSA will be used as the asymmetric encryption implementation used.
|
| |
Communication Call Functions

|
Communication Call Functions
|
bet | 29/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.4.3 Communication Call Functions
The first sets of functions below are simple functions which create or close data and control sockets for the application and are self explanatory.
openControlConnection()
createRecivingSocket()
createSendingSocket()
createServerSocket()
closeConnection()
The next set of functions deal with a particular aspect of signalling and control of the call channels;
comms_listen() thread opens up a listing channel and listens for a incoming connection. When a connection is made the user interface is notified and if the user choices to accept the connection the comms_incall functions is called, on the other hand if the user choices to reject the call the subsystem resumes listening.
comms_incall() opens the two data channels and setups and starts each subsystem processing the recorded and playback audio, once the hang up signal is received the function terminates the call and resumes the listening thread.
comms_makecall() opens a connection with the machine and if an accept signal is received calls the comms_incall function to setup and carry out the call.
comms_uithread() thread waits for a signal, which once received processes messages from the user interface and sends them to the current running thread such as the listening thread.
comms_senduicommand() received the user interface messages and signals comms_uithread() that a messages has arrived.
|
| |
Communications Subsystem - 1. 1 The Motivation

|
1. 1 The Motivation
|
bet | 27/32 | Sana | 22.07.2021 | Hajmi | 0,89 Mb. | | #15652 |
6.4 Communications Subsystem
The communications subsystem is the most complex subsystem within the VoIPv6 application. Its mission is to establish and maintain calls in terms of both signalling and control and in terms of transmitting and receiving audio data blocks.
There are three distinct parts of the communications subsystem; the setup section, the section to deal with audio transmission and also the section to deal with call initialisation and control.
6.4.1 Communications Setup Functions
The setup function comms_initiate deals with setting up the communications sub system in terms of preparing the semaphores and creating and executing the comms_uithread which deals with communications between the user interface subsystem and the communications subsystem.
|
| |
Note: ImmDeviceCollection - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

Note: ImmDeviceCollection and IMMDevice are part of the MMDeviceAPI, which is new for Windows Vista. These interfaces are declared in Mmdeviceapi.h. Also note that the collection that is referenced by the IMMDeviceCollection object contains items that support the IMMDevice interface. This collection contains only one audio endpoint item that supports IMMEndpoint.
To find this item, the APO can traverse the list of items and call QueryInterface on each item until it finds the one that supports IMMEndpoint. Once the APO has identified the endpoint item, the APO can use IMMEndpoint::GetDataFlow to determine whether that endpoint is an input or an output. The APO can also access the property store to get more information about the PKEY_AudioEndpoint_FormFactor.
The number and types of other items in the collection depend on the underlying implementation of the audio endpoint. For typical audio devices that are supported by PortCls, AVStream, and other Kernel Streaming drivers, the collection items represent the KS filters that are implemented by the driver. If the APO needs to interact directly with the audio hardware driver, the APO can do so via the IDeviceTopolgy interface of one or more of the IMMDevice items (not the endpoint item) referenced by the IMMDeviceCollection object. To activate and use the IDeviceTopolgy interface for an IMMDevice item, the APO must call IMMDevice::Activate, and provide the REFIID for the IDeviceTopology interface for the item. However for most APOs, direct interaction with the hardware driver should not be necessary.
|
Enhancements Property Page Replacement

Enhancements Property Page Replacement
Microsoft supplies an Enhancements property page for the Audio Control Panel item. The page is associated with the Microsoft Audio Home Theater Effects sAPO. Vendors can replace this property page with a custom page by implementing and registering a custom property page provider. To implement the provider, use the standard techniques that are documented in the Platform SDK. To replace the default property page, install the DLL that contains the custom property page implementation and modify the appropriate registry value.
The Enhancements property page is registered under the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render\Endpoint\FX key. Endpoint is the identifier of the endpoint to which the property sheet is to be associated. The property page is specified by assigning its CLSID to the registry value that is associated with the UserInterface property store value. For example:
HKLM
SOFTWARE
Microsoft
Windows
CurrentVersion
MMDevices
Audio
Render
Endpoint
FXProperties
...
"{d04e05a6-594b-4fb6-a80d-01af5eed7d1d},3"=
"{YOUR CLSID GOES HERE}"
To replace the default property page with a custom implementation, replace its CLSID with the CLSID of the custom property page. The custom property page provider is installed with the rest of the driver package, by using an INF. The following example is an excerpt from an INF that shows how to register an Enhancements property page DLL:
[SysFx.AddReg]
…
HKR,"FX\\0",%PKEY_SYSFX_UiClsid%,,%SYSFX_UI_CLSID%
…
[Strings]
PKEY_SYSFX_UiClsid = "{D04E05A6-594B-4FB6-A80D-01AF5EED7D1D},3"
SYSFX_UI_CLSID = "{YOUR GUID GOES HERE}"
…
|
INF Files for sAPOs - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

Figure 4. Registry settings for Microsoft Audio Home Theater Effects
INF Files for sAPOs
This section shows examples from an INF that is used to install an sAPO. For readability, it is useful to define friendly names for the property store value names. For example:
; PropertyKeys
PKEY_FX_Association = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},0"
PKEY_FX_PreMixClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},1"
PKEY_FX_PostMixClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},2"
PKEY_FX_UiClsid = "{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},3"
PKEY_FriendlyName = "{ D04E05A6-594B-4fb6-A80D-01AF5EED7D1D },4"
The following example shows the INF text to add the keys and property values to the registry:
HKR,"FX\\0",%PKEY_FriendlyName%,,%FX_FriendlyName%
HKR,"FX\\0",%PKEY_FX_PreMixClsid%,,%FX_PREMIX_CLSID%
HKR,"FX\\0",%PKEY_FX_PostMixClsid%,,%FX_POSTMIX_CLSID%
HKR,"FX\\0",%PKEY_FX_UiClsid%,,%FX_UI_CLSID%
HKR,"FX\\0",%PKEY_FX_Association%,,%KSNODETYPE_ANY%
The final element of each line is a friendly name for the associated property store data. The exact values are defined elsewhere in the INF file, but not shown here.
It is possible to register multiple sAPOs by creating additional subkeys under FX and adding the sAPO's property store data to these keys. However, the names of the subkeys that contain the property store data must be sequential integers, starting with zero. The above example registers a single sAPO, so the property store data goes under FX\0. The code to register a second sAPO would look similar, but the data would go under FX\1, the third under FX\2, and so on.
|
Property name - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 11/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
Property name
|
ID
|
Type
|
Data
|
SysFxAssociation
|
0
|
Multistring
|
KSNODE_TYPE GUIDs that associate the sAPO with the connection types that the sAPO supports. Use a NULL GUID to associate the sAPO with any connection type. If the connection type does not match the GUID, the system effects are not added.
|
PreMixEffect
|
1
|
String
|
The CLSID that is associated with the data and code that are used to create the LFX sAPO.
|
PostMixEffect
|
2
|
String
|
The CLSID that is associated with the data and code that are used to create the GFX sAPO.
|
UserInterface
|
3
|
String
|
The CLSID that is associated with the data and code that are used to create the configuration UI for the system effects package.
|
FriendlyName
|
4
|
String
|
A friendly name for the system effects package.
|
Additional entries as appropriate
|
>4
|
User-defined
|
Initialization data for the sAPO.
|
The value name for each property has the form “{GUID},ID”, where GUID is the standard property key GUID string, {D04E05A6-594B-4fb6-A80D-01AF5EED7D1D}. It is defined in AudioEngineBaseAPO.idl and is the same for all properties. For example, the value for the SysFxAssociation property is named “{D04E05A6-594B-4fb6-A80D-01AF5EED7D1D},0”.
Figure 4 is a screenshot of RegEdit that shows a typical example of how system effect keys and values appear in the registry. The device has one sAPO that is named Microsoft Audio Home Theater Effects. It works with any connection type, and has LFX, GFX, and configuration UI sAPOs.
|
| |
sAPO Initialization - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 16/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
After the sAPOs are inserted in the graph, the graph builder initializes them. An sAPO must export IAudioSystemEffects, an interface that identifies the sAPO as an audio effect. If the query for IAudioSystemEffects is successful, the graph builder fills out the initialization structure, APOInitSystemEffects, and passes it to the sAPO’s Initialize method. The structure includes the following data:
An IPropertyStore interface pointer for the device endpoint’s property store.
An IPropertyStore interface pointer for the audio effect’s property store.
A string that contains the device’s PnP hardware ID.
An IMMDeviceCollection object that contains IMMDevice interface pointers to several objects.
|
| |
sAPO Bypass - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 15/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
sAPO Bypass
After the endpoints and endpoint property stores have been created, the audio service builds the audio device graph that handles the signal processing. The endpoint property store has a global effects bypass setting, PKEY_Endpoint_Disable_SysFx, which enables or disables system effects. A check box on the Audio Control Panel item allows the user to set this property. By default, system effects are disabled. If system effects are enabled and LFX or GFX sAPOs are associated with the device, the audio service adds them to the graph along with the standard audio sAPOs.
The audio service registers for property store notifications so it can monitor changes in the GFX and LFX settings as well as changes in the effects bypass setting. If the audio service receives a notification, it signals a configuration change to all associated audio servers. From that point, the operation proceeds as it does for device format changes.
|
| |
Registry Settings - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

Registry Settings
The association between LFX or GFX sAPOs and the related device is stored under the registry key for the device interface. The DLL that contains the sAPOs must self-register by including a ‘RegisterDlls’ statement in the INF file.
The HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/DeviceClasses key has a subkey for each device interface that is named with the interface’s CLSID string. Under each CLSID key is a subkey for each device that exports the interface. For example, ##?#PCI#VEN_1106&DEV_3059&SUBSYS_810A1043&REV_60#3&61AAA01&1&8D#{6994ad04-93ef-11d0-a3cc-00a0c9223196} is the subkey of {6994AD04-93EF-11D0-A3CC-00A0C9223196} that represents the device for the VIA onboard AC '97 audio controller with a RealTek AC '97 codec.
Each device key has subkeys for all the interfaces that it exposes. For example, the device subkey under discussion has subkeys for wave, topology, and Universal Asynchronous Receiver Transmitter (UART) interfaces that are named #Wave, #Topology, and #UART, respectively. The following example shows these settings schematically. Note that the device subkey string has been truncated for readability.
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Control
DeviceClasses
…
{6994AD04-93EF-11D0-A3CC-00A0C9223196}
##?#PCI#VEN_1106&DEV_3059&SUBSYS_810A1043&REV_60…
#Topology
#UART
#Wave
…
To register a GFX or LFX sAPO, add a DeviceParameters subkey to the appropriate topology subkey, followed by an FX subkey. The FX key can have one or more system effect subkeys, one for each effect's sAPO. The system effect subkey names must be integers, starting with zero.
The data for the property store is contained in a series of values that are associated with the system effect key. The value names are globally unique identifier (GUID) strings, followed by an ID, much like property store key names. The property names and the associated data are listed in the following table.
|
How to Implement a Custom sAPO - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 24/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
How to Implement a Custom sAPO
Custom sAPOs are implemented as in-process COM objects and packaged as DLLs. This section outlines the basics of how to implement an sAPO. For details, see the sAPO software development kit (SDK), which is part of the Platform SDK. The following list gives some basic design considerations.
An sAPO can have one input and one output connection. This connection is an audio buffer and can be multichannel.
An sAPO must be real-time compatible. This means:
All buffers that are processed by the sAPO must be nonpageable.
All code and data in the process path must be nonpageable.
All methods that are members of real-time interfaces must be implemented as nonblocking. They should not block, use paged memory, or call any blocking system routines. Note that most system routines are blocking. Real-time interfaces are identified by an “RT” at the end of their name, such as IAudioProcessingObjectRT.
Real-time compatible sAPOs can be used in contexts that do not require real-time processing.
An sAPO can modify only the audio data that is passed to it through its IAudioProcessingObjectRT::APOProcess routine. It cannot change the settings of the underlying logical device, including its KS topology.
GFX sAPOs must process data by using a format with a fixed frame size. The frame size is specified by the advertised supported format. The format is static for both input and output.
GFX sAPOs should avoid introducing more than 10 ms of latency into the audio processing chain. An sAPO reports this latency through the IAudioProcessingObject::GetLatency API.
|
| |
How to Implement a UI for Configuring the Effects

|
How to Implement a UI for Configuring the Effects
|
bet | 27/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
How to Implement a UI for Configuring the Effects
The CLSID of the system effect's UI sAPO is available from the audio endpoint’s property store. The Audio Control Panel item gets this CLSID from the audio endpoint that is currently in context. When the Audio Control Panel item launches the appropriate custom system effect UI, it passes it the audio endpoint. The UI can then access the endpoint property store to read and adjust property settings. The UI should also register for property store notifications in case some other program modifies the settings.
|
| |
Data Formats - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 20/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
Data Formats
All the system sAPOs are designed to process float32 pulse code modulation (PCM) data. To prevent unnecessary format conversions, LFX and GFX sAPOs should process data in float32 PCM format. A typical GFX for an int16 PCM endpoint uses the float32 PCM format for both input and output. The graph builder attaches a system-provided float32-int16 converter to the endpoint-facing side of the sAPO to convert the audio stream to or from int16 PCM format. GFX sAPOs can omit the system-supplied format converter and process data in the native device format. However, the audio engine-facing side of the GFX must still support the float32 PCM format.
GFX sAPOs can support an encoded output format such as AC3 that can handle multiple speaker configurations. In that case, the sAPO should get the speaker configuration information from the endpoint property store. It can then return S_FALSE to suggest an input (mix) format when IsInputFormatSupported is called with the encoded format as opposite. The GFX sAPO should return a float format that has the sample rate and speaker configuration of the “decoded” format.
Note: An sAPO can suggest an audio format only during calls to IsInputFormatSupported or IsOutputFormatSupported.
|
| |
The sAPO LockForProcess Method - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 21/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
The sAPO LockForProcess Method
After the sample format has been finalized, the graph builder calls the sAPO’s IAudioProcessingObjectConfiguration::LockForProcess method to finalize the input and output formats and give the sAPO a final opportunity to finish initialization. If this is successful, the object is locked in its current state. No format configuration changes are allowed after the object is locked. The IAudioProcessingObjectConfiguration::UnlockForProcess method is called to unlock the sAPO.
|
| |
Po’lat va dub silindrik nagellar, mixlar, shuruplarning joylashtirilish sxemasi

|
Po’lat va dub silindrik nagellar, mixlar, shuruplarning joylashtirilish sxemasi
|
bet | 2/3 | Sana | 14.01.2024 | Hajmi | 154,86 Kb. | | #137073 |
Bog'liq Mavzu mix va burama mixlar yordamida oddiy birikma tayyorlash t-fayllar.orgPo’lat va dub silindrik nagellar, mixlar, shuruplarning joylashtirilish sxemasi:
a -to’g’ri qatorga, b -shaxmat tartibida, v -mixlarning joylashtirilishi
Mix bilan biriktirish yog’och konstruktsiyalardan balkalar, shchitlar (panellar), to’siqlar, fermalar va h. k. da keng qo’llaniladi.
yog’och konstruktsiyalar uchun taxtalarni mix bilan biriktirishda diametri 6mm va undan yo’g’on mixlar ishlatiladi, zirk daraxtidan bo’lgan taxtalarni mix bilan biriktirishda diametri 5mm dan yo’g’on mixlarni oldindan parmalangan teshikka qoqish lozim, bunda teshik diametri qoqiladigan mix diametrining 0,9, teshik chuqurligi esa mix uzunligining 0,6 qismiga teng bo’lishi kerak.
YOg’och elementlarni (taxtalarni) biriktirish uchun mix o’qlari orasidagi masofa (tola bo’yicha) quyidagicha bo’lishi lozim mixlanadigan element qalinligi bo’lganda S1=15d va mixlanadigan element qalinligi s=4d bo’lganda (d-mix diametri) S1<25d. Mix teshib o’tmaydigan elementlarga qoqilganida, uning qalinligidan qat’i nazar S1 masofa mixning o’n besh diametriga teng yoki S1 15dqabul qilinadi.
Tolalar bo’yicha mixdan taxta toretsigacha bo’lgan masofa S1 kamida 15d bo’lishi ko’rak. Mixni tolalarga ko’ndalang qoqishda mixlar o’qlari orasidagi masofa S2 = 4d bo’lishi, mixlarni shax-mat tartibida yoki qiya, burchak ostida qoqishda esa bo’ylama qatorlar orasidagi masofa 3d gacha kamaytirilishi kerak.
Elementning bo’ylama qirrasidan eng chetki mixgacha bo’lgan masofa kamida 4d bo’lishi kerak. Mix diametri mixlanadigan eng yupqa taxta qalinligining 0,25 qismidan yo’g’on bo’lmasligi kerak.
YUk ko’taruvchi konstruktsiyalarda mixlar andaza bo’yicha qoqilib, andazada mix qoqiladigan joylar chizmaga qat’iy rioya qilingan holda belgilanadi. Andaza faner yoki tunukadan yasaladi.
Mix tortilishga ishlaydigan konstruktsiyalarda mixning qayirib qo’yiladigan uchi teshilgan yog’och elementining ikki qalinligidan, mixning 10 diametridan kam bo’lmasligi kerak.
Mixli birikmalarda ikki tomondan mix qoqilganda mixlar hamma taxtalarni (paketni) teshib chiqmasligi kerak. Mixlaganda chiqib qolgan mix uchi tolalarga ko’ndalang ravishda qayi-rib qo’yilishi lozim.
Mix markazlari orasidagi masofada yo’l qo’yiladigan chetga chiqish (mix qoqiladigan tomondan) ±2 mm.
Agar qoqilayotgan mix qayilsa, uni albatta sug’urib olish va o’rniga yangi mix qoqish zarur. Muzlagan ho’l taxtalarga mix qoqish tavsiya etilmaydi, chunki mix zanglashi natijasida birik-maning mustahkamligi kamayadi.
Mixni yog’ochning mustahkam qismiga qoqish lozim. Mixni yog’och ko’ziga va yorilgan joyiga qoqish yaramaydi.
|
| |
SHuruplar - Mavzu: mix va burama mixlar yordamida oddiy birikma tayyorlash texnologiyasi

|
Mavzu: mix va burama mixlar yordamida oddiy birikma tayyorlash texnologiyasi
|
bet | 3/3 | Sana | 14.01.2024 | Hajmi | 154,86 Kb. | | #137073 |
Bog'liq Mavzu mix va burama mixlar yordamida oddiy birikma tayyorlash t-fayllar.orgSHuruplar duradgorlik buyumlari va yig’ma mebellarda keng qo’llaniladi. SHurup pastki qismida vint o’yig’i bo’lgan tsilindrik shakldagi metall sterjendan iboratdir. SHuruplarning kallaklari yarim yumaloq, yashirin va yarim yashirin bo’lishi mumkin. Duradgorlik buyumlarida shuruplar shtapiklar, tirqish berkitgichlar, asboblap (ilgaklar, tortqilar, qulflar va h. k.)ni mahkamlashda qo’llaniladi. Bunda ko’proq yashirin kallakli shuruplar ishlatiladi.
SHurup yog’ochga qoqilmaydi, balki otvyortka yoki elektrik shurup buragich bilan burab kiritiladi. SHurupni oxirigacha burab kiritish kerak. SHurup bolg’a bilan qoqilganda vintli birikma mustahkam chiqmaydi, shurup o’tgan joydagi yog’och tolalari sidiriladi va shurupni birikmada tutib turuvchi kuch 40% ga kamayadi.
SHurupli birikmaniig mustahkamligi yog’och zichligiga, shurup o’lchamiga, shurupning qancha chuqur burab kirgizilishiga va yog’och tolalari yo’nalishiga bog’liq.
Qattiq yog’ochlarga shurup oldindan parmalangan teshiklarga burab kirgiziladi. Bunda teshik diametri 0,9 shurup rezbasi diametriga, teshik uzunligi esa 1/2 dan 3/4 shurup uzunligiga teng bo’lishi kerak.
SHurupni dub yog’ochiga burab kirgizishdan oldin, zanglashdan saqlash maqsadida tavot bilan moylash lozim. Nam yog’ochga shurupni burab kirgizish tavsiya etilmaydi, chunki shurup zanglaydi.
Qurilish elementlarini shuruplar bilan biriktirishda vint o’qlari orasidagi masofa S1=10d; S2=S3=5d bo’lishi kerak (d-shurup diametri).
http://fayllar.org
|
| |
Ikkinchi avlod aloqa mobil tarmoqlari

|
Ikkinchi avlod aloqa mobil tarmoqlari
|
bet | 2/5 | Sana | 09.12.2023 | Hajmi | 1,82 Mb. | | #114752 |
Bog'liq 4-mustaqil ASLIDDINIkkinchi avlod aloqa mobil tarmoqlari
GSM (Global System for Mobiles) standartiga asoslangan 2 avlod mobil
standarti 1991 yil birinchi marta Finlandiyada joriy etildi. Bu avlod aloqa
jarayonlari uchun 1 avloddan farqli ravishda raqamli signallardan foydalanildi.
900MHz chastota polosa kengligida ishlovchi ushbu standartning ma’lumot uzatish tezligi 64 Kbit/s gacha oshirish imkoniyati ishlab chiqildi. 2G tarmoqlari foydalanuvchilarga ovozli, matnli, rasmli va MMS (multimediamessage) xizmatlarini yuqori sifatda taqdim eta oldi. 2G tarmog’ida mobil telefonini ishlash uchun kuchli raqamli signal talab etiladi, aks holda tarmoqda uzilishlar yuzaka keladi va raqamli signal yoqoladi. 2G tarmoqlarida xech qanday video xizmatlari joriy etilmadi, ammo 3G tarmoqlariga moslab video xizmatlarni qo’shish va yana qo’shimcha xizmatlari taqdim etish masalalari ko’rib chiqilgan.
3-rasm. 2Gmobil tarmoqlari arxitekturasi
2 (G) avlod mobil tarmoqlari GSM/CDMA standartiga asoslangan bo’lib, tarmoq bir nechta elementlardan tashkil topgan arxitekturaga asoslanadi. GSM tarmog'ining arxitekturasi Stansiya quyi tizimi (BSS), tarmoq va kommutatsiya
(NSS), operatsiya va qo'llab-quvvatlash quyi tizimi (OMS), shuningdek MSC,
AuC, HLR, VLR va boshqalar iborat.
Uchunchi avlod mobil aloqa tarmoqlari
3 avlod mobil aloqa tarmoqlari 2000-2010 yillar oralig’ida dunyo miqyosida
keng foydalanildi va ularda foydalanilgan terminallar smartfonlar deb nomlandi.1 va 2 avlod taqdim etgan xizmatlarga qo’shimcha video qo’ng’iroqlar ham ushbu avlod tomonidan qo’llab quvvatlandi.Aloqa almashish tezligi juda tez,qo’shimcha xizmatlari ko’paygan va mobil TV xizmatlarini o’zida jamlagan 3Gtarmoqlari 1.6-2.0 GHz chastota diapozonida ishlaydi.Bunday mobil aloqa tarmoqlarining o’tkazish polosasi100Hz va keng polosali qaramli tarmoq ham deb nomlanadi.
CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System) va EDGE(Enhanced Data Rates for GSM Evolution)standart texnologiyalarga asoslangan 3G avlod mobil aloqa tarmog’ining ma’lumot uzatishtezligi soniyasida 144kb/s –2Mb/s tezlikni qo’llab
Quvvatlaydi.
4-rasm.3G mobil tarmoqlari arxitekturasi
|
| |
Next ni bosasiz Custom ni tanlaysiz

|
Next ni bosasiz Custom ni tanlaysiz
|
Sana | 25.01.2024 | Hajmi | 215,04 Kb. | | #145260 |
Bog'liq NetSupport ni o\'rnatish
Next ni bosasiz
Custom ni tanlaysiz
O’quvchi kompyuterida Student ni tanlaysiz
O’qituvchi kompyuterida Tutor Console ni tanlaysiz
Room Eval da turadi
Finish
O’rnatib bo’lgach NSM.LIC faylini C:\Program Files\NetSupport\NetSupport School\ papkaga Заменить qilib tashlaysiz.
Bu litsenziya fayli.
|
| |
Mikroinstruksi - Komputer sap (Simple-As Possible; artinya sederhana mungkin) telah dirancang untuk anda sebagai...

Mikroinstruksi
Pengendali-pengurut mengirimkan kata-kata kendali dengan laju satu kata dalam setiap keadaan T atau satu siklus detak. Kata-kata ini merupakan pengarahan kepada komputer tentang operasi yang harus dilakukan oleh bagian lain dari komputer. Karena masing-masing kata-kata kendali itu menimbulkan satu langkah kecil dalam pemrosesan data, maka setiap kata kendali disebut suatu mikroinstruksi. Bila kita lihat kembali diagram blok SAP-1 (gambar 10-1), kita dapat membayangkan adanya suatu arus lunak dari sederet mikro instruksi yang mengalir keluar dari pengendali-pengurut menuju kerangkaian-rangkaian SAP-1 yang lain.
Makroinstruksi
Instruksi-instruksi yang pernah kita pergunakan dalam pemrogaman (LDA. ADD. SUB,….) kadang-kadang disebut makroinstruksi untuk membedakannya dari mikroinstruksi. Setiap makroinstruksi SAP-1 tersusun dari mikroinstruksi. Setiap makroinstruksi SAP=1 tersusun dari tiga mikroinstruksi. Misalnya makroinstruksi LDA terdiri dari tiga macam mikroinstruksi seperti tercantum dalam tabel 10-3. Guna menyederhanakan bentuk mikroinstruksi itu kita dapat menggunakan bentuk heksadesimal sebagaimana terlihat pada tabel 10-4
Tabel 10-3
Makro
|
Keadaan
|
Cp Ep M
|
1 1 A EA
|
SU EU B O
|
Yang aktif
|
LDA
|
T4
|
0 0 0 1
|
1 0 1 0
|
0 0 1 1
|
M, 1
|
|
T5
|
0 0 1 0
|
1 1 0 0
|
0 0 1 1
|
, A
|
|
T6
|
0 0 1 1
|
1 1 1 0
|
0 0 1 1
|
Tidak ada
|
Tabel 10-4
Tabel 10-5 Mikroprogram SAP-1
Mikro program SAP-1 disajikan dalam tabel 10-5 yang merupakan daftar dari setiap makro instruksi dan mikroinstruksi-mikroinstruksi yang diperlukan bagi pelaksanaannya. Tabel ini merangkum rutin-rutin eksekusi untuk instruksi SAP-1. Tabel yang sama dapat pula dipakai bagi perangkat instruksi tingkat lebih lanjut.
TABEL 10-6. ROM KENDALI SAP-1
Alamat
|
Isi
|
Rutin
|
Bit aktif
|
0H
|
5E3H
|
Fetch
|
Ep, M
|
1H
|
BE3H
|
|
Cp
|
2H
|
263H
|
|
, 1
|
3H
|
1A3H
|
LDA
|
M, 1
|
4H
|
2C3H
|
|
, A
|
5H
|
3E3H
|
|
Tidak ada
|
6H
|
1A3H
|
ADD
|
M, 1
|
7H
|
2E1H
|
|
, B
|
8H
|
3C7H
|
|
A, u
|
9H
|
1A3H
|
SUB
|
M, 1
|
AH
|
2E1H
|
|
, B
|
BH
|
3CFH
|
|
A, u, u
|
CH
|
3F2H
|
OUT
|
u, o
|
DH
|
3E3H
|
|
Tidak ada
|
EH
|
3E3H
|
|
Tidak ada
|
FH
|
X
|
X
|
Tidak dipakai
|
CON = Cp Ep M 1 1 A EA Su Eu B o
Tabel 10-7. ROM ALAMAT
Alamat
|
Isi
|
Rutin
|
0000
|
0011
|
LDA
|
0001
|
0110
|
ADD
|
0010
|
1001
|
SUB
|
0011
|
XXXX
|
Tidak ada
|
0100
|
XXXX
|
Tidak ada
|
0101
|
XXXX
|
Tidak ada
|
0110
|
XXXX
|
Tidak ada
|
0111
|
XXXX
|
Tidak ada
|
1000
|
XXXX
|
Tidak ada
|
1001
|
XXXX
|
Tidak ada
|
1010
|
XXXX
|
Tidak ada
|
1011
|
XXXX
|
Tidak ada
|
1100
|
XXXX
|
Tidak ada
|
1101
|
XXXX
|
Tidak ada
|
1110
|
1100
|
OUT
|
1111
|
XXXX
|
Tidak ada
|
10-7 DIAGRAM SKEMATIK SAP-1
Dalam pasal ini kita akan mengkaji diagram skematik lengkap dari SAP-1. Gambar 10-12 sampai 10-15 memperlihatkan semua serpih, semua rangkaian, dan sinyal-sinyal yang terjadi didalamnya. Anda harus menggunakan gambar-gambar ini dalam mengikuti seluruh pembahasan selanjutnya. Lampiran 3 memberikan penjelasan tambahan untuk beberapa serpih yang lebih rumit.
|
sAPO Failure Monitoring and Automatic Disabling

|
sAPO Failure Monitoring and Automatic Disabling
|
bet | 22/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
sAPO Failure Monitoring and Automatic Disabling
The audio system monitors sAPO return codes to determine whether sAPOs are being successfully incorporated into the graph. It does so by tracking the HRESULT values that are returned by any of several designated methods. The system maintains a failure count value for each sAPO that is being incorporated into the graph, typically an LFX and a GFX sAPO. A single registry value, PKEY_Endpoint_Disable_SysFx, disables both sAPOs when it is set.
The system increments an sAPO's failure count each time one of the designated methods fails. Certain failure codes might be excluded from this count.
If an sAPO indicates that it has been successfully incorporated into the graph, its failure count is reset to zero.
If the failure count for either sAPO reaches a system-specified limit, both sAPOs are disabled by setting PKEY_Endpoint_Disable_SysFx. Currently, this limit is set to 10, but that might change in the future.
The system monitors four primary API calls:
CoCreateInstance: The attempt to create an sAPO can fail for a number of reasons, including:
The graph is running protected content, and the sAPO is not properly signed.
The sAPO is not registered.
The sAPO has been renamed or tampered with.
IsInputFormatSupported/IsOutputFormatSupported: The system increments the sAPO's failure count if either method returns a failure code.
LockForProcess. If this call is successful, the sAPO failure count is reset to zero. Otherwise, the failure count is incremented.
|
| |
Application Control over sAPOs - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

Application Control over sAPOs
If an application doesn’t want any processing on either the render or capture pipeline, it should open the endpoint in exclusive mode. However, this approach has some limitations that often make it undesirable:
No other application can use the endpoint.
The signal processing graph does not process the audio stream. This means that features such as volume control and automatic gain control (AGC) are disabled.
Note: Currently, capture effects are limited to post-split, application-specific processing. This means that they can be implemented only by LFX sAPOs.
Applications cannot query for the type of effects that an sAPO applies to the audio stream. That means that applications cannot make any meaningful decisions on what effects to offer to the user or what effects to enable in the streaming pipeline. As a practical matter, this is typically not a major problem. Most problems can often be avoided by using some intelligence. For example, try the native stream format before inserting an HP visualization.
|
Signal Processing Requirements - Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista

|
Custom Audio Effects in Windows Vista Custom Audio Effects in Windows Vista
|
bet | 26/28 | Sana | 22.07.2021 | Hajmi | 0,57 Mb. | | #15720 |
Signal Processing Requirements
An sAPOs should observe the following limitations on its processing algorithms.
Do not use nonlinear processing. It can interfere with other processing algorithms that the system’s application audio graph provides, such as AEC.
Processing should be nonblocking. In general, the time that is required for processing to run from beginning to end should stay within a well-defined upper bound.
Support IEEE 32-bit float input and output. The audio engine’s native sAPOs all operate on a float32 data path.
An sAPO can have one input and one output audio connection.
|
| |
PON texnologiyasi - Transport tarmoqlarida qo‘llaniladigan protokollar va texnologiyalar: pdh, sdh, sonet, dwdm

|
Transport tarmoqlarida qo‘llaniladigan protokollar va texnologiyalar: pdh, sdh, sonet, dwdm
|
bet | 5/5 | Sana | 09.12.2023 | Hajmi | 1,82 Mb. | | #114752 |
Bog'liq 4-mustaqil ASLIDDINPON texnologiyasi
PONlar nuqtadan ko'p nuqtaga topologiyadan foydalanadi va optik ajratgichlar ma'lumotlarni bitta uzatish nuqtasidan bir nechta foydalanuvchi so'nggi nuqtalariga tarqatish uchun.Ushbu noyob arxitektura PON-larga bir nechta asosiy afzalliklarni taqdim etish imkonini beradi, shu jumladan
8-rasm.PON texnologiyasi
Foydalanilgan adabiyotlar
Transport tarmoqlari va telekommunikatsiya tizimlari. Ed Steklova V.K.
www.Ziyonet.uz
Internet ma’lumotlari
https://.uzwkipedia.org
https://arxiv.uz
https://cyberleninka.ru
https://hozir.org
|
| |
Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish kafedrasi

Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish kafedrasi
|
Bosh sahifa
Aloqalar Bosh sahifa Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish kafedrasi
|
Adabiyotlar - Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish...

|
Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish kafedrasiBog'liq MT 2-MI ElmurodovvAdabiyotlar
1.AdamDrozdek. Data structure and algorithms in C++. Fourth edition.
2013. Chapter 6.9. 268-276 betlar.
2.Ma’ruza matnlari. Carnegie Mellon University – CORTINA. 2010. 15-
121 Introduction to Data Structures,
http://www.cs.cmu.edu/~tcortina/15-121sp10/lectures.html
http://www.cs.cmu.edu/~tcortina/15-121sp10/Unit06B.pdf
3.Algorithms and data structures in C/C++ by Alex Allian.
http://www.cprogramming.com/tutorial/computersciencetheory/heap.html
Document Outline
|
|
Bosh sahifa
Aloqalar
Bosh sahifa
Muhammad al-xorazmiy nomidagi toshkent axborot texnologiyalari universiteti tizimli va amaliy dasturlashtirish kafedrasi
|