Project_01 is _live_ 🥼 👀

[cooperrc]

Links to Project_01 group repositories

We have our first project, in the video above I walk through

• joining a group
• opening the project
• (optionally) using copilot AI assistant to help with Julia coding
• adding changes to the project with a 'Pull Request'

Each group is numbered and should submit the numbered repository link in HuskyCT. Github keeps track of lines of code, pull requests, discussion posts, etc. So this gives you a record of how you're contributing to the group project. I suggest using the pull requests to discuss changes with each other and carefully design your final product.

[Afazzino2026]

My group has been debating between two interpretations of the project, does anyone have any insight? For the fast and slow speeds, we are working between the following ideas:

1. Changing the height and width to change the speed (making the pendulum speed what we are solving for)
2. Changing the angular speed to two constant but separate speeds (the angular speed is an input that we will can choose without changing)

[cooperrc]

great initial thoughts.

I don't think there will be a specific 'slow' speed that you can solve for, but what we should see is that the oscillations and equilibrium angle depend on spin speed. A slow speed could be one where small angle approximation is still true at 0-deg

[cjdipietrantonio]

Hey everyone,

I just wanted to share a tool I've found to be super helpful when working with Git for anyone whose interested! It's called GitKraken, it's free and has a ton of great capabilities. In my opinion, what makes it great is it's interactive graph of all your branches/commits for a repo, which can be super helpful when you're working in a group and multiple people are pushing changes. I also find that it has better git focused functionality than VS Code's source control.

You’ll need to make a local clone of your repo to use it, but that actually adds a nice layer of safety because you make and commit changes locally first, then push them to the remote repo.

Just wanted to drop this here for anyone who is interested. It's a nice middle ground between GitHub's web interface and the command line.

[med17018]

Hi everyone, has anyone else had trouble uploading files to their group repository for project 1? I've tried dragging a .jl file into the group repository, but I get the below error message ("uploads are disabled"). Instead, I ended up making a "fork" which then created my own personal repository. Is this what we are supposed to be doing, or should I be able to drag files into the main group repository like our professor showed in the Project 1 video?

[bp-thibodeau]

I'm having the same problem. I made a fork and started putting my stuff in there temporarily, then a pull request to merge the fork with the group repo. Seems like we don't have write/maintain access to our group repos? @cooperrc what can we do about this?

[cooperrc]

If you're not able to write into your group project, then you might not have accepted the invite to the UConn-Dynamics group. You can join discussion in #8 to look for help

[bp-thibodeau]

Would you be able to send again? the invite has expired :(

[smp21013]

How do I accept the invite?

[AuZwick]

I'm having the same issue where the invitation isn't found and in turn I cannot upload a file to the project.

[JimInput]

@cooperrc

Is there a certain format you want the pluto file to be formatted in before submitting the project in HuskyCT? Or should we just leave a link to our groups repo?

[cooperrc]

You can leave the notebook as a Pluto file in the repo. Then, submit the link to the group's repo e.g. https://github.com/UConn-Dynamics/project_01-1.git for Group-01