Dairy cattle farmers' preferences for different breeding tools

Breeding technologies play a significant role in improving dairy cattle production. Scientifically proven tools for improved management and genetic gain in dairy herds, such as sexed semen, beef semen, genomic testing, dairy crossbreeding, and multiple ovulation embryo transfer (MOET), are readily available to dairy farmers. However, despite good accessibility, decreasing costs, and continuous development of these tools, their use in Sweden is limited. This study investigated Swedish dairy farmers' preferences for breeding tools through a survey including a discrete choice experiment. The survey was distributed online to 1 521 Swedish farmers and by an open link published through a farming magazine. In total, the study included 204 completed responses. The discrete choice experiment consisted of 10 questions with two alternative combinations, which gave 48 combinations in total. Utility values and part-worth values were computed using a conditional logit model based on the responses in the discrete choice experiment for nine groups of respondents: one group with all respondents, two groups based on respondents using dairy crossbreeding or not within the past 12 months, two based on herd size, two based on respondent age, and two based on whether respondents had used breeding advisory services or not. The strongest preferences in all groups were for using sexed semen and beef semen. Genomic testing was also significantly preferred by all groups of respondents. Except in large herds, MOET on own animals was significantly and relatively strongly disfavoured by all groups. Buying embryos had no significant utility value to any group. Dairy crossbreeding had low and insignificant utility values in the group of all respondents, but it was strongly favoured by the group that had used dairy crossbreeding within the past 12 months, and it was disfavoured by the group that had not. Part-worth values of combined breeding tools showed that combinations of sexed and beef semen, alone or with genomic testing without dairy crossbreeding, were the most preferred tools. Compared with the most common combinations of breeding tools used in the past 12 months, the part-worth values indicated that Swedish dairy farmers may prefer to use breeding tools more than they do today. Statements on the different breeding tools indicated that the respondents agreed with the benefits attributed to the breeding tools, but these benefits may not be worth the cost of genomic testing and the time consumption of MOET. These valuable insights can be used for further development of breeding tools

Performance Debugging and Tuning using an Instruction-Set Simulator

Instruction-set simulators allow programmers a detailed level of insight into, and control over, the execution of a program, including parallel programs and operating systems. In principle, instruction set simulation can model any target computer and gather any statistic. Furthermore, such simulators are usually portable, independent of compiler tools, and deterministic-allowing bugs to be recreated or measurements repeated. Though often viewed as being too slow for use as a general programming tool, in the last several years their performance has improved considerably. We describe SIMICS, an instruction set simulator of SPARC-based multiprocessors developed at SICS, in its rôle as a general programming tool. We discuss some of the benefits of using a tool such as SIMICS to support various tasks in software engineering, including debugging, testing, analysis, and performance tuning. We present in some detail two test cases, where we've used SimICS to support analysis and performance tuning of two applications, Penny and EQNTOTT. This work resulted in improved parallelism in, and understanding of, Penny, as well as a performance improvement for EQNTOTT of over a magnitude. We also present some early work on analyzing SPARC/Linux, demonstrating the ability of tools like SimICS to analyze operating systems

Implementing Test Automation with Selenium WebDriver

Many software programs, such as applications for designing, modeling, simulating, and analyzing systems, are now commonly available as web-based applications. The testing of such sophisticated web applications is highly challenging and can be extremely tedious and error-prone if done manually. Recently automation tools have become increasingly used for testing web-based applications, as they minimize human involvement and repetitive work. For this problem report project, we have built and implemented an automation testing framework for web applications. The project specifically uses a tool called Selenium WebDriver, which has been used to develop the testing framework. By using this framework, testers may quickly and effectively write their test cases. The benefits of Selenium WebDriver include that it does not require in-depth research and training by testers, and due to the framework\u27s ability to take screenshots, it provides a useful way for developers to study their code. The framework relies on the Chrome web browser, along with Java running in Eclipse, to provide a user-friendly interface for constructing and running test suites. To validate the testing framework, we performed a case study involving NanoHub (nanoHUB.org), which is a well-known platform that provides valuable resources for those involved in nanotechnology research and education. NanoHub serves as an open-access repository for a wide range of tools, simulations, and information related to nanoscale science and engineering, and it is designed particularly to model and simulate electronic systems and nanoscale phenomena. Testing a website such as NanoHub.org typically encompasses a blend of functional testing, usability testing, and performance testing. Based on the results of this testing, several observations are made about the testing framework in general, and its application to NanoHub in particular. The comprehensive testing approach documented in this report is aimed at ensuring the platform functions as intended, provides a user-friendly experience, and delivers optimal performance. This testing is particularly crucial when dealing with tools and simulations related to electronic systems

THE USE OF WEB-BASED EXAM (WBE) TO OPTIMIZE STUDENTS’ TESTING RESULT

This research was conducted based on theproblems found during the mid and final test by using paper and pen test; those are the students tend to do cheating, the sleepy supervisors, the inconsistency of test time, and the risk of losing the answer sheet. Therefore, the goals of the research are; 1) to make an appropriate WBE testing system, 2) to know the cheating rate of the students, 3) to find out the effectiveness of the system, and 4) to inform the benefits that might be taken by the WBE testing system’s users. By applyingRnD research model, the researcher applies a concept called web-based exam system which uses three main tools to run the system (teacher’s laptop as the server, WBE software, and access point to communicate the server and the user). The results indicated that the system reduces the students’ cheating rate 100%. Then, from the questionnaire given, the teacherstend to likeusing WBE testing system because they can monitor the whole process of the test from his own laptop and the result of the test will be analyzed and be saved automatically in his laptop. Moreover, it reduces time consumption and paper use.Keywords: web-based exam, testing system, testing result, cheating, softwar

The Millennium Run Observatory: First Light

Simulations of galaxy evolution aim to capture our current understanding as well as to make predictions for testing by future experiments. Simulations and observations are often compared in an indirect fashion: physical quantities are estimated from the data and compared to models. However, many applications can benefit from a more direct approach, where the observing process is also simulated and the models are seen fully from the observer's perspective. To facilitate this, we have developed the Millennium Run Observatory (MRObs), a theoretical virtual observatory which uses virtual telescopes to `observe' semi-analytic galaxy formation models based on the suite of Millennium Run dark matter simulations. The MRObs produces data that can be processed and analyzed using the standard software packages developed for real observations. At present, we produce images in forty filters from the rest-frame UV to IR for two stellar population synthesis models, three different models of IGM absorption, and two cosmologies (WMAP1/7). Galaxy distributions for a large number of mock lightcones can be `observed' using models of major ground- and space-based telescopes. The data include lightcone catalogues linked to structural properties of galaxies, pre-observation model images, mock telescope images, and Source Extractor products that can all be traced back to the higher level dark matter, semi-analytic galaxy, and lightcone catalogues available in the Millennium database. Here, we describe our methods and announce a first public release of simulated surveys (e.g., SDSS, CFHT-LS, GOODS, GOODS/ERS, CANDELS, and HUDF). The MRObs browser, an online tool, further facilitates exploration of the simulated data. We demonstrate the benefits of a direct approach through a number of example applications (galaxy number counts in CANDELS, clusters, morphologies, and dropout selections).Comment: MNRAS, in press. Millennium Run Observatory data products, online tools, and more available through http://galformod.mpa-garching.mpg.de/mrobs

Transferring Interactive Search-Based Software Testing to Industry

Search-Based Software Testing (SBST) is the application of optimization algorithms to problems in software testing. In previous work, we have implemented and evaluated Interactive Search-Based Software Testing (ISBST) tool prototypes, with a goal to successfully transfer the technique to industry. While SBSE solutions are often validated on benchmark problems, there is a need to validate them in an operational setting. The present paper discusses the development and deployment of SBST tools for use in industry and reflects on the transfer of these techniques to industry. In addition to previous work discussing the development and validation of an ISBST prototype, a new version of the prototype ISBST system was evaluated in the laboratory and in industry. This evaluation is based on an industrial System under Test (SUT) and was carried out with industrial practitioners. The Technology Transfer Model is used as a framework to describe the progression of the development and evaluation of the ISBST system. The paper presents a synthesis of previous work developing and evaluating the ISBST prototype, as well as presenting an evaluation, in both academia and industry, of that prototype's latest version. This paper presents an overview of the development and deployment of the ISBST system in an industrial setting, using the framework of the Technology Transfer Model. We conclude that the ISBST system is capable of evolving useful test cases for that setting, though improvements in the means the system uses to communicate that information to the user are still required. In addition, a set of lessons learned from the project are listed and discussed. Our objective is to help other researchers that wish to validate search-based systems in industry and provide more information about the benefits and drawbacks of these systems.Comment: 40 pages, 5 figure

Real world evaluation of aspect-oriented software development : a thesis submitted in partial fulfilment of the requirements for the degree of Master of Science in Computer Science at Massey University, Palmerston North, New Zealand

Software development has improved over the past decade with the rise in the popularity of the Object-Oriented (OO) development approach. However, software projects continue to grow in complexity and continue to have alarmingly low rates of success. Aspect-Oriented Programming (AOP) is touted to be one solution to this software development problem. It shows promise of reducing programming complexity, making software more flexible and more amenable to change. The central concept introduced by AOP is the aspect. An aspect is used to modularise crosscutting concerns in a similar fashion to the way classes modularise business concerns. A crosscutting concern cannot be modularised in approaches such as OO because the code to realise the concern must be spread throughout the module (e.g. a tracing concent is implemented by adding code to every method in a system). AOP also introduces join points, pointcuts, and advice which are used with aspects to capture crosscutting concerns so they can be localised in a modular unit. OO took approximately 20 years to become a mainstream development approach. AOP was only invented in 1997. This project considers whether AOP is ready for commercial adoption. This requires analysis of the AOP implementations available, tool support, design processes, testing tools, standards, and support infrastructure. Only when AOP is evaluated across all these criteria can it be established whether it is ready to be used in commercial projects. Moreover, if companies are to invest time and money into adopting AOP, they must be aware of the benefits and risks associated with its adoption. This project attempts to quantify the potential benefits in adopting AOP, as well as identifying areas of risk. SolNet Solutions Ltd, an Information Technology (IT) company in Wellington, New Zealand, is used in this study as a target environment for integration of aspects into a commercial development process. SolNet is in the business of delivering large scale enterprise Java applications. To assist in this process they have developed a Common Services Architecture (CSA) containing components that can be reused to reduce risk and cost to clients. However, the CSA is complicated and SolNet have identified aspects as a potential solution to decrease the complexity. Aspects were found to bring substantial improvement to the Service Layer of SolNet. applications, including substantial reductions in complexity and size. This reduces the cost and time of development, as well as the risk associated with the projects. Moreover, the CSA was used in a more consistent fashion making the system easier to understand and maintain, and several crosscutting concerns were modularised as part of a reusable aspect library which could eventually form part of their CSA. It was found that AOP is approaching commercial readiness. However, more work is needed on defining standards for aspect languages and modelling of design elements. The current solutions in this area are commercially viable, but would greatly benefit from a standardised approach. Aspect systems can be difficult to test and the effect of the weaving process on Java serialisation requires further investigation