DOCSLIB.ORG

Eindhoven University of Technology MASTER Extracting GXF Models

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Eindhoven University of Technology MASTER Extracting GXF Models Eindhoven University of Technology MASTER Extracting GXF models from C code towards LIME-ng tool-chain for dtaflow models Deshpande, A.S. Award date: 2010 Link to publication Disclaimer This document contains a student thesis (bachelor's or master's), as authored by a student at Eindhoven University of Technology. Student theses are made available in the TU/e repository upon obtaining the required degree. The grade received is not published on the document as presented in the repository. The required complexity or quality of research of student theses may vary by program, and the required minimum study period may vary in duration. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain Extracting GXF Models from C Code: towards LIME - next generation for Dataflow Models Aditya S. Deshpande August 2010 TECHNISCHE UNIVERSITEIT EINDHOVEN Department of Mathematics & Computer Science Software Engineering & Technology Master Thesis Extracting GXF Models from C Code towards LIME-ng Tool-chain for Dataflow models by Aditya S. Deshpande (0728718) Supervisors: dr. ir. Tom Verhoeff Pjotr Kourzanov, ir. Yanja Dajsuren, PDEng. August 2010 Preview This thesis introduces the LIME - next generation (LIME-ng) toolchain. LIME-ng was implemented at NXP Semiconductors B.V. Eindhoven. The project was developed in the department of media and signal processing at NXP research. The toolchain comprises of four independent tools. The tools developed as a part of LIME-ng toolchain include: • Extracting GXF Models from C code, by Aditya S. Deshpande, • Model Transformation tool for Dataflow Model Transformations [20], by Swaraj Bhat, • Generating C code from Platform Specific Model [42], by Nishanth Sudhakara Shetty and • Visualization of Dataflow Models [36], by Namratha Nayak. The first part (Part 1) of this thesis gives an introduction to the project undertaken and is common for all the thesis mentioned above. Parallel computing is a form of computation in which many calculations are carried out simultaneously [18], operating on the principle that large problems can often be divided into smaller ones, which are then solved concurrently ("in parallel"). With new advances in technology, the study of parallel systems has reached new magnitudes. The power of parallel systems for computational purposes is almost universal now. The result of this is a multitude of parallel systems. This might seem as an asset, but like every other thing it comes with its own set of drawbacks. All these parallel systems are mainly independent of each other, in the sense that they have their own architecture, their own memory models, etc. A particular application may work more efficiently on one parallel system but may not on another parallel system. An application developer may choose to develop a particular application on one of the parallel systems which he thinks is most apt. Later, if the application does not work as efficiently and as expected on the chosen parallel system then the developer has no other choice but to move the application to some other parallel system or rewrite the application. This move currently compels the application developer to start the development process again from scratch. i A way to overcome these problems is to provide a level of abstraction over the existing parallel systems/parallel languages. Abstraction is espe- cially important given the apparent diversity of different communication and synchronization mechanisms found in modern embedded platforms, often possessing heterogeneous multi-cores and accelerators operating in parallel to run the necessary application. On first thoughts, a single layer of abstraction should solve the problem. Library API's of parallel languages can be used as an abstraction layer to cover the bridge between the different parallel systems. Unfortunately, these API's are confined to specific architectures and cannot be easily migrated. Therefore, there is a need to introduce yet another layer of abstraction, this layer should allow the translation of the application to any programming language, giving the application developer the capability to develop an ap- plication once in any language, translate it into any other programming language and run it on its respective parallel hardware. The question thus is how to implement these abstractions as a practi- cal and feasible implementation. The answer to this question leads us to the development of a comprehensive tool chain which we refer to as LIME - next generation (LIME-ng). This tool chain can create dataflow models, transform these models into various platform specific representations and then translate them into their respective parallel language. The above men- tioned tool chain will also be incorporated with visual editing and graphical support. The task of implementing LIME-ng has been divided among four work packages. The tools to be developed will have the following functionalities: 1. Extracting GXF Models from C code - This tool handles the conversion of platform independent C code into a dataflow model for transforma- tion purposes. 2. Model Transformation tool for Dataflow Model Transformations - This tool applies a series of model transformations on an input dataflow model to make it more platform specific [20]. 3. Generating C code from Platform Specific Model - This tool translates the platform specific dataflow model to its corresponding C code and also provides error locating capabilities [42]. 4. Visualization of Dataflow Models - This tool provides visualization and editing capabilities to the dataflow model obtained from the GXF. [36]. ii Acknowledgement The success of any task will be incomplete without complimenting those who made it possible and whose guidance and encouragement made our effort successful. We are indebted to many people for making this project reach its logical ending. We sincerely express our thanks and gratitude to Dr. Tom Verhoeff who has been there for us at every cornerstone. We heartily thank ir. Pjotr Kourzanov from NXP Semiconductor, Eind- hoven whose encouragement, support, guidance and able supervision led us to the understanding and subsequent completion of this project. He has been a constant pillar of support and guidance right from the preliminary level to the concluding. We would also like to thank Yanja Dajsuren, PDEng. from Virage Logic for her timely evaluations and constructive remarks all throughout the project period. We also thank ir. Protic Zvezdan for his valuable guidance and support during the development of the Eclipse plugin. We owe our deepest gratitude to Dr. Manohara Pai M.M. our programme director and Dr. Radhika M. Pai, H.O.D., Department of I & CT, MIT, Manipal for providing us with their able guidance and moral support at every step during this project. Last but not the least we would like to thank the almighty for giving us the strength and our families & friends for trusting us and being there during all the ups and downs in the project. Aditya S Deshpande Namratha Nayak Nishanth Sudhakara Shetty Swaraj Bhat iii iv Contents Preview i I Introduction 1 1 Domain Information 3 2 Challenges 5 2.1 Motivation . 5 2.2 Dataflow Models . 6 2.3 GXF and DTD . 7 3 Existing Prototype 9 3.1 LIME . 9 3.1.1 Compilation flow . 10 3.2 LIMEclipse . 11 4 LIME-next generation 15 4.1 General Architecture . 15 4.2 Code to Model Transformation . 17 4.3 Model Transformation . 17 4.4 Visualization . 18 4.5 Unparsing . 20 4.6 Implementation Language - Functional Programming . 21 4.6.1 Benefits of Functional Programming: . 21 4.6.2 Why BIGLOO Scheme? . 22 II Extracting GXF Models from C Code 25 5 Recognizers and Parsers 29 5.1 Recognizers . 29 v 6 CIGLOO and Extensions 35 6.1 CIGLOO . 35 6.2 Analysis of the CIGLOO parser . 37 7 Implementations 53 7.1 Standardising the AST . 53 7.2 Formatting . 58 7.2.1 Pattern Matching . 58 7.3 Module translate read-ast . 60 7.4 Module SizeOf . 61 7.4.1 Structure Padding . 63 8 Validation and Performance Measurements 65 8.1 GLPK . 68 8.2 Graphviz . 69 8.2.1 SizeOf library . 70 8.2.2 ModifyAst library . 72 8.3 Performance Measurements . 72 8.4 Software metric . 73 8.5 Pmccabe . 74 9 Related work 79 9.1 Edison Design Group . 79 9.2 C Intermediate language (CIL) . 80 9.3 Src2srcML . 82 9.4 Columbus . 84 9.5 Design Maintenance System (DMS) . 85 10 Conclusion and Future Work 87 10.1 Conclusion . 87 10.2 Future Work . 88 Bibliography 90 Appendices 96 A Structure of CIGLOO Grammar 97 B Graphviz Test Results 101 C Links to the Source Files 103 vi List of Figures 2.1 An example dataflow graph with 4 nodes and 5 edges . 7 3.1 LIME tool-chain compilation flow[34]. 11 3.2 A dataflow model in LIMEclipse . 12 4.1 General Architecture of LIME-ng . 16 4.2 Example of the visual representation of a simple Dataflow graph with three nodes and edges between them. 19 4.3 Architecture of the tool developed. 27 5.1 An example for lookahead . 30 7.1 Architecture of Engine Modify module. 54 7.2 Representation of the AST for Case 1 . 56 7.3 Representation of the AST for Case 2 . 57 8.1 Package structure of Cigloo1.1 . 71 8.2 Pmccabe tool result page. 75 8.3 Graph of LOC vs Time taken for parsing and pretty printing 76 8.4 Graph of McCabe complexity vs Time taken for parsing and pretty printing .
Load more

