It is important to have full control of what you are doing, and I think that a logging system is needed. And maybe you think it is not important at this stage, but I think it is, to have it from the beggining is a must for me.
Search
Showing posts with label log. Show all posts
Showing posts with label log. Show all posts
Wednesday, August 21, 2013
Saturday, April 6, 2013
Google Code
Well, as I promised I created an SVN repository in Google Code with the program. I am commiting there the new program in Python.
The repo is here and every time I commit I will tell you here, with all the changes.
For now in rev2:
- There is a main that calls the mainLoop.
- The main loop ceates a board (as described in old posts) and initializes it.
- A logger class is created and it writes in a file (ETlog.txt) the empty board.
- IT enters in a loop and exits.
Yes, that's it, but is good for a start. I am "translating" my old code from Python to Java (explained why in previous posts).
So, that's how it is, had for me but... I think I am more confortable writing in Python than in Java.
Labels:
baduk,
board,
computer go,
go,
igo,
log,
main loop,
programming,
python,
weiqi
Tuesday, December 18, 2012
Day 130: At least it worked
Well, I was having lots of problems with KGS connection, but as I suspected, the problem was not with KGS, it was with me. Every command that don't need a return at least should have an empty string return. Komi command didn't return it so all commands coming from behind were queued.
Solved that, but saw that KO rule was working bad, so I will have to redesing it. I have an idea. I will create a new class for KO, because ko rule will not only need to prevent illegal moves, but start some things in the future.
Solved that, but saw that KO rule was working bad, so I will have to redesing it. I have an idea. I will create a new class for KO, because ko rule will not only need to prevent illegal moves, but start some things in the future.
Thursday, October 4, 2012
Day 57: First video and log
As I promised, here is a video of how is the program working so far.
The program is SLOW, this is because I am logging a lot, it is running on an overcharged computer and is running from a pendrive. So, to save this I should:
The program is SLOW, this is because I am logging a lot, it is running on an overcharged computer and is running from a pendrive. So, to save this I should:
- Make less logging (just log the same info but writing less).
- Sometimes I should run this from a computer that works well, it just plays random moves, it shouldn't take so long to choose a valid move.
- Run it from a hard disk XD.
But, right now what bothers me is how to continue.
The log (10 moves... 206kb.), that is something impossible to keep.
Tuesday, October 2, 2012
Day 55: Eureka!
Finaly solved the problem, well, two problems. In suicide the data was persisting somehow, so, inexistent groups were being compared. The other was in how it searched for suicide.
Next: A little video with random moves and a log :).
Labels:
baduk,
computer go,
frustrating,
gtp,
igo,
log,
problems,
programming,
weiqi
Friday, September 28, 2012
Day 51: More code deleted and state
As I said some days before, "human" class didn't have any more sense in the program. Now I saw that "console" class have the same problem. The only console I need is the gtp console, so console class can be out of here (but I will make a backup of the class, just in case some day for some weird reason I want to add a parameter to show the game in console).
Now, this is how classes are right now:
So, one part of the boring update is on, now, let's continue logging. Next post will have a log.
Labels:
baduk,
computer go,
design,
go,
gtp,
log,
programming,
weiqi
Thursday, September 27, 2012
Day 50: Back to work!
After some days without touching code, I am back!
Now is time for some boring work:
Now is time for some boring work:
- Log everything in the system. I just want that all what the machine "thinks" keeps logged. That is because it is hard to find bugs in another way.
- Redo the class draw. I really love coding and sometimes being a lot analyzing how it should work is boring. BUT NEEDED.
Monday, September 3, 2012
Day 26: Logging
To see if all what I want to control on the engine is working the way I like, I need to log all that it does. This is the first approach to this:
Important: In Windows 7 you need to run GoGui in Administrator Mode.I made methods to:
- Log any String I want.
- Log the date and time
- Log the board as it is in the moment.
Tuesday, August 28, 2012
Day 20: Logger
I am having some errors with the change to GTP, so, I need to see what is happening in the program every time this moves. I will need it anyway to study what the program does now, I don't have the console anymore to see results because now I write to the GTP console.
So, I am working on a class to log whatever I want.
Subscribe to:
Posts (Atom)