Tag: finalproject

Tic Tac Toe

--Originally published at Valeria CT

https://github.com/valeriact/tc1017/blob/master/tictactoe.cpp

 

The final project is done! I made the first part, that I published on a previous post, and Damian made the second and last part. From what he told me, he had a lot of help from Ken, but was able to do it nonetheless.

The process consisted of a lot (too much) debugging and then adding new features, like the input user error, play again, etc.

The final code is on the link at the beginning of this post.

-Valeria


Project Update (Plot twist…)

--Originally published at My TC1017 programming class

So, about the project Valeria and I were going to do, we decided to give up on that one. Reason being, that it required a little more time than what we had, so we had to come up with a new idea that was simple enough for us to work fast, but no so that Mr. Ken would tell us not to.

We came up with the idea of making a Sudoku, but er soon realized it was not as simple as we thought. Then, we moved up to a Tic Tac Toe. It turns out that it was not as simple as I thought, so we decided to go for it.

About the game, Valeria made the table, and a function that would make sure the user wrote the correct input. In my opinion, probably the hardest part of the game.

Then, I made sure that the program recognized who won (if any), and allow the players to chose if they wanted to replay or not. At the same time, I wanted to make the file an executable, but I couldn’t since the Ubuntu Terminal runs in a Linux environment.

Without any more waiting, I (as always) will put the link to the Google Drive file.


Final Project pt. 1

--Originally published at Valeria CT

Today I gathered with Damián to work on the project and we decided that we wanted to change it, since we have too little time and it was really complicated to do the physical glove. So we decided to do a tic tac toe, which consists of only programming, and that we’ll do it with c++.

We began programming, deciding whether to use vectors, chars, etc. Today we got done the display and the input (we’re still missing to mark fail when the user inputs a string). We’ll continue working on that omorrow and once that’s done, we’ll figure out how to make a loop that constantly checks for a winner.

Here’s the link to the file on my GitHub:  https://github.com/valeriact/tc1017/blob/master/project.cpp

And a list of the resources we’ve used so far:

-Valeria

 

“Tic-Tac-toe” flickr photo by realeyez https://flickr.com/photos/realeyez/506773807 shared under a Creative Commons (BY-NC-ND) license


Final Project

--Originally published at Programming in C++

Programa de enlace entre farmacia y consultorio médico pensado para el sector público.

Objetivo: Optimizar el proceso de atención y disminuir la cantidad de recetas no abastecidas.

Características:

  • Ver disponibilidad de medicamentos en farmacia
  • Ver diferentes presentaciones del medicamento
  • Marcar error
  • Facilitar correo al supervisor
  • Amigable

Cronograma de trabajo:

3 de noviembre: abrir archivos de excel (sacar cantidad de medicamentos disponibles y sus presentaciones)

10 de noviembre: marcar error y enviar correo (error de dedo y preguntar por el correo del supervisor)

17 de noviembre: últimos detalles (hacer programa amigable)

21 de noviembre: Entrega final

*Trabajo a la hora de clases, en caso de ser necesario se trabajará tiempo extra


Final project for TC1017

--Originally published at My TC1017 programming class

A Brief Explanation

For the final project, I teamed up with Valeria Cruz.

We want to create a glove (using an Arduino board as the processing unit) than can read sign language and then translate it to audio, so mute people can communicate more easily with others.

The project is a work Valeria had done before in secondary school. She already has the program for reading the sign language on the glove. What we are trying to do, more than making the code for the signal reading, is to create a code that will take those inputs, turn them into words, and then convert them into audio that can be listened.

Below, there is rough schedule (Made by Valeria).

 

SCHEDULE

Week from the 23rd to the 29th of October

  • Research and try to learn as much as possible on this type of language
  • Search and buy the materials that we’re going to need

Week from the October 30th to November 5th 

  • Begin writing our code
  • Start making the circuit and connecting the sensors, etc.

Week from the 6th to the 12th of November

  • Test our written part code and make corrections
  • Begin the ‘turn to audio’ part

Week from the 13th to the 17th of November

  • Finish our code and test it several times

November 21st

  • Hand in the final project (If finished).

 

DONE! 


Defining final project

--Originally published at Valeria CT

For the final project I teamed up with Damian and we plan on doing a glove for mute people that allows them to communicate with those who do not know the sign language.

We want to adapt a glove with sensors and program it so that when the user signs a letters, our program detects it and then, when they’re done, it can read what they said out loud.

We want to use Arduino, since we have the Arduino board already and we know the basics of programming in this language; however, we still need to learn a lot more on how to convert text to audio.

 

SCHEDULE

Week from the 23rd to the 29th of October

  • Research and try to learn as much as possible on this type of language
  • Search and buy the materials that we’re going to need

Week from the October 30th to November 5th 

  • Begin writing our code
  • Start making the circuit and connecting the sensors, etc.

Week from the 6th to the 12th of November

  • Test our written part code and make corrections
  • Begin the ‘turn to audio’ part

Week from the 13th to the 17th of November

  • Finish our code and test it several times

November 21st

  • Hand in the final project

 

DONE! 

 

 


css.php