Impact of Injection Protocol Selection by Retina Specialists on Clinical Outcomes in Patients with Diabetic Macular Edema

Intravitreal anti-VEGF injections are the current gold standard for treating diabetic macular edema (DME). However, injection practice patterns of retina specialists have varied markedly based on physician discretion. This retrospective study analyzes the impact of injection protocol selection on change in best-corrected visual acuity (BCVA) and central macular thickness (CMT) in 170 eyes treated by 4 retina specialists practicing a pro re nata (PRN) strategy between 2010 and 2020. DME patients received an average of 7.25 injections every 6.24 weeks over 56.6 weeks. There were significant differences between retina specialists in mean number of injections (p = 0.0001) and mean length of treatment (p = 0.0007) but not in mean interval between injections. Over the treatment period, average change in BCVA was −0.053 logMAR, and average change in CMT was −51.1 µm, neither of which had significant differences between retina specialists. BCVA and CMT at initial visit were found to be significantly associated with improved BCVA and CMT over the treatment period (p < 0.001). Number of injections administered and interval between injections were not found to be significant factors affecting change in BCVA or CMT. Despite significant differences in injection dosing regimen, retina specialists achieved similar outcomes in change in BCVA and CMT over the treatment period.

Demonstration of Modbus Protocol for Robot Communication Using C#

Purpose: The Modbus is the trusted name in the industrial automation communication domain. It is a pretty simple protocol to implement and so very popular to the industrial communication personnel. Nowadays, Some industrial robots are also capable of communicating through Modbus. So our robot researchers frequently face the challenge of communicating with Modbus-enabled devices or robots. They need to know the protocol in detail before integrating it into their project. Its learning curves are a bit higher because of the lack of document which is practical oriented. The protocol selection, packet structure, CRC, or LRC calculation need to maintain precisely as standards; otherwise, the Modbus exception may happen. We experience those scenarios. Through our practical experience, we learned what is required for a new researcher who wants to implement Modbus in their project. In this paper, we demonstrate the Modbus packet structure and implement it with several practical examples. Finally, to test the written code, we provide simple tools which are easy to use and customizable. The researcher can easily integrate into their research project. The complete project source code is available in Github. Design/Methodology/Approach: The Modbus is the standard protocol to communicate between or among the devices. We need a better understanding of it and interface software to test around all aspects. Here we described some practical examples. The GUI is created using C# language inside the Microsoft Visual Studio. The application has several capabilities. In the TCP/IP mode, It can be a server or client. In RTU mode, it can play as a Master or slave device. We can also run two instances in a single system. To communicate between two running apps in RTU mode, we need virtual loopback software, two physical comm port, or two USB to Serial modules. For Modbus TCP mode, we can test within the system using the localhost address (127.0.0.1) or need an IP address for a different. Findings/results: The robot researcher can find helpful information about communicating the robot through the Modbus protocol. The practical example can help them to create packet purser. The functional CRC algorithm code can be used for better understanding and implementation into their project. Originality/Value: This work has some different features than other available utilities. We added features based on our research needs. Our created application is a little bit different from a professional approach. Various display formats are available in our GUI. That makes a difference in the originality of this work. Our GUI can be master, slave, server, or client, which is rarely available. Paper Type: Experimental-based Research.

Machine-Learned Recognition of Network Traffic for Optimization through Protocol Selection

We introduce optimization through protocol selection (OPS) as a technique to improve bulk-data transfer on shared wide-area networks (WANs). Instead of just fine-tuning the parameters of a network protocol, our empirical results show that the selection of the protocol itself can result in up to four times higher throughput in some key cases. However, OPS for the foreground traffic (e.g., TCP CUBIC, TCP BBR, UDT) depends on knowledge about the network protocols used by the background traffic (i.e., other users). Therefore, we build and empirically evaluate several machine-learned (ML) classifiers, trained on local round-trip time (RTT) time-series data gathered using active probing, to recognize the mix of network protocols in the background with an accuracy of up to 0.96.