Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » datacomm
notes:datacomm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
notes:datacomm [2018/10/02 10:14] – [Morse Code Fun (Mcf0)?] bstrong2notes:datacomm [2018/10/30 13:11] – [Mcf1?] bstrong2
Line 10: Line 10:
 Since our getting started plan is learning some python, generally the first project that you do is making the "Hello, World!" program, that is probably where we should start :P. Since our getting started plan is learning some python, generally the first project that you do is making the "Hello, World!" program, that is probably where we should start :P.
  
-======Morse Code Fun (Mcf0)?====== +======Morse Code Fun (Mcf0) Due October 17th====== 
-**morse code sender/receiver: Due October 17th**+**morse code sender/receiver:**
  
 Alright, so at this point we should all have a decent understanding of how python works... Alright, so at this point we should all have a decent understanding of how python works...
Line 22: Line 22:
  
 ^^^ totally not copied from Wikipedia... Basically it's a way of communication through sound using long and short sounds called dits(short sounds) and dahs(long sounds).  ^^^ totally not copied from Wikipedia... Basically it's a way of communication through sound using long and short sounds called dits(short sounds) and dahs(long sounds). 
 +
 +
 +**How much functionality should the program have?**
 +
 +The program shall be able to recognize these letters: 
 +  * **[A-Z]**
 +  * **Comma: ---...**
 +  * **Equals: -...-**
 +  * **Period (also called full stop): .-.-.-**
 +  * **Question mark: ..--..**
 +  * **AA new line (\n): .-.-**
 +  * **AR end of message (EOF): .-.-.**
  
  
Line 27: Line 39:
  
 First thing we need to come up with a way to express our dits and dahs (that way we can use each others programs to encode/decode morse code). **We shall use "." for dits, and "-" for dahs. For spaces how about we use " | "**... Open to suggestions on that :P. First thing we need to come up with a way to express our dits and dahs (that way we can use each others programs to encode/decode morse code). **We shall use "." for dits, and "-" for dahs. For spaces how about we use " | "**... Open to suggestions on that :P.
-So our encoder should be able to convert text into the dits and dahs, and our decoder should convert dits and dahs to text. +So our encoder should be able to convert text into the dits and dahs, and our decoder should convert dits and dahs to text.
  
 encoder ex: encoder ex:
  
-  * encoder --> . -. -.-. --- -.. . .-. +  * $ ./encode <<< "encoder" --> . -. -.-. --- -.. . .-. .-.- .-.-. 
-  * enc oder --> . -. -.-. | --- -.. . .-. +  * $ ./encode <<< "enc oder" --> . -. -.-. | --- -.. . .-. .-.- .-.-. 
-  * $ ./encode <<< "hello" +  * $ ./encode <<< "hello" --> .... . .-.. .-.. --- .-.- .-.-. 
-        .... . .-.. .-.. --- .-.- .-.+        
 decode ex: decode ex:
  
-  * . -. -.-. --- -.. . .-. --> encoder +  * $ ./decode «< “. -. -.-. --- -.. . .-. .-.- .-.-." --> encoder 
-  * . -. -.-. | --- -.. . .-. --> enc oder +  * $ ./decode «< “. -. -.-. | --- -.. . .-. .-.- .-.-." --> enc oder 
-  * $ ./decode <<< "hello" | ./decode --> hello+  * $ ./encode <<< "hello" | ./decode --> hello
              
-  
- 
-**How much functionality should the program have?** 
- 
-The program shall be able to recognize these letters: **[A-Z], Comma: ---..., Equals: -...-, Period (also called full stop): .-.-.-, Question mark: ..--.., AA new line (\n): .-.-, AR end of message (EOF): .-.-.** 
- 
  
 **Should we have the program accept the augments in argv, or use input?** **Should we have the program accept the augments in argv, or use input?**
Line 59: Line 65:
 really give our encoders/decoders a stress test to make sure they process really give our encoders/decoders a stress test to make sure they process
 information accordingly." information accordingly."
 +
 +======Mcf1?======
 +So far it seems that one of our objectives is to send encoded messages to each other, and be able to decode the message... So to help with this here is a link that you might find useful, if any of you guys find something useful feel free to share it with the rest of us boi's :P.
 +[[https://www.tutorialspoint.com/python/python_networking.htm]]
 +Good luck everyone!!!
 ======URLs====== ======URLs======
 Pythons built in functions: Pythons built in functions:
Line 71: Line 82:
 How does one start programming on lab46? How does one start programming on lab46?
  
-There might be a different way, but this is what i'm doing... So if you add this line to the file that you intend to program in, then you're all good to start programming in thee dank python. **#!/usr/bin/env python**, so all you would need to do is make the file executable, and run it whenever you want to execute your program.+There might be a different way, but this is what i'm doing... So if you add this line to the file that you intend to program in, then you're all good to start programming in thee dank python. **#!/usr/bin/python3**, so all you would need to do is make the file executable, and run it whenever you want to execute your program. Just a note, we have decided to use python3 for our programming adventures, so make sure that you are using that, and not python2.
  
 Another way to run a Python Program is to simply include the command python before your script. Another way to run a Python Program is to simply include the command python before your script.
notes/datacomm.txt · Last modified: 2018/11/15 01:07 by bstrong2

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki