It's UWAweek 53

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 the 4 articles in this topic
Showing 4 of 83 articles.
Currently no other people reading this forum.


 UWA week 38 (2nd semester, week 8) ↓
SVG not supported

Login to reply

👍x1
helpful
4:36pm Fri 20th Sep, ANONYMOUS

Hi, I understand gozz has mentioned that he prefers us not to look at the provided code for the other agents, and that we should devise our own strategy to solve this project. Are we allowed to use the variables in the agent.py class, namely the mission sizes, spy count and betrayals required dictionaries in our strategy?


SVG not supported

Login to reply

👍?
helpful
10:44am Sat 21st Sep, ANONYMOUS

Also are we allowed to use the fact that one of the agents is a random agent in our decision making? Not necessarily looking at the code in it, but just the fact that the actions of it are random, and so we can't use its actions to determine whether it is a resistance or a spy, but for the other agents we can


 UWA week 39 (2nd semester, week 9) ↓
SVG not supported

Login to reply

👍?
helpful
1:22pm Tue 24th Sep, Andrew G.

ANONYMOUS wrote:
> Hi, > > I understand gozz has mentioned that he prefers us not to look at the provided code for the other agents, and that we should devise our own strategy to solve this project. > > Are we allowed to use the variables in the agent.py class, namely the mission sizes, spy count and betrayals required dictionaries in our strategy?
You are explicitly required to subclass the Agent class from `agent.py`. My previous statements have advised students not to analyse the benchmark agents provided (BasicAgent, SatisfactoryAgent), as you should be solving the problem yourself from scratch, and if we have reason to believe you have plagiarized from the benchmark agents you may receive zero marks. Agent and `agent.py` are not mentioned in this, as it is not an agent, but just the interface and rules information available to your agent.


SVG not supported

Login to reply

👍?
helpful
1:28pm Tue 24th Sep, Andrew G.

ANONYMOUS wrote:
> Also are we allowed to use the fact that one of the agents is a random agent in our decision making? > > Not necessarily looking at the code in it, but just the fact that the actions of it are random, and so we can't use its actions to determine whether it is a resistance or a spy, but for the other agents we can
Your agent will be tested (as in the tournament code) against various combinations of agents. It is not valid to assume that any particular agent (or any agent at all) will play randomly. Furthermore, if you were to do so, this would simply mean that you are optimizing your play against the random agent, and a better agent can be expected to play at least that well, as the better agent could always *choose* to play randomly. I encourage you to swap out what agents are in the tournament to assess the performance of your agent(s) against different combinations. Remember that it will only use whatever agents you have put in the agents directory. As you develop better agents, you can put them into rotation and see if you are able to develop one that consistently outperforms them.

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