Flow Chart For a 'for' Loop In Python

  • Context: Python 
  • Thread starter Thread starter Taylor_1989
  • Start date Start date
  • Tags Tags
    Flow Loop Python
Click For Summary
SUMMARY

This discussion focuses on creating flow charts for 'for' loops in Python, emphasizing the differences in representation compared to other programming languages like BASIC. Participants highlight the importance of understanding the flow chart's structure, including the use of specific shapes such as rectangles for actions and diamonds for decisions. The conversation also touches on the flexibility of flow chart design, suggesting that while there are general guidelines, the specific implementation can vary based on the programmer's intent and the level of detail required.

PREREQUISITES
  • Understanding of Python programming, specifically 'for' loops
  • Familiarity with flow chart symbols and their meanings
  • Basic knowledge of algorithm design and representation
  • Experience with diagramming tools for creating flow charts
NEXT STEPS
  • Research Python's 'for' loop mechanics and its iteration over different data structures
  • Study flow chart best practices and standard symbols
  • Explore UML diagramming techniques for software design
  • Learn how to use diagramming software like Visual Paradigm for flow chart creation
USEFUL FOR

Beginner Python programmers, software developers looking to document algorithms, and educators teaching programming concepts through visual aids.

  • #61
The secret of the ASR 33 and ASR 35 teletype machines was some kind of force feedback (I don't know how it worked), that forced you to slow down and type in perfect rhythm with the machine. That did not make fast typing, but it greatly reduced the error rate.

Even today, I wager that I could type with fewer errors with the help of a metronome.
 
Technology news on Phys.org
  • #62
Some vintage history on the teletype

http://www.samhallas.co.uk/repository/telegraph/teletype_story.pdf
And more specifically the asr33

https://en.m.wikipedia.org/wiki/Teletype_Model_33
The heavier key press was due to electromechanical feel of a typewriter. I suspect it may have been an engineering scheme to control the speed of the character bits written to tape or sent over the line as well as typing it on the paper. It’s true though you developed a certain rhythm when typing at about 10 characters per second.
 
Last edited:
  • Informative
Likes   Reactions: anorlunda
  • #63
anorlunda said:
The secret of the ASR 33 and ASR 35 teletype machines was some kind of force feedback (I don't know how it worked), that forced you to slow down and type in perfect rhythm with the machine.
A key part of that mechanism was the requirement for deep keystrokes. You had to push the key down about half an inch for it to register - and once one key was down, the next could not be pressed at all until the first key had fully returned to its original position. Since a key would not return to its original position until the cycle had ended, you couldn't type ahead at all.
 
  • Like
  • Informative
Likes   Reactions: jbriggs444 and anorlunda
  • #64
I've tried using Ctrl +C to break infinite loops, to no effect, in Jupyter notebooks . Do you know anything else that would break an infinite loop?
 
  • #65
WWGD said:
I've tried using Ctrl +C to break infinite loops, to no effect, in Jupyter notebooks . Do you know anything else that would break an infinite loop?

1671582850912.png

https://en.wikipedia.org/wiki/Power_symbol
 
  • Like
Likes   Reactions: DrJohn and WWGD
  • #66
WWGD said:
I've tried using Ctrl +C to break infinite loops, to no effect, in Jupyter notebooks . Do you know anything else that would break an infinite loop?
Kernel -> Interrupt, or the ■ button.
 
  • Like
Likes   Reactions: WWGD
  • #67
sysprog said:
You could wire the plug-board on a card duplicating machine to allow that, but how would you get, say, an IBM model 29 keypunch machine to do that? It not only doesn't detect which corner is cut, but also as far as I know, it has no capability to read anything on a card, except if you wrap the card around the program drum to be used as a program card, and in that case it could only heed the codes specific to that keypunch machine; not duplicate the card.
Since this thread has been bumped. I'll respond to this.
Here is a link to a 029 instructional video.
The actual mp4 file is here.
The photos below are from frames of that video.
This first image shows the part of the card bed between the punching station (out of frame to the right) and the read station (on the left).
029KeyPunchReadstationB.jpg

I have circled an important part of the card path. It is where a card can be manually fed to the read station.
There's a corresponding slot on the bottom of the card bed that is only barely visible from the cameras viewing angle.
To duplicate a damaged card, feed that damaged source card through that "slot" and feed a blank card to the punching station.
Then, hold down the "DUP" key:
029KeyPunchReadstationD.jpg

029KeyPunchReadstationE.jpg
 

Similar threads

  • · Replies 5 ·
Replies
5
Views
2K
  • · Replies 10 ·
Replies
10
Views
3K
Replies
6
Views
3K
  • · Replies 9 ·
Replies
9
Views
4K
  • · Replies 43 ·
2
Replies
43
Views
4K
  • · Replies 17 ·
Replies
17
Views
3K
  • · Replies 16 ·
Replies
16
Views
3K
  • · Replies 31 ·
2
Replies
31
Views
3K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 3 ·
Replies
3
Views
1K