Analogically, if Tensorflow is the extravagant building that stands firm and tall. Python constitutes the roots that support it.
Therefore, the GDSC has arranged a session on the basics of Python Language, as the 4th edition in the Tensorflow Bootcamp Workshops.
The utmost fundamentals, the building blocks of your code ie: datatypes, several types of loops, conditional statements and Functions, are going to be discussed in detail. And as students, we've been listening to the emphasis laid on the importance of basics since 1947.
So we call out all those who are ambitious to grow to attend this session. Specially, the freshmen (since their course includes a touch of Python). Python being the most fascinating language there is; make sure you don't miss out on the opportunity.
🕐Tuesday, December 7, 2021 from 3:00 PM - 4:00 PM GMT +0500.
Register here: https://tinyurl.com/GDSCTF03
Stream the session live at: https://meet.google.com/awn-ifrf-rqo
#TensorFlow #dataanlytics #dataanalysis #datascience #python #pythonprogramming #function #loops #conditionalstatements #datatypes #GoogleDeveloperStudentClubs #GDSCNUCES #gdsc #GoogleDSC #GoogleDevelopersGroup #GDSCNUCESKHI #FASTNU #Google #training #workshop #Bootcamp #community
0 notes
Syllabus
DIG 1710: Introduction to Game Design
Professor Mark Simpson
_________________________
Important Dates
Class Sessions:
Monday 5:30pm-8:50pm in Room 8109
Tuesday/Thursday 2:20-4:00pm in Room 3410
Fall Term: August 28th – December 15th 2017
Final Exam Week: December 18-22 (Monday-Friday)
Last day to drop with refund: September 1 (Friday)
MDC Holidays Fall 2017
September 2-4 (Saturday-Monday)
November 10-12 (Friday- Sunday)
November 23 Thanksgiving
Website: dig1710.tumblr.com
Required Materials
Textbook: The Art of Game Design: A Book of Lenses
Flash Drive and/or cloud storage
Tumblr account & blog dedicated to this class
Class Competencies
Competency 1: The student will demonstrate how to evaluate game concepts by:
Comparing different game concepts.
Composing a game concept document.
Presenting and justifying the game concept.
Identifying and comparing the different genres of games.
Competency 2: The student will demonstrate an understanding of various tools that are used in game development by:
Identifying different computer programming languages used for game development.
Reviewing different development environments for game development.
Studying automation software for game and software development.
Competency 3: The student will demonstrate an understanding of the game development process by
Distinguishing the different stages of the game development process.
Creating a generic plan for developing a game.
Competency 4: The student will demonstrate an understanding of 3D computer environments by:
Reproducing simple objects in different coordinate systems.
Manipulating screen coordinates to create new game levels.
Converting and exporting objects and levels between different 3D environments.
Competency 5: The student will demonstrate an understanding of game development tools by:
Creating simple shapes and structures that can be exported to games or game editors.
Modifying an existing level in a game using editing tools.
Creating a level that can be ported to an existing game engine or editor.
Competency 6: The student will demonstrate an understanding of how to analyze the different uses of textures by:
Creating texture maps for object in games.
Modifying existing texture maps to work with new designs.
Applying new textures for changing the look and feel of existing game levels.
Distinguishing between the different types of texture mappings.
Competency 7: The student will demonstrate an understanding of level design, creation tools, and editors by:
Distinguishing the different level building tools.
Examining the game development process and application to help design new tools for building levels
Competency 8: The student will demonstrate an understanding how to design game levels by:
Distinguishing the different types of levels in terms fun factor.
Discussing how to decrease and increase the difficulty for player each type of game level.
Creating a new level for an existing game, that is going to address all the issues of difficulty.
Competency 9: The student will demonstrate an understanding of how to export created levels to existing game engines by:
Creating building blocks for game level editors and existing engines.
Creating programs that will be able to convert and export levels into game engines and level editors.
Modifying existing items to make them exportable in to game engines and level editors.
Competency 10: The student will demonstrate an understanding of game development by:
Creating conditionalstatements and loops for games.
Modifying sprites to add simple motion to games.
Developing a simple 2D side scrolling game using a game development software kit.
Grades
Mid-Term 20%
Final 30%
Homework 35%
Attendance 15%
(subject to change)
GRADING SCALE
A 100 - 90
B 80 - 89
C 70 – 79
D 60 – 69
F 0 - 59
COURSE POLICIES:
Attendance Policy:
Students are expected to attend all the classes.
Class attendance and participation is pre-supposed and strongly recommended.
Attendance will be taken each class session and students are expected to attend all scheduled class sessions.
To obtain credit for attendance; students must sign the attendance “sheet” distributed in class.
If absent, it is your responsibility to keep fully informed about the notes, class material discussed (including syllabus adjustments, additional reading assignments, changes in examination material and dates, etc.).
Students who stop attending class will receive a letter grade of “F” for the course unless they submit a drop card to the Registrar’s office prior to the withdrawal deadline date.
If you will be absent from class for any reason, please message me in advance.
Lectures are given at the beginning of the class, therefore, if a student is absent during the lecture portion of the class, it is his/her responsibility to cover/study the material that is missed.
Late homework is subject to a 10% late penalty for each day it is late.
No homework may be submitted more than 1 week late.
Academic Dishonesty Procedure:
Academic dishonesty is defined as an action inconsistent with the ethical standards of Miami Dade College. Academic dishonesty includes the following actions, as well as other similar conduct aimed at making false representation with respect to a student’s academic performance.
Collaborating with others in work to be presented, if contrary to the stated rules of the course.
Plagiarizing, including the submission of other’s ideas or papers (whether purchased, borrowed, or otherwise obtained) as one’s own.
Submitting, if contrary to the rules of a course, work previously presented in another course.
Knowingly and intentionally assisting another student in any of the above actions, including assistance in an arrangement whereby any work, classroom performance, examination, or other activity is submitted or performed by a person other than the student under whose name the work is submitted or performed. Some actions of academic dishonesty, such as stealing examinations or course material and falsifying records, may be processed through the Student Disciplinary Procedure.
The Student Disciplinary Procedure may be found on the Student’s Rights & Responsibilities Guide (page 20).
Students are to work individually during lab hours, unless otherwise instructed.
If the prohibited behavior continues, the student may receive an an “F” for the course.
Copying Project Files from another student is prohibited; both students, the author and whoever copied, will earn a grade of “F” for that assignment or exam.
Course Withdrawal:
A student not completing the course for any reason is required to submit an official drop notice to the Registrar’s office.
If a student decides to withdraw; it is the responsibility of the student to do so by the course withdrawal date provided on the College Academic Calendar.
If a student stops attending this class, the student may be dropped from the course without notice and the student’s record will show a grade of “IW” (Instructor Withdrawal).
Students are responsible for checking the College Academic Calendar for refund and course withdrawal deadline dates.
Incomplete Grade:
In this class, an “Incomplete” or “I” grade is not usually given.
An incomplete grade (“I” grade) is only available at the discretion of the instructor; as a result of a documented emergency that prohibits your completing the course.
The “I” grade applies to students that cannot submit the final project.
Students will only be considered for an incomplete grade if it is beyond the course withdrawal date and the student is passing the course at the time of the request.
The instructor and the student will complete an Agreement for Grade of Incomplete form.
This agreement will determine the requirements for a course grade which must be completed by the end of the next major term or a failing grade will be assigned.
CLASSROOM POLICIES:
1. Electronic (cellphones, iPods…etc.) devices are to be either turned off or in silent mode.
2. NO electronic (cellphones, mp3, etc.) devices are allowed during lecture.
3. Eating, drinking, chewing gum, or smoking is strictly prohibited in the electronic classroom.
4. All food items such as soda cans, gum, food wrappings…etc. should be disposed of prior to entering the electronic classroom.
5. Behavior in the electronic classroom is expected that will allow for conditions that foster learning and a free exchange of ideas. A positive learning atmosphere is one that shows respect and courtesy for the instructor and fellow students. For example, such things as whispering, sleeping, working on other subject matters, or interrupting students or instructor, will not be tolerated.
6. Students will be punctual. Being late to a class is disruptive and rude to both the instructor and to the rest of the class.
7. Personal matters will be discussed with the instructor outside of class. Either right outside the electronic classroom or in the instructor’s office. 1. Distinguishing the different stages of the game development process. 2. Creating a generic plan for developing a game.
0 notes