Made some progress!

Completed:

• Trajectory generation to bumps using compact code
• Removed trig from polar slew rate and replaced with vector math (so much cleaner)
• Fixed some axis inversion with the contorller input causing weird behavior.
• Broke bump paths unintentionally but fixed it again
• Fixed some landmark positions and zone coordinates that were incorrect
• Increased kp in heading requests to make it snappier

I am pretty surprised at the amount of things that I was about to work on and get done in this 5 hour period of time. I did a lot of testing, involving digging through past commits for direction issues and narrowing down issues with the bump stuff, and I also made sure not to ignore the small details like cleaning up old code and keeping things readable and compact.

Next:

Honestly I might take a small break from this robot. I did have a cool idea of generating PathPlanner trajectories with continuous math functions. But I might do that in another repository and move it over to this after.

Signing off,
Ash-ioL

I am sleepy so short devlog

Quick summary:

• Added AdvantageKit
• Made sure the swerve 2d simulation works
• Changed default settings in custom joystick
• Measured some things in the robot and filled in configs
• Added current and speed limit
• Fixed the deadband
• Fixed som broken config values
• (not sure if this counts) but I also spent some time figuring out whats wrong with the can loop in the hardware (not counted in the 2h)

Plans:

• Test everything on the real robot
• Maybe add a fancy auto
• Maybe add a normal controller for people to try out, and an override controller
• Idk more ideas forming

Signing off,
Ash-ioL

Progress on the time… but no progress on the code

First of all I want to be clear I spent every minute of these 4 hours working on this. I was learning in depth how commands work, and shortcuts to use them, etc. as I was coding this on the side.

Anyways now that we have that clear, back to the progress report.

So this entire time I was working on making a teleop auto generation functionality to go from bump to bump with the click of a button.

Phase 0: Programmers start at 0

This only took like 5 minutes. So I copied over a utility I made in another robot that remaps the Xbox controller readings from windows axis/buttons to macos axis/buttons. So yay! I can use my controller now.

Phase 1: Brute Force

I wrote a like a 120-200 line code (forgot), and it involved copy pasting and changing stuff each time, resulting in a unique seperate command for each zone the robot can be in.

Why this was changed: It hurt my eyes.

Phase 2: Compactifying:

So I managed to simplify those into one command that modifies the pose x y and rotation values directly and uses mirroring and stuff to really keep it as low lines and simple as possible. I was proud of this, took a lot of thinking and fixing minor tiny errors here and there.

Phase 3: Kicking out the teammate with 4000 ping

By teammate, I mean advantagescope. It turns out when I was a youngling learning to do frc code (still am ig), i accidentally installed the x64 version into my macbook instead of the arm64, so after installing the advantagescope that my cpu works better with, it fixed the 4000ping and 10fps and I got a beautiful thing actually moves more than 4 steps when I push the joystick.

Before this it took me a lot of time ot figure out that i needed to reinstall advantage scope. I tried to mess aorund with the command scheduler, have a debate with stubborn AI about how to fix this, and lets just say it took a lot of time.

Phase 4 - What… the… hail who sped up time while i was coding

So now as I am writing this I am looking at the clock expecting it to be 10am, and its currently 11:30am which is normal for some people but I do practice at 6:30am so I’m probably not gonna feel the best tomorrow but whatever. Oh and how did my code work?

THE COMMAND JUST MAKES THE ROBOT JUST STUPIDLY DRIVE STRAIGHT TO THE MIDDLE OF FUDGING NOWHERE

but yea thats a problem for tomorrow.

And sorry the repository is private for now. I’ll try to get it public when my team meeting happens.

Signing off,
Ash-ioL

Devlog 1: First “Build Successful”

At the point where I spent 90 minutes on this, we hit a nice milestone where we saw a beautiful build successful. However after this point I spend a couple more hours on this which I wasn’t able to record unfortunately. To make sure the changes aligns with the time spent, I will not be considering the changes from the lost hours in this devlog.

First attempt:

The first attempt involved reviving the 2024 code as is, but we found that this was getting us nowhere as we faced gradle issues, vendordep issues, and we wre just having a hard time to get it to work.

Solution:

I decided to start a new project all together and redo the yagsl ocnfigurations, and use the old code as a reference.

Completed:

• Build Successful
• Yagsl Configured
• Vendordeps issues gone

Future goals

• Get simulation working
• collect robot properties
• maybe prepare a nice auto
• limit speed and make kid friendly

Signing off,
Ash-ioL

THE CHANGES ARE ROLLING

To be honest I did not expect it to take this long to add a little bar that can take an input. But I guess it is how it is.

Feature #1: Date Configuration Bar!

• I spent the longest on this, and this is what most of the reviews I got wanted.
• Half the time was layout debugging and responsiveness
• It is fully functional with no known bugs, successfully updating the date with the JS code and displaying the time since that date at 12am.

Feature #2: Readability

• Someone in my reviews requested to make the note in the second page to be more readable… Well AS YOU WISH!
• There is now a clean, blurred, dark background around it.

Feature #- Oh wait… that was it…

But wait–theres more coming! (planned for tomorrow)

• Hour, minute, and second configuration for the time
• Manual control over the unit of time
• A nice showcase video
• A ship!

BUG FIXES

• This also took up a huge chunk of time
• I fixed a property in css that was causing the transitions to not work correctly
• Fixed a big that causes the page to break when reloaded

