Timeline for AI In 2048 Game, Calculations so slow
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 6, 2023 at 13:15 | history | suggested | Spitz | Added the performance tag | |
| Jun 5, 2023 at 8:28 | review | Suggested edits | |||
| S Jun 6, 2023 at 13:15 | |||||
| Feb 13, 2020 at 8:44 | comment | added | Graipher | @Vicrobot: Please update your question in that case. Since you have not received any answer yet, you can freely do so. At the moment it is unclear which of your three solutions should be reviewed, or should all of them be reviewed? I would suggest to pick one (maybe the most vanilla one, or maybe the fastest) and ask about that. You can ask about the other approaches in separate questions (maybe a day or so later in order to incorporate any generically applicable advice you might receive). | |
| Feb 12, 2020 at 14:50 | comment | added | Vicrobot | @uli Question isn't changing. I am just posting improvements in my algorithm so that answerer could help me in better way. The problem is same as it was in start. | |
| Feb 12, 2020 at 8:18 | comment | added | uli | You really need to profile your program. That's the only sane way to find out where it spends its time. Asking a changing question here is IMHO the wrong approach to this. | |
| Feb 12, 2020 at 8:09 | answer | added | RootTwo | timeline score: 2 | |
| Feb 11, 2020 at 20:48 | history | edited | Vicrobot | CC BY-SA 4.0 | added 6740 characters in body |
| Feb 11, 2020 at 11:01 | history | edited | Vicrobot | CC BY-SA 4.0 | added 2 characters in body |
| Feb 10, 2020 at 18:23 | history | edited | Vicrobot | CC BY-SA 4.0 | added 56 characters in body |
| Feb 10, 2020 at 15:20 | history | edited | Vicrobot | CC BY-SA 4.0 | added 4 characters in body |
| Feb 10, 2020 at 11:30 | history | edited | Vicrobot | CC BY-SA 4.0 | deleted 47 characters in body |
| Feb 10, 2020 at 11:19 | history | edited | Vicrobot | CC BY-SA 4.0 | improved version of isvalid |
| Feb 10, 2020 at 9:25 | comment | added | Vicrobot | @Brian Hi, please review my edit, if you've got a minute or so. | |
| Feb 10, 2020 at 9:22 | history | edited | Vicrobot | CC BY-SA 4.0 | added 1344 characters in body |
| Feb 9, 2020 at 23:46 | comment | added | Vicrobot | @DavidK I separated each move's function. Still slow. | |
| Feb 9, 2020 at 23:46 | history | edited | Vicrobot | CC BY-SA 4.0 | added 1423 characters in body |
| Feb 9, 2020 at 21:45 | comment | added | David K | The Javascript version looks a lot different than yours, and not just because of the different language. In that version there is a set of "prototype vectors" to deal with the different move directions; in yours you apparently do all kinds of transformations on the entire array to set it up for just a single move. | |
| Feb 9, 2020 at 18:14 | comment | added | Vicrobot | @Brian Its sure that its all because of the game trials in each move. It needs optimization is all i know. The post i linked has js version of that algorithm, this is the link for that js version github.com/ronzil/2048-AI. I did see the code and saw that its roughly doing same stuff in ai.js. I think its python's slowness, but since i can't shift to other language, thus trying to see if optimization is possible. | |
| Feb 9, 2020 at 18:01 | comment | added | Brian61354270 | Not the downvoter, but have you done any profiling to determine what precisely is slowing you code down? | |
| Feb 9, 2020 at 17:36 | history | edited | Vicrobot | CC BY-SA 4.0 | added 1609 characters in body |
| Feb 9, 2020 at 16:45 | review | Close votes | |||
| Feb 14, 2020 at 13:14 | |||||
| Feb 9, 2020 at 16:30 | review | First posts | |||
| Feb 9, 2020 at 17:12 | |||||
| Feb 9, 2020 at 16:28 | history | asked | Vicrobot | CC BY-SA 4.0 |