Volume 2: Ptolemy II Software Architecture)

Total Page:16

File Type:pdf, Size:1020Kb

Volume 2: Ptolemy II Software Architecture) Heterogeneous Concurrent Modeling and Design in Java (Volume 2: Ptolemy II Software Architecture) Christopher Brooks Edward A. Lee Xiaojun Liu Stephen Neuendorffer Yang Zhao Haiyang Zheng Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2007-8 http://www.eecs.berkeley.edu/Pubs/TechRpts/2007/EECS-2007-8.html January 11, 2007 Copyright © 2007, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Acknowledgement This work was supported in part by the Center for Hybrid and Embedded Software Systems (CHESS) at UC Berkeley, which receives support from the National Science Foundation (NSF award #CCR-0225610), the State of California Micro Program, Rome AFRL, and the following companies: Agilent, DGIST, General Motors, Hewlett Packard, Infineon, Microsoft, National Instruments, and Toyota. PTOLEMY II HETEROGENEOUS CONCURRENT MODELING AND DESIGN IN JAVA Edited by: Christopher Brooks, Edward A. Lee, Xiaojun Liu, Steve Neuendorffer, Yang Zhao, Haiyang Zheng VOLUME 2: PTOLEMY II SOFTWARE ARCHITECTURE Authors: Shuvra S. Bhattacharyya Department of Electrical Engineering and Computer Sciences University of California at Berkeley Christopher Brooks I T Y • O F S • C R A http://ptolemy.eecs.berkeley.edu E A L V Elaine Cheong I I F N O U R • L John Davis, II N E E L T IG H T T I H H A E T R E BE • Mudit Goel Document Version 6.0 • •1 8 6 8• Bart Kienhuis for use with Ptolemy II 6.0 Edward A. Lee January 11, 2007 Man-Kit Leung Jie Liu Earlier versions: Xiaojun Liu • UCB/ERL M05/22, UCB/ERL M04/16, UCB/ERL M03/28, Lukito Muliadi UCB/ERL M02/23 UCB/ERL M99/40, UCB/ERL M01/12 Steve Neuendorffer John Reekie This work was supported in part by the Center for Hybrid and Embed- Neil Smyth ded Software Systems (CHESS) at UC Berkeley, which receives support Jeff Tsay from the National Science Foundation (NSF award #CCR-0225610), the Brian Vogel State of California Micro Program, Rome AFRL, and the following com- Winthrop Williams panies: Agilent, DGIST, General Motors, Hewlett Packard, Infineon, Yuhong Xiong Microsoft, National Instruments, and Toyota. Yang Zhao Haiyang Zheng Gang Zhou Copyright © 1998-2007 The Regents of the University of California. All rights reserved. “Java” is a registered trademark of Sun Microsystems. VOLUME 2 PTOLEMY II SOFTWARE ARCHITECTURE This volume describes the software architecture of Ptolemy II. The first chapter covers the kernel package, which provides a set of Java classes supporting clustered graph topologies for models. Clus- ter graphs provide a very general abstract syntax for component-based modeling, without assuming or imposing any semantics on the models. The actor package begins to add semantics by providing basic infrastructure for data transport between components. The data package provides classes to encapsu- late the data that is transported. It also provides an extensible type system and an interpreted expres- sion language. The graph package provides graph-theoretic algorithms that are used in the type system and by schedulers in the individual domains. The plot package provides a visual data plotting utility that is used in many of the applets and applications. The codegen package is a templated based code generator similar to the Ptolemy Classic code generators. The copernicus package is a code generator that performs static analysis on Java class files to produce smaller, faster executable models. Volume 1 gives an introduction to Ptolemy II, including tutorials on the use of the software, and vol- ume 3 describes the domains, each of which implements a model of computation. This page intentionally left mostly blank. Contents Volume 2 Ptolemy II Software Architecture 3 Contents 5 1. The Kernel 1 1.1. Abstract Syntax 1 1.2. Non-Hierarchical Topologies 2 1.2.1. Links 2 1.2.2. Consistency 2 1.3. Support Classes 4 1.3.1. Containers 4 1.3.2. Name and Full Name 4 1.3.3. Workspace 6 1.3.4. Attributes 6 1.3.5. List Classes 8 1.4. Clustered Graphs and Hierarchy 9 1.4.1. Abstraction 9 1.4.2. Relation Groups 12 1.4.3. Level-Crossing Connections 12 1.4.4. Tunneling Entities 13 1.4.5. Cloning 14 1.4.6. An Elaborate Example 14 1.5. Opaque Composite Entities 14 1.6. Concurrency 15 1.6.1. Limitations of Monitors 18 1.6.2. Read and Write Access Permissions for Workspace 20 1.7. Mutations 21 1.7.1. Change Requests 21 1.7.2. NamedObj and Listeners 23 1.8. Actor-Oriented Classes 24 1.9. Exceptions 25 1.9.1. Base Class 25 1.9.2. Less Severe Exceptions 25 1.9.3. More Severe Exceptions 27 2. Actor Package 29 2.1. Concurrent Computation 29 2.2. Message Passing 30 2.2.1. Data Transport 30 2.2.2. Example 33 2.2.3. Transparent Ports 34 2.2.4. Data Transfer in Various Models of Computation 36 2.2.5. Discussion of the Data Transfer Mechanism 39 2.3. Execution 40 2.3.1. Director 42 2.3.2. Manager 46 2.3.3. ExecutionListener 46 2.3.4. Opaque Composite Actors 47 2.4. Scheduler and Process Support 48 2.4.1. Function Dependency 48 2.4.2. Statically Scheduled Domains 49 2.4.3. Process Domains 51 3. Data Package 55 3.1. Introduction 55 3.2. Data Encapsulation 55 3.2.1. Matrix data types 57 3.2.2. Array and Record data types 57 3.2.3. Fixed Point Data Type 57 3.2.4. Function Closures 59 3.2.5. Nil Tokens 59 3.3. Immutability 59 3.4. Polymorphism 60 3.4.1. Polymorphic Arithmetic Operators 60 3.4.2. Automatic Type Conversion 61 3.5. Variables and Parameters 64 3.5.1. Values 64 3.5.2. Types 64 3.5.3. Dependencies 68 3.6. Expressions 68 3.7. Unit System 70 3.8. The Static Unit System 71 3.8.1. Unit Systems 72 3.8.2. Units of Measurement Algebra 73 3.8.3. Descriptive Form Language 75 3.8.4. Implementing the Static Unit System in Ptolemy 76 3.8.5. The Unit Library 78 3.8.6. Generating Descriptive Forms 78 3.8.7. UnitsConstraint Solver 79 3.8.8. Minimal Span Solutions 82 3.8.9. Implementing the Units Constraint Solver 85 Appendix: Expression Evaluation 86 Generating the parse tree 86 Traversing the parse tree 87 Node types 88 Extensibility 90 4. Graph Package 91 4.1. Introduction 91 4.2. Classes and Interfaces in the Graph Package 92 4.2.1. Element and ElementList 92 4.2.2. Labeled Lists 92 4.2.3. Node 92 4.2.4. Edge 93 4.2.5. Graph 93 4.2.6. Directed Graphs 93 4.2.7. Graph Mappings 97 4.2.8. Graph Analysis 97 4.2.9. Graph Analyzers 101 4.2.10. Strategies 102 4.2.11. Cached Strategies vs. Non-Cached Strategies 105 4.2.12. Graph Schedules 106 4.2.13. Graph Exceptions 107 4.2.14. Directed Acyclic Graphs and CPO 109 4.2.15. Inequality Terms, Inequalities, and the Inequality Solver 110 4.3. Example Use 111 4.3.1. Generating A Schedule for a Composite Actor 111 4.3.2. Forming and Solving Constraints over a CPO 111 5. Type System 115 5.1. Introduction 115 5.2. Formulation 119 5.2.1. Type Constraints 119 5.2.2. Run-time Type Checking and Lossless Type Conversion 120 5.3. Structured Types 121 5.3.1. Setting Up Type Constraints 122 5.4. Implementation 125 5.4.1. Implementation Classes 125 5.4.2. Type Checking and Type Resolution 126 5.4.3. Some Implementation Details 128 5.5. Examples 129 5.5.1. Polymorphic DownSample 129 5.5.2. Fork Connection 129 5.6. Actors Constructing Tokens with Structured Types 130 Appendix: The Type Resolution Algorithm 131 6. Plot Package 133 6.1. Overview 133 6.2. Using Plots 134 6.2.1. Zooming and filling 135 6.2.2. Printing and exporting 135 6.2.3. Editing the data 137 6.2.4. Modifying the format 138 6.3. Class Structure 139 6.3.1. Toolkit classes 140 6.3.2. Applets and applications 140 6.3.3. Writing applets 143 6.4. PlotML File Format 145 6.4.1. Data organization 146 6.4.2. Configuring the axes 147 6.4.3. Configuring data 150 6.4.4. Specifying data 151 6.4.5. Bar graphs 152 6.4.6. Histograms 152 6.5. Old Textual File Format 152 6.5.1. Commands Configuring the Axes 153 6.5.2. Commands for Plotting Data 154 6.6. Compatibility 155 6.7. Limitations 156 7. Code Generation 157 7.1. Motivation 157 7.2. A Helper-based Mechanism 158 7.2.1. What is in a C Code Template File? 159 7.2.2. What is in a Helper Java Class File? 160 7.2.3. The Macro Language 160 7.2.4. The CountTrues Example 162 7.3. Overview of The Software Architecture 163 7.4. Domains 167 7.4.1. SDF 167 7.4.2.
Recommended publications
  • Introduction to Scene Design COURSE SYLLABUS: Spring 2014
    THE 366.001 – Introduction to Scene Design COURSE SYLLABUS: Spring 2014 Instructor: Michael G. Knight, Jr., Assoc. Professor of Theatre Design & Technology Office Location: PAC rm. 104 Office Hours: by appointment Office Phone: 903.886.5311 Office Fax: 903.468.3250 University Email Address: [email protected] COURSE INFORMATION Materials – Textbooks, Readings, Supplementary Readings: Textbook(s)/Materials Required: 1. (1) package printer paper 2. 3 ring binder (2”) 3. Plenty of pencils 4. Plenty of paper (notes) 5. White card stock paper (8.5 x11) 6. Black foam core (5 sheets) 7. Vellum drafting paper (will be provided) 8. Balsa wood/Model wood 9. Art supplies 10. Acrylic Paper (8.5 x 11) Course Description: The basic techniques of the principles and practices of scenic design for stage. Included are design functions, construction, painting, modeling, history and theories of design. Pre-requisite THE 215 or instructor approval. Student Learning Outcomes: 1. The student will be able to understand the basic skills and theoretical practices involved in scenic design. 2. The student will be able to identify and understand the use of scenic design equipment and tools associated with design. 3. The student will be able to practically apply the skills learned in a completed scenic design (conceptual). COURSE REQUIREMENTS Instructional / Methods / Activities Assessments: Students will be graded on a series of quizzes, exams, type-written/hand written assignments, drafting projects, model projects, painting projects, and theoretical essay responses. Grading: Quizzes: 5 20 pts. 100 pts. Topic Assignments: 10 10 pts. 100 pts. Final Project 1 100 pts. 100 pts.
    [Show full text]
  • (Purple Masque) Scenic Design Checklist
    SECOND STAGE (PURPLE MASQUE) SCENIC DESIGN CHECKLIST MANDATORY ATTENDANCE AT: All director/designer meetings Minimum of two meetings with Faculty Scenic Designer: one prior to preliminary deadline, and one prior to final deadline. All production meetings Minimum of one run-through rehearsal prior to crew watch Crew watch All technical and dress rehearsals Strike Any conflicts with attending the above meetings/rehearsals must be cleared ahead of time with the faculty designer and the director. IMPORTANT INFORMATION There is a very limited time frame for installation and painting of scenery in the masque. Therefore, it is extremely important for you to be organized prior to your load in date. Some things to consider: You will be working late nights/weekends during load in and tech, so plan ahead to have papers/homework/studying done ahead of time. “I had to write a paper so the set didn’t get done until opening night” is not a valid excuse. EVERYTHING needs to be built prior to load in. It is best if you can paint pieces beforehand, also. If you are building a large unit, make sure it will fit through all doors. Large units in pieces should be “dry fit” in the scene shop to make sure they assemble as planned. Make sure you arrange for help ahead of time. People will be more willing to assist you if they know a week or two beforehand. This is not just your show. Having the scenery unfinished not only affects the actors, but the lighting and costume designs as well. ROUGH DESIGNS Rough designs will include research image boards of conceptual, architectural and detail inspirations for the set.
    [Show full text]
  • Sean Michael Savoie ˘ Lighting Designer 7358 Pershing Ave
    Sean Michael Savoie ˘ Lighting Designer 7358 Pershing Ave. Apt 2W z St. Louis, MO 63130 z 513.319.8407 [email protected] Professional Vita Employment Washington University in St. Louis St. Louis, MO Lighting Designer / Production Manager (Summer 2007 ˘ Present) • Teach all Lighting Design courses and others as assigned • Lead Designer for main stage productions and supervisor of student designs • Production Manager for Performing Arts Department • Design / Technology Coordinator The Muny St. Louis, MO Production Manager ( 2008 ˘ 2011) • Manage build, installation and tech of a very demanding seven show summer season • Coordination between IATSE crew and Broadway designers, directors and stage managers • 11,000 seat performance venue; over $7 million budget; Broadway’s top performers • Oversee design internship company • Nation’s oldest and largest outdoor musical theatre University of Cincinnati, College Conservatory of Music Cincinnati, OH Production Manager / Adjunct Instructor (Autumn 2005 ˘ Summer 2007) • Technical coordinator of all CCM Dance & Preparatory Department concerts • Technical coordinator of all CCM Unsupported (non-mainstage) workshops for Drama, Opera and Musical Theatre • Average academic year will include about 14 productions • Coordinate and manage student crews for any non-university performance group • Instructor of Stage Lighting I in BFA curriculum (full year course) • Instructor of Introduction to Lighting (quarterly) • Numerous lectures on Architectural Lighting Design & Practice Cincinnati Fringe Festival Cincinnati,
    [Show full text]
  • Scenic Design: a Compilation Kelly Meredith Paysinger Hart University of South Carolina - Columbia
    University of South Carolina Scholar Commons Theses and Dissertations 2014 Scenic Design: A compilation Kelly Meredith Paysinger Hart University of South Carolina - Columbia Follow this and additional works at: https://scholarcommons.sc.edu/etd Part of the Theatre and Performance Studies Commons Recommended Citation Hart, K. P.(2014). Scenic Design: A compilation. (Doctoral dissertation). Retrieved from https://scholarcommons.sc.edu/etd/2593 This Open Access Dissertation is brought to you by Scholar Commons. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of Scholar Commons. For more information, please contact [email protected]. SCENIC DESIGN: A COMPILATION by Meredith Paysinger Hart Bachelor of Arts Sweet Briar College, 2010 Submitted in Partial Fulfillment of the Requirements For the Degree of Master of Fine Arts in Theatre College of Art and Sciences University of South Carolina 2014 Accepted by: Nic Ularu, Director of Thesis Lisa Martin-Stuart, Reader Steven Pearson, Reader Lacy Ford, Vice Provost and Dean of Graduate Studies © Copyright by Meredith Paysinger Hart, 2014 All Rights Reserved. ii ABSTRACT Scenic Design: A Compilation ventures into the process of creating three productions including, Boeing Boeing, Fusions and Three Sisters. Exploring the foundations of each design, the content covers all aspects from the beginning to the implementation of each production. Supported through historical research, inspiration, function of space and the endless possibilities of creation, this thesis will reveal the growth of each design in great detail. Theatre is about collaboration, creating a world from a script and transforming it into an art of performance and design.
    [Show full text]
  • Theatrical Scenic Design: Creating the Physical World of the Play
    10th Annual Faculty Research & Creative Activities Symposium Presentation Title: Theatrical Scenic Design: Creating the Physical World of the Play Presenters: Sarah J. Fabian, Assistant Professor, Department of Communication, Media, and Theatre Abstract: Scenic design is an important component of any theatrical production as almost every production will have some form of a set, however minimal. Scenery can be abstract, photo-realistic, or anywhere in between. The primary function of the scenic design is to provide the audience with some context of location(s) for the theatrical work. However, the most important element of any scenic design is to impart a point of view about the story and the world of the play, sharing an emotional and textural experience to the production – Are there moments of surprise, something that suddenly appears that wasn’t previously there? Does the physical world of the play transform to reveal new layers to the story? As a scenic designer, you must be creative, innovative and visionary all while working within the director’s vision. Additionally, scenic designers must understand how to take their artistic vision and make it into a reality through the work executed by the scene shop staff and artisans. For the 10th Annual Faculty Research & Creative Activities Symposium, I will share my design process from page-to-stage, and present two contrasting examples of my scenic design work from the past year – Kate DiCamillo’s The Miraculous Journey of Edward Tulane adapted for the stage by Dwayne Hartford at Filament Theatre in Portage Park, and Fulfillment Center by Abe Koogler at A Red Orchid Theatre in Old Town.
    [Show full text]
  • Usitt Scenicdesign and Technicalproduction Graphicstandard
    A S U P P L E M E N T T O T H E S P R I N G 1 9 9 3 I S S U E O F T D & T U S I T T S C E N I C D E S I G N A N D T E C H N I C A L P R O D U C T I O N G R A P H I C S T A N D A R D USITT Education Commission Graphic Standards Board - Scenic Drafting Subcommittee Members Greg Bell James Brewczynski Dennis Dorn Jonathan Darling Ming Cho Lee Mark Shanda Frank Silberstein Robert F. Wolin Stephan M. Zapytowski (Chair) 18 March 1992 (reissued 15 April 1999) USITT SCENIC DESIGN AND TECHNICAL PRODUCTION GRAPHIC STANDARD 1.0 GENERAL. obvious that there will need to be whether the drawing is being prepared subsequent revision to this standard for a rigging crew, stage manager, 1.1 INTRODUCTION. as new assemblies and fabrication director, prop master, or one of the techniques become available and as other many specialty areas of the This first revision of the Scenic Design our understanding of standards performing arts which communicate and Technical Production Graphic becomes more refined. through the use of graphics. Whatever Standard is the result of many choices are made, however, each exchanges, both written and verbal. These revisions have been made based choice must be in the form of The initial document was published in on the assumption that the majority of communication that is clear, the 1982 Spring volume of the USITT scenic drafters will be using standard consistent, and efficient for both journal, Theatre Design & drawing tools rather than CADD drafter and reader.
    [Show full text]
  • A Little Night Music"
    University of Arkansas, Fayetteville ScholarWorks@UARK Theses and Dissertations 7-2020 The Scenic Design of "A Little Night Music" Kathleen Holmes University of Arkansas, Fayetteville Follow this and additional works at: https://scholarworks.uark.edu/etd Part of the Art and Design Commons, and the Other Theatre and Performance Studies Commons Citation Holmes, K. (2020). The Scenic Design of "A Little Night Music". Theses and Dissertations Retrieved from https://scholarworks.uark.edu/etd/3777 This Thesis is brought to you for free and open access by ScholarWorks@UARK. It has been accepted for inclusion in Theses and Dissertations by an authorized administrator of ScholarWorks@UARK. For more information, please contact [email protected]. The Scenic Design of “A Little Night Music” A thesis submitted in partial fulfillment of the requirements for the degree of Master of Fine Arts in Theatre by Kathleen Holmes Louisiana Tech University Bachelor of Arts in Theatre, 2017 July 2020 University of Arkansas This thesis is approved for recommendation to the Graduate Council. _____________________________ Michael Riha M.F.A Thesis Director _____________________________ _____________________________ Shawn Irish M.F.A Jason Burrow M.F.A Committee Member Committee Member Abstract A Little Night Music by Hugh Wheeler and Stephen Sondheim was produced by the University of Arkansas Department of Theatre in 2018-2019 academic school year. The scenic design process entailed a series of private meetings, design meetings, independent research, and analysis that all culminated into a full scenic design package. The show itself has many locations that quickly transition into one another. It was my challenge as the designer to cohesively design the scenery so that it could be transitioned easily and in time with the music.
    [Show full text]
  • Scenic Designer Contract
    Longwood University 2013 Scene Designer The Design Process: • Determine the production schedule and budget. • Read, assimilate, and understand the material being designed. • Find out as much as you can about: o The material in the script. o The director's concept. o The production circumstances (Type of stage, budget, etc.) • Decide on the show's “ism” (realism, expressionism, etc.) • Do background research (books, periodicals, paintings, etc,) • Do conceptual research (Create as many potential designs as possible) • Start by doing thumbnail sketches or models. • Choose the design that fits the best (this may be a mash-up of several designs) • Create the following: o A ground plan o Front elevations o Models o Detail drawings o Paint elevations o Properties lists o Property sketches • Evaluate the scenic design for safety. • Discuss masking placement with the technical director. Pre-Production: • Attend pre-production meetings with the director and other design team members. • Keep in mind that other people rely heavily on the scenery and it is therefore important to keep in contact with the director, technical director, stage manager, and other designers. • Meet with the technical director to discuss your budget. • The technical director will price your design. • If you are over budget you are responsible for lowering your overall cost. • There will be several scenic workshops held, supervised by you: o Scene shop safety and equipment, held by the technical director § All properties crew and carpenters should attend. o Painting, held by the scenic charge § All painters should attend. Rehearsal Process/Tech Week: • You are required to attend production meetings. o Give a brief statement about the progress of the show's set.
    [Show full text]
  • Designer Guidelines [List]
    Designing theatrical productions requires a great amount of time. If you are asked to design a departmental production you must be prepared to devote a great amount of time toward research, collaboration, designing, as well as fabrication and installation. While it is impossible to gauge in advance how much time any particular production will take, you should expect that the production, after class attendance and homework, will take a lead priority in your schedule. NYU-TSOA-UG DRAMA – Production & Design Studio REQUIREM ENTS OF THE SOUND DESIGNER The Sound Designer is expected to attend design/production meetings as required throughout the design/installation period of the production. Equally important, the Sound Designer is expected to regularly attend rehearsals and continue the design communication throughout the process. As a designer you will be called upon to help guide the educational experience of associate and assistant designers assigned to this project. When designs are due, the following is expected: • All designs for pre-recorded music and or sound effects andenhancement of “live” voices, musical instruments and sound elements, • Full sound equipment lists and a sound plot drawn to 1/2" = 1'-0" scale from Scenic Design and theatre drawings provided by NYU-TSOA Drama. (If necessary 3/8” = 1’-0” scale is acceptable.) Sound plot is to be coordinated with lighting and projection plots. • Design a sound delivery system that will properly execute the needs of the production. Provide a Signal Flow” that illustrates the connectivity of this system. • Participate in the installation of the sound delivery system. • A design presentation to acting company as well as to the production department and area staff.
    [Show full text]
  • Design for Performance: Scenic, Lighting and Costume Design Spring 2012 Unique #26040 Tuesdays and Thursdays 9: 30Am -11:00Am SCENIC: WIN Rm
    The University of Texas at Austin Department of Theatre and Dance TD 314C - Design For Performance: Scenic, Lighting and Costume Design Spring 2012 Unique #26040 Tuesdays and Thursdays 9: 30am -11:00am SCENIC: WIN rm. 2.138 * LIGHTING: WIN rm. 1.164 * COSTUME: WIN rm. 1.139 SCENIC DESIGN: Rowan Doyle [email protected] Office:Win B.204 (Grad design studio) Office Hours: TBA Scenic TA: Jocelyn Pettway [email protected] LIGHTING DESIGN: Rachel Atkinson [email protected] Office: Win B.204 (Grad design studio) Office Hours: Tues: 11-12, Thurs:11-12 and by appointment COSTUME DESIGN: Barbara Pope [email protected] Office: Win 1.113 Ph: 512-232-4436 Office Hours: Wed. 11:30-1:00, Thurs: 11:00-1:00 Costume TA: Kaitlyn Alyward [email protected] COURSE DESCRIPTION: This course is an introductory overview of design for performance from the perspective of the scenic, costume and lighting designer. You will learn about the design process and the artists and technicians involved in bringing a design to life. The class will be divided into three groups and will rotate through each design area. You will be asked to participate in various roles throughout this course, including researcher, designer and critic. Students’ success in this class requires active learning, and participation. Upon successful completion of this course you will be eligible to take more advanced courses in the respective design disciplines. COURSE GOALS: *To explore the design process through a variety of approaches and techniques. *To use critical thinking to investigate and analyze a text from the perspective of the designer.
    [Show full text]
  • Lighting Design Concept and Development of Spring Awakening by Frank Wedekind
    Lighting Design Concept and Development of Spring Awakening By Frank Wedekind A Thesis Presented in Partial Fulfillment of the Requirements for the Degree Master of Fine Arts in the Graduate School of The Ohio State University By Alex Kyle-DiPietropaolo Graduate Program in Theatre The Ohio State University 2011 Thesis Committee: Professor Mary Tarantino, Advisor Assistant Professor Jimmy Bohr Assistant Professor Janet Parrott Copyright by Alex Kyle-DiPietropaolo 2011 Abstract This thesis documents the design process for the production Spring Awakening by Frank Wedekind, as translated by Jonathan Franzen. The show was produced in The Ohio State University‟s Thurber Theatre from February 24th through March 13th, 2011. The design concepts for the production were developed as informed by an adolescent‟s perspective on the world, and the representation of that viewpoint through lighting design. Modern theatre techniques were employed to address issues raised in the play. One such modern technique was the use of live video to reinforce the emotional impact in key scenes, which required researching lighting design for the medium of film, and how to adapt it to the stage. Working within these design ideas, color and the positions of instruments were used to develop a hyper-reality where the adolescents‟ emotions and feelings are echoed in the world around them. ii Dedication This document is dedicated to those people who never let me get away with mediocrity. iii Acknowledgments First, I would like to acknowledge my parents. They accepted my floating through reality after reality, and only momentarily balked at my choice to make a career in theatre.
    [Show full text]
  • A Lighting Design Process for a Production of Godspell, Originally Conceived and Directed by John-Michael Tebelak with Music and New Lyrics by Stephen Schwartz
    A Lighting Design Process for a Production of Godspell, Originally Conceived and Directed by John-Michael Tebelak with Music and New Lyrics by Stephen Schwartz A Thesis Presented in Partial Fulfillment of the Requirements for the Degree Master of Fine Arts in the Graduate School of The Ohio State University By Anthony Steven Pellecchia, B.A. Graduate Program in Theatre The Ohio State University 2009 Masters Exam Committee: Professor Mary Tarantino, Advisor Assistant Professor Mandy Fox Associate Professor Kristine Kearney Copyright by Anthony Steven Pellecchia 2009 Abstract Godspell originally conceived and directed by John-Michael Tebelak with music and new lyrics by Stephen Schwartz, was a theatrical production presented during the spring quarter of 2009 at The Ohio State University produced by the Department of Theatre in collaboration with The Columbus Association of the Performing Arts at the Southern Theatre. This thesis is a documentation of the lighting design process for Godspell. The first chapter is a examination of the Southern Theatre and the producing situation. The second and third chapters explore the design ideas for the production through director concept, collaboration and script analysis. The last two chapters examine the lighting design process from initial stages to final product and provide self- evaluation of the final design. The concept for the production was to connect Godspell to central Ohio by creating a visual environment that reflected the changing and struggling economic landscape of a downtown landmark. The production was developed, researched and designed in order for viewers to absorb the overarching message of Godspell, while becoming energized and inspired to change the world around them.
    [Show full text]