Even without the features, v2 is already turning out to be smoother, cleaner, more functional, and more responsive. I thank you reviewers for the nice detailed reviews you have given, it really helps me see my project from a different perspective. And I really do value it, which is why I am fulfilling every single suggestion.

Stay tuned for the final result tomorrow. Imma go enjoy a nice (sarcasm) 7 hours of sleep now (ugh gotta get up for practice tomorrow).

Signing off,
Ash-ioL

BRINGING IT BACK– and improving!

Hey yall,

So after my first ship, a lot of people didn’t see much usability in it other than it being a gift for my parents.

So… I couldn’t resist taking like an hour or so to create a v2 for this. So here’s the plan:

Feature #1: Usability

The background will be a more generic one, and you will be able to input your own parents’ marriage date and time to see how long they’ve been married.

Feature #2: Control

You will be able to swipe through the minutes, hours, seconds, etc. Instead of an animation playing.

Excited to bring these suggestions to life! So stay up to date!

Signing off,
Ash-ioL

COMPLETE FOR REAL

And just letting you all know, the one I showed my parents is unblurred and uses the real unix time they were married. The public one contains no personal information and is not the real time they were married for.

Sorry for lying last devlog saying it’ll be my last. But I gotta claim my 21 mins before I ship this.

What I’ve completed:

• Fixed the descriptions of the times being clipped due to overflow: hidden;
• Added text blur to the letter in the second page so that it is readable.
• Fixed a bug where the heart particles break the page by going outside the boundaries.

As I have said in my previous log, I enjoyed making this project in the last few days and I am proud of this. When I showed my parents they really liked it and it was a nice moment.

Happy wedding anniversary to my parents.

Please feel free to check it out in the deployed page: https://ash-iol.github.io/parents-marriage-clock/

Signing off,
Ash-ioL

Devlog #2 IT’S COMPLETE!

Hi everyone. If you read my last devlog you may know me as the idiot with the duck background. But I’m glad to announce that the ducks will soon be retiring as they have served their purpose.

Let me introduce my project as a quick refresher:

So this is a marriage clock, tracking the hours minutes seconds days years etc. that my parent’s have been married. And tomorrow’s their anniversary so I plan to surprise them and show it to them :).

What I have done in this session:

• A sliding animation showing the time my parents were married in 6 different units of time: years, months, days, hours, minutes, and seconds.
• Tried my best to make it aesthetic with nice fonts and color.
• Added a heart particle effect background.
• Did a lot of digging through css documentation once again
• Spent like 45 minutes screaming at a layout problem I struggled to fix.
• Did the time logic and the scaling for the units in a way that leap years don’t mess it up.
• Wrote a nice letter in the 2nd page
• Made the arrows stationary so it doesn’t look weird.

A couple super duper tiny specks to do tomorrow (around 5-10 mins hopefully):

• One last run through to check if everything’s good.
• Deploy it
• Ship it
• Most exciting part-showing my parents.

Since I have such little work to do, this will be my last devlog for this project. And I may not have been able to add every feature I wanted to like I envisioned and listed in my previous devlog, I’m glad how it turned out for the time I spent on it and I like how it is simple and also purposeful. Overall, I’m proud of how it turned out.

Check out the repo: https://github.com/Ash-ioL/parents-marriage-clock

I am gonna miss this project… sob sob. But boy am I glad I won’t have to deal with any css grid till maybe my next web project.

Signing off,
Ash-ioL

Dev Log #1: No Clock Logic YET!

A little background info…

So what I have here is a little surprise I’m preparing for my parents’ wedding anniversary. The end result–how I envision it–has a clock on the first container counting the time they’ve been married, and on the second container, it’ll have a little note and/or some kind words. Super excited to present it to them–not excited that I have to finish it by the end of tomorrow. Kinda busy tomorrow so we’ll see if I can get it done 🤞🤞.

Why are there ducks??????!?!???!!!!!!?

I know what you’re thinking: “This guy is an absolute fool for putting a picture of ducks on an anniversary gift.” Well, shame on you (in a friendly way)!

The ducks are actually a temporary background so I don’t get caught in the act of creating this by my parents when they walk by (and it indeed was a good decision because it has already saved me once).

For curious souls who want to know how the interaction went:
Dad: What’s that
Me: Umm its a duck thing
Dad: what does it do
Me: So uhh… so like you press the button and then… it tell you like how they quack. So for example these ducks quack like “fdsafas” and when you press the button now they quack like… like… that.

So yea! Pretty good interaction. Okay anyways back to devlog stuff->

What I’ve worked on:

• A lot of looking through CSS documentations
• Created the layout of everything
• Added custom font and background
• Made the page responsive for different screen sizes
• Added transitions to switch between the clock page and the notes page
• Created custom arrow navigation with hover effects

Moving forward / What’s left to do:

• Code the logic for the clock (which displays the time my parents have been married)
• Add some logic where the clock freezes and catches up (for animations)
• Add animations for big milestones (like months or years)
• Add a sliding transition for the increases
• Write the nice words in the notes section
• Add heart effects in the background
• Deploy it and PRESENT IT!

Feel free to check out the GitHub repository: https://github.com/Ash-ioL/parents-marriage-clock.
And ill be back with another update toooomoooorrrooowwwww…

Signing off,
Ash-ioL