FIT5222 Flatland Challenge Submission Instruction
FIT5222 Flatland Challenge
Submission Instruction
Hi everyone, we are glad to announce that the contest server for the FIT5222 Flatland
Challenge is online at http://fit-web96-v01.ocio.monash.edu:5000/! Now, you can submit your
question3 solution and we will evaluate your solution on 24 contest instances. Read the
submission instruction before submission!
Evaluation
Instance characteristics
Map Size Number of Agents Max Time Steps Amount
10 x 10 5 150 4
25 x 25 12 937 4
50 x 50 25 3750 4
75 x 75 37 8437 4
100 x 100 50 15000 4
150 x 150 75 33750 4
Limitation on submissions
● You are only allowed to use 1 thread to solve the problem.
● Write the solution only in python.
● All dependent packages must be available in conda or pip.
● Timelimit for evaluating all 24 instances is 4 hours.
● The memory limitation is 4 GB.
If your submission takes more than 4 hours or uses more than 4 GB memory, the process
will be killed and submission fails.
Please note, the execution on instances with 75 agents is slow and the evaluation time
depends on the makespan of your solution. If you submit the dummy (default codes in
question 3, which generates solutions with makespan of max_time_steps/10 ) solution for
question 3, the evaluation time of all 24 instances will be around 1 hour.
FIT5222 Flatland Challenge Submission Instruction
Ranking
Your submission is ranked by the mean of the ratio of agents reach destinations (Mean Ratio
of Done) and Sum of Normalized SIC.
, while i is the id of each instance. =
= 0
23
∑ (




+

)
The rank first prefers the Mean Ratio of Done. Then, it prefers the Sum of Normalized SIC.
We expect all of you have the Mean Ratio of Done = 1, which means all agent reach their
destination.
Deadline
The submission closes at the Due time of Assignment 1.
Submission
Register on Contest Server
1. Open contest website: http://fit-web96-v01.ocio.monash.edu:5000/
2. Click “Register” and register with your Monash Email.
3. Click Submit.
4. At the same time, you should receive a repo invitation email from Bitbucket. Check
you Monash Email.
5. Click “Accept My Invitation” in the email.
6. Follow the instructions from Bitbucket to register a bitbucket account using Monash
Email or directly join the repo if you already registered.
Post a thread on bitbucket if you didn’t receive the invitation email from Bitbucket
Bitbucket App Password/SSH-KEY
To push codes to your Bitbucket repo, you need to create an app password or set up
ssh-key to access your repo through git.
FIT5222 Flatland Challenge Submission Instruction
Set up an app password to access the repository with git:
This will generate a random password for you. Remember the password (it’s difficult) or save
it somewhere, as it only shows once.
FIT5222 Flatland Challenge Submission Instruction
For advanced git user, set up your ssh-key following the instructions on:
https://support.atlassian.com/bitbucket-cloud/docs/set-up-an-ssh-key/
Link to Submission Git Repo
1. On the contest website, click “Show Git Link”. Then click “Open Git Repo”.
2. Select Https if using the app password, and copy the https link following the “git
clone” text.
3. In the terminal/command-line interface, open your piglet-public folder. You should
make sure you are in the assignment1 branch and have question3.py in the folder.
4. Link the remote repo with:
git remote add contest_server your_git_repo_link
Submit Your Codes
5. If you use any dependency python packages (packages you installed manually from
pip and used in your assignment) that are not listed in environment.yml file,
add it to environment.yml file. (For pip packages add after -pip: and use the
same format as other items)
6. Stage and commit all your changes (including the environment.yml, question3.py,
and any other required files written by you). The simplest way to do this is in the root
folder of piglet-public:
git add *
git commit -m ”Changed Bala Bala”
Or
Follow the instructions in the week2’s tutorial worksheet to do these with visual studio
code. Note it is important to write a meaningful commit message so that you can
know what changes you submit.
7. Push your code to the submission git repo with:
git push contest_server
8. Click the “Evaluate my codes” button on the contest website. Then you can see the
“Evaluator Status” change to “queuing”.
9. Wait for “Evaluator Status” change to “running”, and finally “idle” again.
Q&A
1. How can I know my submission history?
Click the “My submission” button on the contest website.
2. What if the submission history shows a submission failed?
Read the error message if have. If you can’t judge what’s the issue, write an email to
FIT5222 Flatland Challenge Submission Instruction
[email protected] or post a thread in ED discussion. I’ll run your submission
manually to find out the issue.
3. How can I identify what I submit in each submission?
Read the “commit info” (last column) in the submission history.
4. What if I forget my contest website password?
Write an email to [email protected] or post on ED discussion. We will reset a
password for you.
5. What if my submission failed and the error message shows
“ResolvePackageNotFound”?
Remove all not found packages from environment.yml manually (remember to stage,
commit and push after the change) and submit again.
6. What if my algorithm failed to find a solution?
Use debug mode and visualizer. Find out exactly which agent failed to find a path
and think about why?
* All instances guarantee that for any agent, there exists a path without traversing
other agent’s start location or goal location.

欢迎咨询51作业君