What a journey this has been. Other than leaving this to the last minute I think hacktoberfest was pretty fun. I really enjoyed learning about a lot of different and unique projects. For the last post, I plan to go over the last five post I have made.
Blog 1: https://codingblub.blogspot.com/2018/10/hacktoberfest-blog-1.html
This is the first post and on this post was my very first successful pull request, up until now I had only dreamed of getting pull request up, but thanks to my friend who showed me the ropes I was able to get one up.
Blog 2: https://codingblub.blogspot.com/2018/10/hacktoberfest-blog-2.html
This post was were I really started to learn about making CPU and its parts, registers, instructions, buses, etc... There was a lot of things i had to learn to get to this point. Although the pull its self was simple it still marks my development.
Blog 3: https://codingblub.blogspot.com/2018/10/hacktoberfest-blog-2_15.html
Now this was when I started to really understand the concepts, and I tried to test my metal. The purpose of this code was just to get the command to be converted to machine code. In the little picture I typed "HALT HALT" which refers to a command that the machine should understand as "0"
Blog 4: https://codingblub.blogspot.com/2018/10/hacktoberfest-blog-4.html
This one was propably the hardest of the total pull requests it defiantly took the longest. Glad to have it done tho. This was a tester function that i made which will have its own file.
Blog 5 : https://codingblub.blogspot.com/2018/10/hacktoberfest-blog-5.html
This one was a simple one i just updated the readMe.md to say that the project was in fact not closed but wide open.
All in all i would say it was a lot of fun. I just wish i didn't leave it to the last minute(i think i have a problem) But all is well that ends well. ahahahahah
Monday, October 29, 2018
Monday, October 15, 2018
Hacktoberfest Blog 4
Let goooooooooooooooooooooooooooooo only one more!!!!I hope you can read the excitement in my thots, but let's get this underway.
If I haven't already explained this when someone types in a command like "JMP" (which moves to a place spficyed by an adress you enter after the command). It and all its agumets get converted into machine code these simple bits are used in tandube with logic gates.
I wont go into to much detail about logic all you need to know is they are important. For this pull I created the framwork for the test code we will be useing. It is currently just in a function, but later on i should have its own cs file.
This simple tester just compares the insructions to itself and checks if they are the same. Later, when we start imlementing the machine's interprtation of these codes, we will change this to a static problem, and test if the machine has the right output.
If I haven't already explained this when someone types in a command like "JMP" (which moves to a place spficyed by an adress you enter after the command). It and all its agumets get converted into machine code these simple bits are used in tandube with logic gates.
I wont go into to much detail about logic all you need to know is they are important. For this pull I created the framwork for the test code we will be useing. It is currently just in a function, but later on i should have its own cs file.
This simple tester just compares the insructions to itself and checks if they are the same. Later, when we start imlementing the machine's interprtation of these codes, we will change this to a static problem, and test if the machine has the right output.
Hacktoberfest Blog 3
Number 3 haha, I didn't think I would get here. honestly, I think I have a problem. MOVING ON
Now that we understand the specs of the CPU we are building it is important to explain how much progress the project currently has completed.
The assembler, as well as the machine files, have been created not much code has been written, mostly just mapping out what the project could be. As such we needed to create a scope for all the instructions we wanted to make. What he did was create a hashtable which stored the string command, as well as its conversion in machine code.
What i did in this pull, was add the feature to output in the string form(will be number prob bits or byte) the value of the hash table.
Next, I will be looking to make a tester for this code
Now that we understand the specs of the CPU we are building it is important to explain how much progress the project currently has completed.
The assembler, as well as the machine files, have been created not much code has been written, mostly just mapping out what the project could be. As such we needed to create a scope for all the instructions we wanted to make. What he did was create a hashtable which stored the string command, as well as its conversion in machine code.
What i did in this pull, was add the feature to output in the string form(will be number prob bits or byte) the value of the hash table.
Next, I will be looking to make a tester for this code
Hacktoberfest Blog 2
Before I go on I would first like to explain this project a little, Building a CPU does not seem too intuitive and are very complex, in fact, don't even understand all of it. But I will try to explain what I do know. The current CPU is 16 bit, which can hold 256 instructions, these instructions can be used to do different things, such as insert, delete, move etc... In this pull request, I tried to specify in the documentation the grouping of some of the instructions.
Hacktoberfest Blog 1
hacktoberfest
Well, well, well someone said I couldn't do this last minute, well I'm here to prove you wrong. I got in contact with a friend that is developing a CPU.
My first pull request isn't all that special, I will just be updating the
Aura_CPU_Instructions.txt and fixing some mistakes with the file.
Nothing special, just some lines of text.
issue:https://github.com/Auios/Aurasm/issues/2
pull:https://github.com/Auios/Aurasm/pull/3
Friday, September 28, 2018
Release 1 Blog
Release 1
I worked on the stat.spec section of the filer code. The goal was to create promise version for a function in the .spec code. I started by git cloning the master repo and worked on some of the implementation. The problems started to hit, when i tried to run the testers and they failed, but they failed for reasons other then what i was expecting
I later found out that it was because of some code, in the .eslintrc.json file
in the line break section, under error it set the cli for a unix computer, after i changed the code to windows it began to pass the tests. unfortunately there where more problems. After running npm test command there seemed to be a problem with the karma test, and it started spitting out errors. By this time have spent more time trying to debug working code then i would like. Next time i think i will look closer at the process of people who have been successful with their pulls and understand how to go about doing this, because on my own it is something else.
I worked on the stat.spec section of the filer code. The goal was to create promise version for a function in the .spec code. I started by git cloning the master repo and worked on some of the implementation. The problems started to hit, when i tried to run the testers and they failed, but they failed for reasons other then what i was expecting
I later found out that it was because of some code, in the .eslintrc.json file
in the line break section, under error it set the cli for a unix computer, after i changed the code to windows it began to pass the tests. unfortunately there where more problems. After running npm test command there seemed to be a problem with the karma test, and it started spitting out errors. By this time have spent more time trying to debug working code then i would like. Next time i think i will look closer at the process of people who have been successful with their pulls and understand how to go about doing this, because on my own it is something else.
Subscribe to:
Posts (Atom)