Weekly Standup (2026-06-22) #135

Activity

1. github-actions

   added

   Weekly StandupWeekly standup to coordinate stdlib activities and development.Weekly standup to coordinate stdlib activities and development.

   on Jun 22, 2026
2. github-actions

   assigned

   anandkaranubc

   ,

   batpigandme

   ,

   gururaj1512

   ,

   headlessNode

   ,

   kgryte

   ,

   Neerajpathak07

   and

   Planeshifter

   on Jun 22, 2026
3. MeKaustubh07 commented on Jun 22, 2026

   

   MeKaustubh07

   on Jun 22, 2026

   Member

   More actions

   ✅ Updates from last week

   • I worked on and opened 6 PRs adding ndarray wrappers for packed symmetric BLAS Level 2 routines, including dspmv, sspmv, dspr, sspr, and related packages.

   🕵️ Pull requests I reviewed

   • None this week.

   🧑‍🎓 One thing I learned last week

   • I gained a much better understanding of packed symmetric matrix storage and how an N * N symmetric matrix is represented as a 1D array of length N*(N+1)/2.

   🔭 My plan for the current week

   • Add ndarray wrappers for triangular matrix operations (e.g., dtrmv, dtrsv, and related routines).
   • Continue adding ndarray wrappers for Level 3 BLAS routines involving matrix-matrix operations (e.g., dgemm).
   • Add complex-precision counterparts for the remaining Level 2 and Level 3 BLAS ndarray wrappers.

   🙏 Challenges that I’ve faced and things I’d like help with

   • @kgryte Just a friendly reminder regarding the matrix constructor.

   🏝️ My availability for next week

   • I will be available throughout the week.

   💬 Important items for discussion

   • discussion regarding the infrastructure plan for the top-level blas/* API.
4. prajjwalbajpai commented on Jun 22, 2026

   

   prajjwalbajpai

   on Jun 22, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @kgryte for reviewing the PR for dlarft routine. I will work on the suggested changes and many of them are applicable for the dlabrd routine's PR as well.
   • @aayush0325 for helping me through many small issues I faced during the week.

   ✅ Updates from last week

   • I worked on the dlarft routine, and the dlabrd routine.

   🕵️ Pull requests I reviewed

   None

   🧑🎓 One thing I learned last week

   • I delved deeper into the error accumulation problem for higher level LAPACK routine, and realised that it highly depends on the nature of operation that particular routine and it dependencies have.

   🔭 My plan for the current week

   • I plan on working on the dgebd2 and the dlasq3 routine.

   🙏 Challenges that I've faced and things I'd like help with

   • I had a hard time figuring out how to fix the error in the dtrmm implementation. Posted the same on zulip.

   🏝️ My availability for next week

   • I'll be available the whole week.

   💬 Important items for discussion

   • I would love to hear @kgryte's thoughts on the dtrmm issue I faced while working on the dlarft routine. Link to the Zulip thread (#blas-lapack > dtrmm).
5. Sachinn-64 commented on Jun 22, 2026

   

   Sachinn-64

   on Jun 22, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @gururaj1512 for reviewing the pr's and clearing my doubts.

   ✅ Updates from last week

   • I worked on feat: add plot/vega/base/stroke-joins stdlib#12987, feat: add plot/vega/base/assert/is-stroke-join stdlib#12988, addressed review feedback and refactored the PRs, and completed the initial implementation of the general mark properties.

   🕵️ Pull requests I reviewed

   • I reviewed and provided feedback on the following PRs:

     • None

   🧑🎓 One thing I learned last week

   • I learned about properly managing child EventEmitter arrays by removing change listeners from old arrays and adding them to new ones to prevent stale listener leaks.

   🔭 My plan for the current week

   • I plan on working on completing the General Mark Properties, refactoring the reviewed pr's.

   🙏 Challenges that I've faced and things I'd like help with

   • I had a hard time figuring out how to implement the setter for handling an array of fields, which was then guided by the mentor

   🏝️ My availability for next week

   • I'll be off from 23/06/2026 to 29/06/2026.

   💬 Important items for discussion
   None
6. iampratik13 commented on Jun 22, 2026

   

   iampratik13

   on Jun 22, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • Thanks to @kgryte for the detailed PR reviews and feedback.
   • Thanks to @anandkaranubc for reviewing my PRs and for the helpful discussions during our 1:1 meetings.

   ✅ Updates from last week

   • I worked on dlaqsp, dlanst, dlagtm

   🕵️ Pull requests I reviewed

   • I reviewed and provided feedback on the following PRs:

   • None

   🧑🎓 One thing I learned last week

   • I gained a better understanding of how LAPACK builds complex algorithms by reusing common computational kernels.

   🔭 My plan for the current week

   • Continue implementing LAPACK auxiliary and norm routines, and address review feedback on open PRs.

   🙏 Challenges that I've faced and things I'd like help with

   • I spent time understanding dependencies between LAPACK routines to ensure I can schedule implementations efficiently. I already discussed this with Karan.

   🏝️ My availability for next week

   • I’ll be available throughout next week.

   💬 Important items for discussion

   • I wanted to give a heads-up that dtrsm and dgtts2 are dependencies for some of my upcoming LAPACK routines.
7. nakul-krishnakumar commented on Jun 23, 2026

   

   nakul-krishnakumar

   on Jun 23, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @kgryte for helping me figure out API designs.

   ✅ Updates from last week

   • I worked on ml/strided/dkmeans-distance, ml/strided/dkmeans-inertia and ml/strided/dkmeans-closest-centroids.

   🕵️ Pull requests I reviewed

   • None

   🧑🎓 One thing I learned last week

   • I learned more about custom datatypes in C.

   🔭 My plan for the current week

   • I plan on working on remaining loss functions and get started with sgd-classification

   🙏 Challenges that I've faced and things I'd like help with

   • I had a hard time figuring out API design for C implementation of dkmeans-distance

   🏝️ My availability for next week

   • I'll be available.

   💬 Important items for discussion

   • None