It's UWAweek 51

help3011

This forum is provided to promote discussion amongst students enrolled in CITS3011 Intelligent Agents.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying selected article
Showing 1 of 83 articles.
Currently 11 other people reading this forum.


 UWA week 40 (2nd semester, week 10) ↓
SVG not supported

Login to reply

👍x1
helpful
12:21pm Wed 2nd Oct, Andrew G.

ANONYMOUS wrote:

I've noticed that the agent seems to persist throughout the tournament, since it is only created once at the start. This means that it could remember things between games in the tournament.

When the projects are marked, are they tested using the same tournament code that we have or some other way, and if so, are we allowed to use this ability to remember things between games? (I suspect this is what the game_outcome method is for, since otherwise it can't see what it would be used for, but I could be misunderstanding it.)

Thanks

No, you should not assume that your agent will survive between games. The testing code provided is not exactly the same as how your code will be assessed, and game_outcome is provided so your agents as you are developing them can know the outcome (useful for learning techniques, etc.). Your agent as submitted should be ready to be dropped into a game with no "warm up time", and may be assessed as such.

Besides, the only thing I think you could do with this information between rounds is metagaming by trying to learn how other agents you are up against play. This may work at the testing scale, where there are only a handful of agents you are competing against, but in more thorough testing against more effective agents, it can't help you.

So I guess you are welcome to implement this, but I do not expect it will actually make your agent more effective in any measurable way, so probably not a priority!

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy