You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QMCPACK office hours are a new monthly meeting to support current and potential users and developers of QMCPACK and Quantum Monte Carlo methods. Attendees of all experience levels and at all career stages are welcome. All topics are “on the table”: fundamentals of QMC, installation issues, questions on the roadmap, requests for help or advice, tutorials, etc..
The office hours will evolve based on feedback received during the meetings and via e.g. comments on this issue or by email. We currently intend to alternate between afternoon and morning times to allow for widest possible attendance. Let us know what would work for you. e.g. We are considering holding the "afternoon" meeting later to make it a little more practical for people to join from Japan.
QMCPACK office hours are a new monthly meeting to support current and potential users and developers of QMCPACK and Quantum Monte Carlo methods. Attendees of all experience levels and at all career stages are welcome. All topics are “on the table”: fundamentals of QMC, installation issues, questions on the roadmap, requests for help or advice, tutorials, etc..
The office hours will evolve based on feedback received during the meetings and via e.g. comments on this issue or by email. We currently intend to alternate between afternoon and morning times to allow for widest possible attendance. Let us know what would work for you. e.g. We are considering holding the "afternoon" meeting later to make it a little more practical for people to join from Japan.
The next meeting will be on
Thursday 27th March 2025 at 3pm EST. Countdown at timeanddate.com
Connection info:
Microsoft Teams
Join the meeting now
Meeting ID: 278 034 876 614
Passcode: 6ff7oA7J
Previous meeting: #5289
Next meeting: April 27th, 10am EST
An new issue will be posted with connection information for the next meeting shortly after this one.
The text was updated successfully, but these errors were encountered: