Hi everyone,
I was just going through the repo to slowly start understanding at a deeper level the applications of ML to problems in string theory. Came across this work during a talk at EuroStrings 2022 but I'm getting around to actually playing with the code only now.
I notice that all tasks (and issues) are currently handled by using TODO flags in comments. While most good IDEs like VSCode handle it pretty well, I believe it's better to track these using issues on GitHub. It would open the repo up to contributions from other people without having to dive into the code. Would the contributors be okay with me doing that?
It's a fairly low intensity task and there's quite a few third-party utilities out there that automatically handle that.
Cheers!
Hi everyone,
I was just going through the repo to slowly start understanding at a deeper level the applications of ML to problems in string theory. Came across this work during a talk at EuroStrings 2022 but I'm getting around to actually playing with the code only now.
I notice that all tasks (and issues) are currently handled by using TODO flags in comments. While most good IDEs like VSCode handle it pretty well, I believe it's better to track these using issues on GitHub. It would open the repo up to contributions from other people without having to dive into the code. Would the contributors be okay with me doing that?
It's a fairly low intensity task and there's quite a few third-party utilities out there that automatically handle that.
Cheers!