Hello, here to help!

[nrbgt]

Hello @nesarasr! 👋

I'm the GTRI "faculty" 🤓 that is helping out on the @smileey's Small Bets program.

I can help out with any stuff related to defining and maintaining environments, code review, etc. Feel free to make new issues, or just comment here!

Down the road, once you are comfortable with this work, I'd love to be able to

• integrate it into https://github.com/gt-coar/gt-coar-lab
• make an interactive demo of your work with https://mybinder.org

Good Luck! ✨

[nesarasr]

Hey @nrbgt ! Thanks a lot
I have uploaded most of my codes here on this repo. I am still in the process of editing them, and I'd love to hear your feedback and suggestions on how I can improve my codes to be more readable and user-friendly.
Thanks again,

[nrbgt]

Cool!

It'll be a bit before I can do a deep dive on your notebooks, but some first things that jump out at me:

• you've got a couple __pycache__ folders: they don't hurt anything, but they also don't help readability/reproducibility/reusability.

I recommend creating and checking in a .gitignore file like so:

.ipynb_checkpoints/
__pycache__/

and then forcibly removing those offending files from the repo.

This will hide them from git so they don't show up in the UI, searches, etc.

Hooray notebooks! A quick scan reveals you have some markdown, and some nice output plots. Good show! I recommend adding links, with a short description, to each of them in your README.md.

Organizing and managing code in notebooks present a few special problems (I'm a Jupyter core contributor, so I've heard ALL ABOUT IT from EVERYONE). I can recommend importnb (disclaimer: co-author) which might allow you to reuse components of your notebooks. This also helps ensure that they are "restart and run all"able.

To keep yourself honest, I also recommend building up a minimal environment.yml which captures all your dependencies. I can help with this. While the repo is private, it won't make much of a difference, but if you were to make it public, it would be enough for someone to be able to try out your code on binder without spending the time to get a working environment.

Good luck! Will revisit more thoroughly soon...