November 27th, biweekly GROMACS developer meeting

Dear all,

Next GROMACS developer meeting will be Wednesday, November 27, 2024 4:00 PM on zoom.

We usually start with a brief update from Berk and Magnus followed by questions and discussion points by everybody. If there are any specific topics you wish to discuss, just answer to this post. So, everybody else interested can join and contribute to the discussion. :)

When 2024-11-27 at 17:00 CET

Where: Join our Zoom Meeting (magic link)

Meeting ID: 692 7708 9234
Password: gmxdevs

Join by SIP:
69277089234@zoom.nordu.net

See you next Wednesday!

I’m afraid I can’t join the meeting today.

Neither can I. Alessandra and Andrey will be present.

A kind remind. Today biweekly GROMACS developer meeting at 17:00 CET on zoom.
Among other topics, today we will discuss a new format for the quartely planning meeting. Note next quarterly meeting is next week.

Where:
Join our Zoom Meeting (magic link)

Meeting ID: 692 7708 9234
Password: gmxdevs

See you later
Alessandra

Attendees: @Golui, @al42and, @avilla, @dmorozov, @lmullender, @pbauer, @vedran.

Minutes:

  • @avilla presented the plan for the quarterly planning meeting (5-7 minutes presentations + discussion instead of a shared text list) and asked for feedback.

    • For @pbauer it could be legally problematic to share slides, but text is ok. He will investigate further internally what can be done.
    • @lmullender likes new format.
    • @Golui suggested to additionally discuss open issues so that core developers can communicate which pressing tasks (e.g., tabulated potential and a recent correctness issue) external developers can help with; @avilla agreed in general, but noted that intersects a bit with other meetings.
    • @dmorozov suggested organizing a proper conference twice year, with a program etc. @avilla agrees in principle, but not possible to do it for the next meeting.
    • @vedran remarked that presentation can be in any format, so the new format should not change things much.
  • @vedran raised the point of running physical validation weekly. Discussion with @pbauer and @al42and: weekly builds disabled now, but should be easy to being back; weekly Sat/Sun night is okay, better than monthly; start with one configuration to avoid overwhelming CI, add more later if resources allow. @pbauer will add a weekly job back once @vedran says the job script is ready.

    • Additionally, @Golui raised the point of which configurations are tested. @al42and and @pbauer: FP64 and GPU builds are not compatible with physical validation tests; they are only tested via regression testing.
  • @avilla asked opinions about using AI tools to write a transcript of quarterly planning meeting. No objections raised; Zoom AI seems to be an ok choice.

  • @pbauer and @vedran discussed HIP branch performance and their benchmarking efforts.

Persons mentioned here: please contact me if I incorrectly captured your opinion.

1 Like