Here is the code for the chaos program with the addition of user input for the number of loops.

#This program is chaos program
#in chapter 1
#It shows how chaotic results
#can arise from simple starts
#Steve Conger
#9/28/2017

def main(): #start of the main function block
    print("This program illustrates a chaotic function")
    x=eval(input("Enter a number between 0 and 1 "))
    y=eval(input("Enter the number of loops to do "))
    for i in range(y):
        x = 3.9 * x * (1-x)
        print(i,"\t", x)

main()

Here is the code for the loop variations

for i in range(10,0,-1):
    print(i)


x=5
for i in range(1,x):
    print(i)

Here is the code for the Temperature conversion

#Converts Celsius to Fahrenheit
#Steve Conger
#9/28/2017
#Three things take place in every program
#input--celsius temp
#processing, execution, Algorithm -9/5 * celsius + 32
#output--Fahrenheit

def main():
    celsius = eval(input("Enter a Celsius temperature "))
    fahrenheit = 9/5 * celsius + 32
    print("Your farhenheit temperature for ", celsius, "is " ,fahrenheit)

    

main()




    

Process and diagrams afternoon

Here are the undigested notes from the afternoon class

Process
Somebody needs a database
Interview the manager about the database
When do need it
What data --What does the database need to do
Track Tickets start and close
Prioritize criteria
need to be tell status, how long it takes to resolve a ticket, Who was assigned, Who are the techs
Descriptions.Report history of departments or of certain kinds of problems. Track all the computers,
list of all faculty and staff and which computers they use. Change time date. track who files the ticket.  Permissions, who can do what. Any big security issues?
Talk to the other stakeholders. 
Job shadowing
Review documents

Computer
computer number
make
model
Date issued
Date removed
location

faculty/staff
name
email
phone
office
computer number

Ticket
Date time
ticket number
issue
Description
Status
priority look up 
computer Number
faculty/staff ID

Locations
Building
Room
Dept
floor

Process and Diagram

Process

The first thing to do is to interview about the database Help desk for faculty and staff.

How many staff?

What do you want the database to do?

Questions? Store help desk tickets. what kinds of problems reoccur patterns. levels of service, priorities. Which technicians. Solutions to the tickets. Tickets status pending, solved, open. Severity. Reports. Response rates. list of all the computers, their locations and the faculty and/or staff that are assigned to them How soon?

List all the fields

faculty name
faculty office
faculty email

Computer
make
model
location
date installed
date removed

technicians
name
specialty
contact

Problem Categories

Ticket
date time
category
computer
faculty requester
problem
status

Response to Tickets
ticket number
technician
priority
Resolution date time
Note

What are they doing now--and in past

Interviewing people actually working with database

Job shadowing exceptions job flow missing information

Go back to the people you interviewed and ask, did I get it all, is something missing.

First Python

#This program will do a simple Hello world
#Steve C 9/26/2017

def main():
    name = input("Enter your name  ")
    print ("Hello," , name)

main()

#Does a simple calculation
#Steve 9/16/2017

def main():
    
    #number=eval(input("Enter a number from 1 to 41: "))
    for number in range(1,40):
        prime=number * number - number + 41
        print(prime)

main()