From cbfb0ea9acc64ebebcb5b8841ccc605bae74e33d Mon Sep 17 00:00:00 2001 From: Nathan Sims Date: Wed, 23 Sep 2020 19:09:32 +1000 Subject: [PATCH 1/4] Started task 1 --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index dda25a4..df88dfd 100644 --- a/README.md +++ b/README.md @@ -28,3 +28,7 @@ Once you've completed a task make sure to push (`git push`) everything and creat Before creating a pull request remember to get the latest changes (`git pull`). This is one place where conflicts may occur (hint - this is when rebases are useful). + + +Task:1 +We are the dynamic balancing team from DeepNeuron. We are a reinforcement focused \ No newline at end of file From 5ede422366566451e644dddcc458c11b28f3e77c Mon Sep 17 00:00:00 2001 From: Nathan Sims Date: Wed, 23 Sep 2020 19:35:44 +1000 Subject: [PATCH 2/4] Brief intro complete --- .idea/.gitignore | 8 ++++++++ .idea/GitWorkshop.iml | 11 +++++++++++ .idea/inspectionProfiles/Project_Default.xml | 6 ++++++ .idea/inspectionProfiles/profiles_settings.xml | 6 ++++++ .idea/misc.xml | 4 ++++ .idea/modules.xml | 8 ++++++++ .idea/vcs.xml | 6 ++++++ README.md | 8 ++++++-- 8 files changed, 55 insertions(+), 2 deletions(-) create mode 100644 .idea/.gitignore create mode 100644 .idea/GitWorkshop.iml create mode 100644 .idea/inspectionProfiles/Project_Default.xml create mode 100644 .idea/inspectionProfiles/profiles_settings.xml create mode 100644 .idea/misc.xml create mode 100644 .idea/modules.xml create mode 100644 .idea/vcs.xml diff --git a/.idea/.gitignore b/.idea/.gitignore new file mode 100644 index 0000000..aa8b6af --- /dev/null +++ b/.idea/.gitignore @@ -0,0 +1,8 @@ +# Default ignored files +/shelf/ +/workspace.xml +# Datasource local storage ignored files +/../../../../../../../:\UNI\2020\DeepNeuron\GitWorkshop\GitWorkshop\.idea/dataSources/ +/dataSources.local.xml +# Editor-based HTTP Client requests +/httpRequests/ diff --git a/.idea/GitWorkshop.iml b/.idea/GitWorkshop.iml new file mode 100644 index 0000000..c821916 --- /dev/null +++ b/.idea/GitWorkshop.iml @@ -0,0 +1,11 @@ + + + + + + + + + + \ No newline at end of file diff --git a/.idea/inspectionProfiles/Project_Default.xml b/.idea/inspectionProfiles/Project_Default.xml new file mode 100644 index 0000000..03d9549 --- /dev/null +++ b/.idea/inspectionProfiles/Project_Default.xml @@ -0,0 +1,6 @@ + + + + \ No newline at end of file diff --git a/.idea/inspectionProfiles/profiles_settings.xml b/.idea/inspectionProfiles/profiles_settings.xml new file mode 100644 index 0000000..105ce2d --- /dev/null +++ b/.idea/inspectionProfiles/profiles_settings.xml @@ -0,0 +1,6 @@ + + + + \ No newline at end of file diff --git a/.idea/misc.xml b/.idea/misc.xml new file mode 100644 index 0000000..a891b7d --- /dev/null +++ b/.idea/misc.xml @@ -0,0 +1,4 @@ + + + + \ No newline at end of file diff --git a/.idea/modules.xml b/.idea/modules.xml new file mode 100644 index 0000000..82ae704 --- /dev/null +++ b/.idea/modules.xml @@ -0,0 +1,8 @@ + + + + + + + + \ No newline at end of file diff --git a/.idea/vcs.xml b/.idea/vcs.xml new file mode 100644 index 0000000..94a25f7 --- /dev/null +++ b/.idea/vcs.xml @@ -0,0 +1,6 @@ + + + + + + \ No newline at end of file diff --git a/README.md b/README.md index df88dfd..a1b3995 100644 --- a/README.md +++ b/README.md @@ -30,5 +30,9 @@ Before creating a pull request remember to get the latest changes (`git pull`). This is one place where conflicts may occur (hint - this is when rebases are useful). -Task:1 -We are the dynamic balancing team from DeepNeuron. We are a reinforcement focused \ No newline at end of file +Who are we +We are the dynamic balancing team from DeepNeuron. We are a reinforcement learning focused group working towards the end goal of +having an AI dynamically balanced to always provide a reasonable challenge to the player. Going forward this could be implemented by +game developers to help keep players engaged in the growing games market with a perfect challenge provided. + + From 711e7cb1d5391559fbf1d90af82ac83966e379bb Mon Sep 17 00:00:00 2001 From: Nathan Sims Date: Wed, 23 Sep 2020 19:54:58 +1000 Subject: [PATCH 3/4] added a second section on what we do --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a1b3995..c863d38 100644 --- a/README.md +++ b/README.md @@ -30,9 +30,14 @@ Before creating a pull request remember to get the latest changes (`git pull`). This is one place where conflicts may occur (hint - this is when rebases are useful). -Who are we +#Who are we We are the dynamic balancing team from DeepNeuron. We are a reinforcement learning focused group working towards the end goal of having an AI dynamically balanced to always provide a reasonable challenge to the player. Going forward this could be implemented by game developers to help keep players engaged in the growing games market with a perfect challenge provided. +#Moar details. +This semester we are working our way up through reinforcement learning algorithms with Gym enviroments. We have implented a DQN to solve cartpole +before moving on to ATARI games and building up to a DDQN algorithm. When moving to ATARI we increased our networks by introducing CNN layers to +extract features out of the screen. Moving forward we intend on developing actor critic and then PPO networks. Once these algorithms have been explored +and our agent can kick ass we will return to the goal of dynamic balancing. From 8317559edf321b3a0bac5800b8e9e1cd3ccfb99c Mon Sep 17 00:00:00 2001 From: Nathan Sims Date: Wed, 23 Sep 2020 20:02:01 +1000 Subject: [PATCH 4/4] whats happening --- README.md | 30 ------------------------------ 1 file changed, 30 deletions(-) diff --git a/README.md b/README.md index c863d38..25b371d 100644 --- a/README.md +++ b/README.md @@ -1,33 +1,3 @@ -# Git Workshop Exercise -In this exercise your team will create a mini-website (with simple markdown pages) documenting your project. -There are several tasks to complete (listed as `GitLab Issues`), but take these with a pinch of salt. -The questions should get you thinking about positive open-source documentation, but the priority here is to **practice conflict resolution with Git**. - -To complete the exercises you'll just need to edit markdown files (end with a `.md`) with any text-editor. -The `#`'s are for headings (more `#` means smaller). -Wrap text in `*` for italics or `**` for bold and `\`` for code-blocks (`\`\`\`` for multi-line code blocks). - -Think very carefully about your actions (creating files, editing files, where you create a branch from...) and discuss any doubts/questions with your teammates. -If you stay conscious of what you're doing, you'll quickly become a Git lean mean machine! -Please **work on merging and fixing conflicts together** where possible. -Note that it may be useful to use a visual UI to show what changes have been made (VScode is a great choice). - -# Setup and Workflow -Sart by forking and cloning this repository (`git clone YOUR_REPO_LINK`). -There will be a fork button near the top right hand side of the screen (left of the blue clone button). -**Only one person per-team should do this** (you can share screen with everyone else so they know how too though)! -Once you've got your own GitLab repository clone it (hitting the clone button and then HTTPS will give you the URL) to use in `git clone REPO_LINK`. - -Once everyone knows what task they'll start with create a feature branch to work in (`git checkout -b some-feature-branch`, but use a meaningful name which doesn't include the words feature branch). -Although it won't be immidiately useful, do recall that you by default branch from your current (**not `master`**) branch. - -> Remember, each task should be completed in a new branch! - -You should gradually commit (`git commit -m "ADDED COOL THING/CHANGED BLAH BLAH BLAH"`) your changes. -Once you've completed a task make sure to push (`git push`) everything and create a pull request (through the website). - -Before creating a pull request remember to get the latest changes (`git pull`). -This is one place where conflicts may occur (hint - this is when rebases are useful). #Who are we