scholarly journals On the Potential of Execution Traces for Batch Processing Workload Optimization in Public Clouds

Author(s):  
Dominik Scheinert ◽  
Alireza Alamgiralem ◽  
Jonathan Bader ◽  
Jonathan Will ◽  
Thorsten Wittkopp ◽  
...  
Plant Methods ◽  
2021 ◽  
Vol 17 (1) ◽  
Author(s):  
Shuo Zhou ◽  
Xiujuan Chai ◽  
Zixuan Yang ◽  
Hongwu Wang ◽  
Chenxue Yang ◽  
...  

Abstract Background Maize (Zea mays L.) is one of the most important food sources in the world and has been one of the main targets of plant genetics and phenotypic research for centuries. Observation and analysis of various morphological phenotypic traits during maize growth are essential for genetic and breeding study. The generally huge number of samples produce an enormous amount of high-resolution image data. While high throughput plant phenotyping platforms are increasingly used in maize breeding trials, there is a reasonable need for software tools that can automatically identify visual phenotypic features of maize plants and implement batch processing on image datasets. Results On the boundary between computer vision and plant science, we utilize advanced deep learning methods based on convolutional neural networks to empower the workflow of maize phenotyping analysis. This paper presents Maize-IAS (Maize Image Analysis Software), an integrated application supporting one-click analysis of maize phenotype, embedding multiple functions: (I) Projection, (II) Color Analysis, (III) Internode length, (IV) Height, (V) Stem Diameter and (VI) Leaves Counting. Taking the RGB image of maize as input, the software provides a user-friendly graphical interaction interface and rapid calculation of multiple important phenotypic characteristics, including leaf sheath points detection and leaves segmentation. In function Leaves Counting, the mean and standard deviation of difference between prediction and ground truth are 1.60 and 1.625. Conclusion The Maize-IAS is easy-to-use and demands neither professional knowledge of computer vision nor deep learning. All functions for batch processing are incorporated, enabling automated and labor-reduced tasks of recording, measurement and quantitative analysis of maize growth traits on a large dataset. We prove the efficiency and potential capability of our techniques and software to image-based plant research, which also demonstrates the feasibility and capability of AI technology implemented in agriculture and plant science.


Author(s):  
Md Rubel Ahmed ◽  
Hao Zheng ◽  
Parijat Mukherjee ◽  
Mahesh C. Ketkar ◽  
Jin Yang

Author(s):  
Giles Reger ◽  
David Rydeheard

AbstractParametric runtime verification is the process of verifying properties of execution traces of (data carrying) events produced by a running system. This paper continues our work exploring the relationship between specification techniques for parametric runtime verification. Here we consider the correspondence between trace-slicing automata-based approaches and rule systems. The main contribution is a translation from quantified automata to rule systems, which has been implemented in Scala. This then allows us to highlight the key differences in how the two formalisms handle data, an important step in our wider effort to understand the correspondence between different specification languages for parametric runtime verification. This paper extends a previous conference version of this paper with further examples, a proof of correctness, and an optimisation based on a notion of redundancy observed during the development of the translation.


1967 ◽  
Vol 71 (676) ◽  
pp. 235-236 ◽  
Author(s):  
M. V. Wilkes

When digital computers first became available many of us expected that they would have an early and significant impact on engineering design. This did not happen, and the reasons why it did not are worth examining. For one thing, the early computers were not nearly large enough; engineers do not build things out of spheres and parallelograms as mathematicians do, and quite a lot of storage space is needed to describe a typical problem in engineering design. Unfortunately, the big computers when they came were so expensive that it was not considered economic to allow users to handle them personally, and batch-processing techniques were introduced. The result was to create a barrier between the computer and the design engineer, and to make it impossible for him to get results of any kind without a delay amounting to a few hours at the very best, and often to much more. Emphasis in fact, was put on the efficiency with which the central processor of the computer was used and no regard at all was paid to the efficiency with which the users—in this case programmers and design engineers—worked. We are on the threshold of a development which, there is every reason to hope, will change the situation radically.


Sign in / Sign up

Export Citation Format

Share Document