Recommended publications
  • Hy Documentation Release 0.12.1+64.G5eb9283
    hy Documentation Release 0.12.1+64.g5eb9283 Paul Tagliamonte Apr 14, 2017 Contents 1 Documentation Index 3 1.1 Quickstart................................................4 1.2 Tutorial..................................................5 1.2.1 Basic intro to Lisp for Pythonistas...............................5 1.2.2 Hy is a Lisp-flavored Python..................................7 1.2.3 Macros............................................. 12 1.2.4 Hy <-> Python interop..................................... 13 1.2.5 Protips!............................................. 14 1.3 Hy Style Guide.............................................. 14 1.3.1 Prelude............................................. 15 1.3.2 Layout & Indentation...................................... 15 1.3.3 Coding Style.......................................... 16 1.3.4 Conclusion........................................... 17 1.3.5 Thanks............................................. 17 1.4 Documentation Index.......................................... 18 1.4.1 Command Line Interface.................................... 18 1.4.2 Hy <-> Python interop..................................... 19 1.4.3 Hy (the language)........................................ 21 1.4.4 Hy Core............................................. 47 1.4.5 Reader Macros......................................... 65 1.4.6 Internal Hy Documentation................................... 66 1.5 Extra Modules Index........................................... 72 1.5.1 Anaphoric Macros....................................... 72 1.5.2
    [Show full text]
  • An Industrial Strength Theorem Prover for a Logic Based on Common Lisp
    An Industrial Strength Theorem Prover for a Logic Based on Common Lisp y z Matt Kaufmannand J Strother Moore Personal use of this material is permitted. particular style of formal veri®cation that has shown consid- However, permission to reprint/republish this erable promise in recent years is the use of general-purpose material for advertising or promotional pur- automated reasoning systems to model systems and prove poses or for creating new collective works for properties of them. Every such reasoning system requires resale or redistribution to servers or lists, or considerable assistance from the user, which makes it im- to reuse any copyrighted component of this portant that the system provide convenient ways for the user work in other works must be obtained from the to interact with it. IEEE.1 One state-of-the-art general-purpose automated reason- ing system is ACL2: ªA Computational Logic for Applica- AbstractÐACL2 is a re-implemented extended version tive Common Lisp.º A number of automated reasoning of Boyer and Moore's Nqthm and Kaufmann's Pc-Nqthm, systems now exist, as we discuss below (Subsection 1.1). In intended for large scale veri®cation projects. This paper this paper we describe ACL2's offerings to the user for con- deals primarily with how we scaled up Nqthm's logic to an venientªindustrial-strengthºuse. WebegininSection2with ªindustrial strengthº programming language Ð namely, a a history of theACL2 project. Next, Section 3 describes the large applicative subset of Common Lisp Ð while preserv- logic supportedby ACL2, which has been designed for con- ing the use of total functions within the logic.
    [Show full text]
  • Mixing R with Other Languages JOHN D
    Mixing R with other languages JOHN D. COOK, PHD SINGULAR VALUE CONSULTING Why R? Libraries, libraries, libraries De facto standard for statistical research Nice language, as far as statistical languages go “Quirky, flawed, and an enormous success.” Why mix languages? Improve performance of R code Execution speed (e.g. loops) Memory management Raid R’s libraries How to optimize R Vectorize Rewrite not using R A few R quirks Everything is a vector Everything can be null or NA Unit-offset vectors Zero index legal but strange Negative indices remove elements Matrices filled by column by default $ acts like dot, dot not special C package interface Must manage low-level details of R object model and memory Requires Rtools on Windows Lots of macros like REALSXP, PROTECT, and UNPROTECT Use C++ (Rcpp) instead “I do not recommend using C for writing new high-performance code. Instead write C++ with Rcpp.” – Hadley Wickham Rcpp The most widely used extension method for R Call C, C++, or Fortran from R Companion project RInside to call R from C++ Extensive support even for advanced C++ Create R packages or inline code http://rcpp.org Dirk Eddelbuettel’s book Simple Rcpp example library(Rcpp) cppFunction('int add(int x, int y, int z) { int sum = x + y + z; return sum; }') add(1, 2, 3) .NET RDCOM http://sunsite.univie.ac.at/rcom/ F# type provider for R http://bluemountaincapital.github.io/FSharpRProvider/ R.NET https://rdotnet.codeplex.com/ SQL Server 2016 execute sp_execute_external_script @language = N'R' , @script =
    [Show full text]
  • The Embeddable Common Lisp
    ACM Lisp Pointers 8(1), 1995, 30-41 The Embeddable Common Lisp Giuseppe Attardi Dipartimento di Informatica, Universit`adi Pisa Corso Italia 40, I-56125 Pisa, Italy net: [email protected] Abstract The Embeddable Common Lisp is an implementation of Common Lisp designed for being embeddable within C based applications. ECL uses standard C calling conventions for Lisp compiled functions, which allows C programs to easily call Lisp functions and viceversa. No foreign function interface is required: data can be exchanged between C and Lisp with no need for conversion. ECL is based on a Common Runtime Support (CRS) which provides basic facilities for memory management, dynamic loading and dumping of binary images, support for multiple threads of execution. The CRS is built into a library that can be linked with the code of the application. ECL is modular: main modules are the program development tools (top level, debugger, trace, stepper), the compiler, and CLOS. A native implementation of CLOS is available in ECL: one can configure ECL with or without CLOS. A runtime version of ECL can be built with just the modules which are required by the application. 1 Introduction As applications become more elaborate, the facilities required to build them grow in number and sophistica- tion. Each facility is accessed through a specific package, quite complex itself, like in the cases of: modeling, simulation, graphics, hypertext facilities, data base management, numerical analysis, deductive capabilities, concurrent programming, heuristic search, symbolic manipulation, language analysis, special device control. Reusability is quite a significant issue: once a package has been developed, tested and debugged, it is un- desirable having to rewrite it in a different language just because the application is based in such other language.
    [Show full text]
  • Ants Go Marching—Integrating Computer Science Into Teacher Professional Development with Netlogo
    education sciences Article Ants Go Marching—Integrating Computer Science into Teacher Professional Development with NetLogo Mike Borowczak 1,* and Andrea C. Burrows 2 1 Department of Computer Science, College of Engineering and Applied Science, University of Wyoming, 1000 E University Ave, Laramie, WY 82071, USA 2 School of Teacher Education, College of Education, University of Wyoming, 1000 E University Ave, Laramie, WY 82071, USA; [email protected] * Correspondence: [email protected] Received: 1 February 2019; Accepted: 20 March 2019; Published: 26 March 2019 Abstract: There is a clear call for pre-collegiate students in the United States to become literate in computer science (CS) concepts and practices through integrated, authentic experiences and instruction. Yet, a majority of in-service and pre-service pre-collegiate teachers (instructing children aged five to 18) lack the fundamental skills and self-efficacy to adequately and effectively integrate CS into existing curricula. In this study, 30 pre-collegiate teachers who represent a wide band of experience, grade-levels, and prior CS familiarity participated in a 16-day professional development (PD) course to enhance their content knowledge and self-efficacy in integrating CS into existing lessons and curricula. Using both qualitative and quantitative methodology, a social constructivist approach guided the researchers in the development of the PD, as well as the data collection and analysis on teacher content knowledge and perceptions through a mixed-methods study. Ultimately, participants were introduced to CS concepts and practices through NetLogo, which is a popular multi-agent simulator. The results show that although the pre-collegiate teachers adopted CS instruction, the CS implementation within their curricula was limited to the activities and scope of the PD with few adaptations and minimal systemic change in implementation behaviors.
    [Show full text]
  • 23 Things I Know About Modules for Scheme
    23 things I know about modules for Scheme Christian Queinnec Université Paris 6 — Pierre et Marie Curie LIP6, 4 place Jussieu, 75252 Paris Cedex — France [email protected] ABSTRACT difficult to deliver (or even rebuild) stand-alone systems. The benefits of modularization are well known. However, Interfaces as collection of names — If modules are about shar- modules are not standard in Scheme. This paper accompanies ing, what should be shared ? Values, locations (that is an invited talk at the Scheme Workshop 2002 on the current variables), types, classes (and their cortege` of accessors, state of modules for Scheme. Implementation is not addressed, constructors and predicates) ? only linguistic features are covered. Cave lector, this paper only reflects my own and instanta- The usual answer in Scheme is to share locations with neous biases! (quite often) two additional properties: (i) these loca- tions can only be mutated from the body of their defin- ing modules (this favors block compilation), (ii) they 1. MODULES should hold functions (and this should be statically (and The benefits of modularization within conventional languages easily) discoverable). This restricts linking with other are well known. Modules dissociate interfaces and implemen- (foreign) languages that may export locations holding tations; they allow separate compilation (or at least indepen- non-functional data (the errno location for instance). dent compilation a` la C). Modules tend to favor re-usability, This is not a big restriction since modern interfaces (Corba common libraries and cross language linkage. for example) tend to exclusively use functions (or meth- Modules discipline name spaces with explicit names expo- ods).
    [Show full text]
  • Basic Lisp Techniques
    Basic Lisp Techniques David J. Cooper, Jr. February 14, 2011 ii 0Copyright c 2011, Franz Inc. and David J. Cooper, Jr. Foreword1 Computers, and the software applications that power them, permeate every facet of our daily lives. From groceries to airline reservations to dental appointments, our reliance on technology is all-encompassing. And, it’s not enough. Every day, our expectations of technology and software increase: • smart appliances that can be controlled via the internet • better search engines that generate information we actually want • voice-activated laptops • cars that know exactly where to go The list is endless. Unfortunately, there is not an endless supply of programmers and developers to satisfy our insatiable appetites for new features and gadgets. Every day, hundreds of magazine and on-line articles focus on the time and people resources needed to support future technological expectations. Further, the days of unlimited funding are over. Investors want to see results, fast. Common Lisp (CL) is one of the few languages and development options that can meet these challenges. Powerful, flexible, changeable on the fly — increasingly, CL is playing a leading role in areas with complex problem-solving demands. Engineers in the fields of bioinformatics, scheduling, data mining, document management, B2B, and E-commerce have all turned to CL to complete their applications on time and within budget. CL, however, no longer just appropriate for the most complex problems. Applications of modest complexity, but with demanding needs for fast development cycles and customization, are also ideal candidates for CL. Other languages have tried to mimic CL, with limited success.
    [Show full text]
  • IDOL Connector Framework Server 12.0 Administration Guide
    Connector Framework Server Software Version 12.0 Administration Guide Document Release Date: June 2018 Software Release Date: June 2018 Administration Guide Legal notices Copyright notice © Copyright 2018 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Trademark notices Adobe™ is a trademark of Adobe Systems Incorporated. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. UNIX® is a registered trademark of The Open Group. Documentation updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. To verify you are using the most recent edition of a document, go to https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result?doctype=online help. You will also receive new or updated editions of documentation if you subscribe to the appropriate product support service. Contact your Micro Focus sales representative for details. To check for new versions of software, go to https://www.hpe.com/software/entitlements. To check for recent software patches, go to https://softwaresupport.softwaregrp.com/patches. The sites listed in this section require you to sign in with a Software Passport.
    [Show full text]
  • A Tutorial on Lisp Object-Oriented Programming for Blackboard Computation (Solving the Radar Tracking Problem)
    Electrical and Computer Engineering ECE Technical Reports Purdue Libraries Year A TUTORIAL ON LISP OBJECT-ORIENTED PROGRAMMING FOR BLACKBOARD COMPUTATION (SOLVING THE RADAR TRACKING PROBLEM) P. R. Kersten∗ A. C. Kak† ∗Naval Undersea Warfare Center Division, †Purdue University School of Electrical Engineering, This paper is posted at Purdue e-Pubs. http://docs.lib.purdue.edu/ecetr/233 A TUTORIAL ON LISPO BJECT- ORIENTED PROGRAMMING FOR BLACKBOARD COMPUTATION (SOLVING THE RADAR TRACKING PROBLEM) TR-EE 93-24 JULY 1993 A TUTORIAL ON LISP OBJECT -ORIENTED PROGRAMMING FOR BLACKBOARD COMPUTATION (SOLVING THE RADAR TRACKING PROBLEM)* P. R. Kersten Code 2211 Naval Undersea Warfare Center Division Newport, RI 02841-5047 A. C. Kak Robot Vision Lab 1285 EE Building Purdue University W. Lafayette, IN 47907- 1285 ABSTRACT This exposition is a tutorial on how object-oriented programming (OOP) in Lisp can be used for programming a blackboard. Since we have used Common Lisp and the Com- mon Lisp Object System (CLOS), the exposition demonstrates how object classes and the primary, before, and after methods associated with the classes can be used for this pur- pose. The reader should note that the different approaches to object-oriented program- ming share considerable similarity and, therefore, the exposition should be helpful to even those who may not wish to use CLOS. We have used the radar tracking problem as a 'medium' for explaining the concepts underlying blackboard programming. The blackboard database is constructed solely of classes which act as data structures as well as method-bearing objects. Class instances fonn the nodes and the levels of the blackboard.
    [Show full text]
  • Secrets of the Glasgow Haskell Compiler Inliner
    Secrets of the Glasgow Haskell Compiler inliner Simon Marlow Simon Peyton Jones Microsoft Research Ltd, Cambridge Microsoft Research Ltd, Cambridge [email protected] [email protected] Septemb er 1, 1999 A ma jor issue for any compiler, esp ecially for one that Abstract inlines heavily,is name capture. Our initial brute-force solution involved inconvenient plumbing, and wehave Higher-order languages, such as Haskell, encourage the pro- now evolved a simple and e ective alternative Sec- grammer to build abstractions by comp osing functions. A tion 3. go o d compiler must inline many of these calls to recover an eciently executable program. At rst wewere very conservative ab out inlining recur- sive de nitions; that is, we did not inline them at all. In principle, inlining is dead simple: just replace the call But we found that this strategy o ccasionally b ehaved of a function by an instance of its b o dy. But any compiler- very badly. After a series of failed hacks we develop ed writer will tell you that inlining is a black art, full of delicate a simple, obviously-correct algorithm that do es the job compromises that work together to give go o d p erformance b eautifully Section 4. without unnecessary co de bloat. Because the compiler do es so much inlining, it is im- The purp ose of this pap er is, therefore, to articulate the p ortant to get as much as p ossible done in each pass key lessons we learned from a full-scale \pro duction" inliner, over the program.
    [Show full text]
  • Decreasing the Environmental Impact in an Egg-Producing Farm Through the Application of LCA and Lean Tools
    applied sciences Article Decreasing the Environmental Impact in an Egg-Producing Farm through the Application of LCA and Lean Tools Iván E. Estrada-González 1, Paul Adolfo Taboada-González 2 , Hilda Guerrero-García-Rojas 3 and Liliana Márquez-Benavides 4,* 1 Faculty of Biology, Building “R”, Ground Floor, University Campus, UMSNH, 58000 Morelia, Michoacán, Mexico; [email protected] 2 Facultad de Ciencias Químicas e Ingeniería, Universidad Autónoma de Baja California, Calzada Universidad No. 14418, Mesa de Otay, 22390 Tijuana, Mexico; [email protected] 3 Faculty of Economy “Vasco de Quiroga”, Building “T2”, Upper Floor, University Campus, UMSNH, 58000 Morelia, Michoacán, Mexico; [email protected] 4 Institute of Agricultural and Forestry Research (IIAF)-UMSNH, San Juanito Itzícuaro Avenue, C.P. 58341 San Juanito Itzícuaro, Morelia, Michoacán, Mexico * Correspondence: [email protected] Received: 18 January 2020; Accepted: 12 February 2020; Published: 17 February 2020 Abstract: Intensive poultry farming transforms vegetable protein into animal protein through shelf egg and chicken meat production. Mexico is the largest egg consumer and fifth-ranked egg producer worldwide. However, the environmental impact of egg production in this country is scarcely reported. This research aimed to design an eco-efficient approach for egg production in a semi-technified farm based on door-to-door life cycle assessment (LCA) and value stream mapping (VSM) methodologies. The LCA points out that the climate change category is a hotspot in egg production, with emissions of 5.58 kg CO2 eq/kg per egg produced. The implementation of an eco-efficient scheme focused on energy usage could result in a 49.5% reduction of total energy consumption and 56.3% saving in environmental impacts.
    [Show full text]
  • The Future of Programming for Non-Programmers
    THE FUTURE OF PROGRAMMING FOR NON-PROGRAMMERS P. Co Goldberg Rapporteurs: Miss. JoM. Harrison Dr. B.N. Rossiter Mr. J, Stewart 17 TilE FUTURE OF PROGRAMi\1ING FOR NON-PROGRAMMERS Introduction The basic issue uddressed by workers in the arca of automatic programming is: Must programming be the exclusive d0l11ain of "professional programmers," with extensive training in cornputer science. or can the computer be made accessible to specialists in other fields who could make usc of its capabilities, if only they could easily master the arl of programl11ing? Although rixed application packages are often useful when programming ability is abscnt, in general such packages lack flexibility; as a consequence. they cannot bc tailored to an individual's particular needs. Thus a primary area of concern in uutomatic programming is the development of methods which make it possible for non-programmers to construct programs tailored to their requirements. In this sequence bf lectures we would like to discuss the current status of work in automatic programming. and to focus on some of the important problems to be solved in the area. There arc a number of quite different approaches to automatic programming which are currently being pursued. Among these are: (I) The development of application-orienfed I'erv high lel'el languages which embody a style of programming that closely rnimics the coml11on, but less formal. style of algorithmic expression in that application area. The assumption behind these attempts is that. since the intended user of the language is an expert in that application area, he will be able to translate his informal algorithms into formal specifications - provided the translation does not require a drastic shift in his "computational model." (2) The development of clls(omizahle packages.
    [Show full text]