Just a bit over a week until they start counting votes.

This looks like a nice way of creating code documentation first pass: lmdocs: Generative AI for code documentation

Tasks

• Call Jim Donnies
• Vote! Plenty of time between the morning and afternoon meetings – done!

SBIRs

• Start looking at the trade show project. I think the first thing I’ll do is set up an overleaf project. Then create a data generator to ease back into coding
  • Underlying curve with additional horizontal and vertical weave patterns.
  • Goal is to generate at least 10,000 samples fast)
  • Calculate intersections of a straight line to points on the curve. For each point, calculate the time for iterators on the two lines to intersect. It might be possible to project this into a 2D space, since in this case the lines are functions, which means the intersection is a function, too.
  • Or maybe, just have the data generator extrapolate a straight line, calculate the intercept to that, and see if at that time, the two source lines are within a threshold. I think I like that. This should be pretty fast and generate nice data.
• Do a getting started on PyTorch 2.5.
• Train a model to predict something that supports the heat map display. I think it could simply be the distance between the points at the time of intersection with the projected line.
• 10:00 – 11:30 SimAccel review. Some nice stuff! I need to talk to Ron about using some of the (RayTune at least?) pipeline for the demo project. Because I kind of like being able to specify datasets, a range of architectures, and let it decide what the best/fastest model for learning a new trajectory/intersection dataset.
• Uploaded the proposal to the ASRC overleaf. Some last-second tweaks, so redid that.
• 3:00 Tradeshow demo tagup.