Skip to content

Project Meeting Minutes

Jump to bottom
Chris Fonnesbeck edited this page Jun 4, 2024 · 37 revisions

Held on the 1st Friday of each month, 10Eastern/15GMT/16Europe

May 2024

No meeting

April 5, 2024 (14:00 UTC)

Attendees

  • Chris F., Thomas W., Ricardo V., Oriol A.

Agenda

  1. Google Summer of Code 2024
    1. Submitted projects
  2. PyData London 2024 Hackathon
  3. Roadmap
  4. Development Updates

November 3, 2023 (14:00 UTC)

Attendees

  • Chris, Thomas, Christian, Alex, Fernando

Agenda

  1. CZI grant update
    1. Applications due Dec. 5
  2. November Docathon (Nov. 17)
  3. Development Updates
  4. Remove stuff from Root namespace: https://github.com/pymc-devs/pymc/pull/6973
  5. PyMCon Updates

October 2023

No meeting

September 1, 2023 (14:00 UTC)

Agenda

  1. POSE grant update
  2. Development Updates
    1. Do/Observe (we can discuss as much as you want)
  3. NumFOCUS resubmission
    1. Deadline Sept 8
  4. GSoC Wrapup
    1. Should we do an internal presentation?
  5. PyMCon Updates

August 4th, 2023 (14:00 UTC)

Agenda

  1. POSE grant update
  2. Development Updates
  3. Numfocus grants?
  4. GSoC Project Home Stretch
  5. PyMCon Updates

July 7th, 2023 (14:00 UTC)

Attendees

  • Christian, Ricardo, Thomas, Oriol and Larry

Agenda

  1. NSF grant
    1. Grant for something like Numfocus, but we already have it
    2. Community building events
    3. Partnerships with companies and other OSS (scipy/ stan/ arviz)
    4. Can’t be used for paying developers
      1. But maybe hackathons / sprints
      2. Documentation writing / maintenance
      3. Community manager / social media person
    5. Production / Commercial applications
      1. Running on cloud platforms
  2. Development Updates
    1. 5.6.0 is out!🎉
    2. multivariate imputation (includes timeseries)
    3. do/observe operator in pymc-experimental
      1. Hopefully merged in 1-2 months
      2. Gotta fix some other things and make sure the base functionality FunctionGraph is robust and flexible enough
    4. PyTensor blockwise almost ready → Vectorization of Pytensor grahs and arbitrarily batched multivariate distributions
  3. GSoC Project Updates
  4. Numfocus grants for the rejected GSoC projects
  5. Userbase is growing as seen by PyPI downloads, GH Stars and questions on Discourse
    1. Interest in JAX
    2. Should integrate more with BlackJax inference algorithms
  6. PyMCon Updates
    1. Big thanks for Purna for generating so much excitement
    2. August event will be a CFP workshop hosted by Ravin
    3. September likely causal inference, hosted by Thomas and Ben (who need to confirm)
    4. Some discussion of an end-of-year review of 2023 PyMCon events

May 5th, 2023 (14:00 UTC)

Agenda

  1. Development updates
  2. GSoC Projects
    1. Support for unselected projects
  3. PyMCon is going strong
    1. May event is being planned
  4. Argentina Bayesian Meetup
    1. Around August 1st through 3rd in Buenos Aires
    2. Bayesian Conference in Santiago Del Estero 4th and 5th
    3. Osvaldo, Tomas, Ravin, Oriol, Alex confirmed attendance. Anyone welcome

April 7th, 2023 (14:00 UTC)

Agenda

  1. “Friction points” when using PyMC (e.g., installation), particularly in production environments
  2. PyMCon reviews
  3. GSoC Projects
    1. Review
    2. Slot requests

Mar 3rd, 2023 (14:00 UTC)

Agenda

  1. Development updates
    1. Release of PYMC
  2. Add a new sampler
    1. https://github.com/symeneses/SBM/blob/main/notebooks/template.ipynb
    2. Need to market the nutpie sampler
    3. All contained within pm sample
  3. PyTensor fixes jax implementation of scan
  4. Add computational speedup dock
    1. https://colab.research.google.com/drive/1gYEAJvjR4Gs5X3alc1JE6liCguXzrH2u?usp=sharing&authuser=6
  5. PyMCon Web Series
    1. Ricardo
    2. Advertise GSOC during PyMCon
  6. Tracebackend
    1. It happened!
    2. Replaced multitrace
  7. PyTensor
    1. Encourage
    2. No Pytensor users
  8. Do like the Aesara devs are in twitter
    1. Here’s a new contributor
    2. We could get more exposure
    3. Celebrating new PRs
    4. New core members
    5. More publicity to the development efforts
    6. Ask Fernando about marketing
  9. Communications Repo for social media
    1. Coordinating and a structure has to be setup
    2. Create repo

Feb 3rd, 2023 (14:00 UTC)

Attendees

  • Ravin, Michael, Virgile, Fernando, Reshama, Oriol, Larry

Agenda

  1. Move meeting to PyMC Dev
    1. Delete [email protected]
  2. Tracebackend
    1. McBackend may replace
    2. Looking for reviewers trace backend
  3. Colab on PyMC v4; need to move to v5
  4. GSoC
    1. GSoC 2023 projects · pymc-devs/pymc Wiki · GitHub
    2. New contributor activity on GitHub: reviewers needed
    3. Speed up merge time for first time contributors
  5. Blog on PyMC: Chris F 2020 keynote
  6. PyMCon Web Series
    1. Rolling CFP
    2. https://github.com/pymc-devs/pymcon_web_series/tree/main/docs/events
    3. First event is live. Go check it out https://discourse.pymc.io/t/pymcon-web-series-the-power-of-bayes-in-industry-your-business-model-is-your-data-generating-process-feb-9-2023/11264
    4. Discourse announcements
      1. About the Announcements category - Announcements - PyMC Discourse

January 6, 2023 (14:00 UTC)

Attendees

  • Ravin, Adrian, Reshma, Thomas, Larry, Austin, Ricardo, Danh, Chris Notes Taken By
  • Chris

Agenda

  1. PyMCon
    1. First set of mentors and mentees paired!
    2. Events are being developed
  2. PyTensor
  3. Development Updates
    1. Nutpie

Minutes

  • PyMCOn
    • CFP is underway; first events have dates
    • Pairing entries with mentors has begun
    • Call next week for mentors
  • PyTensor
    • Numba
      • Missing Ops
      • Optimization
      • random number generators
    • Perhaps have dev branch (“staging”) where nutpie is the default sampler, so that we can find the issues easily
  • Nutpie
    • would be nice to have nutpie interoperate with Python samplers (https://github.com/pymc-devs/nutpie/issues/32)
    • one bottleneck is writing to trace backend
      • hopefully McBackend will help with this(?)
    • use of float32 should be relatively straightforward; requires some knowledge of Rust
    • include benchmarks in PyMC paper

December 2, 2022

Attendees

Oriol AP, Thomas W, Michael O, Rob Z, Christian L, Rowan S, Reshama S, Ravin K, Larry S, Ricardo V, Alex A

Notes Taken By

Rowan

Agenda

  1. PyMCon
    1. We got 13 submissions!
    2. We need mentors
    3. Next Steps
      1. Review proposals
      2. Determine how many mentors we have
      3. Pair the two
      4. Start working with each candidate
      5. Run our first event Late Jan/Early Feb
    4. In next couple of weeks we’ll review, submit feedback, and pick the accepted talks 1.
  2. PyTensor
    1. What should we do with AePPL?
    2. We can make it a git submodule but this isnt great
      1. Advantage is we don’t need to maintain a second codebase
      2. Disadvantage is working with git submodules is its confusing for first time maintainers
    3. Agreed single commit for user and maintainer reasons
    4. Ravin to talk Junpeng
  3. Development Updates
    1. Vote on Ricardos poll for the next session
    2. Switch to pytensor on dependency, Michael can do hfind and replace
  4. NumFOCUS CDR interim report

Minutes

  1. PyMCon

    1. 13 submissions!
      1. 7 people volunteered to review
      2. Try to make decisions by Wednesday, Dec 7
      3. Form is still open - Christian will reach out to late submitters and explain timing
      4. Eventually move to rolling submissions
    2. Need mentors i. Hopefully 4-5 mentors to work for next quarter ii. Mentors to encourage creativity from speakers iii. For this cycle - Mentorship role in development
    3. Next steps
      1. Please review!
      2. Please reach out if you want to mentor!
    4. In next couple of weeks we’ll review, submit feedback, and pick the accepted talks
    5. Sponsorship
      1. Conference will be helpful for sponsors
      2. Advertise Sponorship - Fernando
      3. Reshama & Thomas - Sponsorship Prospectus

  2. Aesara Fork / PyTensor

    1. What should we do with AePPL?
      1. As a submodule
        1. Pros: independent git histories, no maintenance overhead of making releases, technically most elegant solution
        2. Cons: confusing to clone and pull repos that contain git submods, high barrier for 1st time contributors
    2. Agreed on single commit for user and maintainer reasons

  3. Development updates

    1. Vote on Ricardo’s poll for the next session
    2. Switch to pytensor on dependency

  4. NumFOCUS CDR interim report

    1. Contributor diversity and retention
    2. Report is out

November 4th, 2022 (14:00 UTC)

Attendees

Christopher Fonnesbeck, Bill Engels, Christian Luhmann, Fernando Irarrazaval, Junpeng Lao, Larry, Michael Osthege, Ravin Kumar, Ricardo Vieira, Thomas Wiecki, Virgile Andreani, Rowan Schaefer

Notes Taken By

Rowan

Agenda

  1. Aesara Fork
    • Communication
    • Project organization
  2. Development Updates
  3. Getting all devs on board with PyMC-experimental (please read https://smartinference.slack.com/archives/C6AKTNSBS/p1664180846362399)

Minutes

  1. Aesara Fork: Discussion
  • Ergonomic workflow + faster PRs to benefit PyMC codebase and users - Taking on development responsibility for this: interest, hours, expertise? - Adrian, Ricardo familiar with Aesara codebase - Ricardo: Suggested 1 year outlook and re-evaluation of outcomes a. Communication: - 1. Internal announcement - 2. Named vote (Monday?) - 3. External announcement b. Project organization - Organization of the fork within the project - Michael: Opened discussion on decisions re: apps and dependencies->submodules?
  1. Development Updates - Formal processes can be revised to get core developers more involved in decision making
  2. PyMC Experimental
    • Use as crazy ideas repository, or new features that will end up in pymc?
    • Can keep solid implementations around without slowing down development
    • Consider developing standards for documentation
  3. PyMCon
    • Per Ravin: Review proposals for PyMCon and share social media posts!

September 2nd 5, 2022

Agenda

  1. PyMC Development Updates
    1. Blockers?
  2. Paper
  3. PyMCon Web Series
    1. Everyone can view current progress here https://github.com/pymc-devs/pymcon_2022/
      1. Please take a look and see if you can help out
    2. Big shoutout to Purna, Christian and Fernando
    3. Each have made lots progress on the Website, Contributor Experience, and Marketing in the last month
  4. NumFocus Summit
  5. Norway Summit
    1. Start thinking about a Spring summit in Norway
    2. Good spot to talk about samplers and backends
  6. Google Summer of Code

Friday August 5, 2022

Agenda

  1. PyMC Development Updates
  2. Summer of Code 2022
    1. Status updates
  3. PyMCon 2022
  4. PyMC Trademarking

July 2022

No meeting

June 17, 2022

Agenda

  1. PyMC Development

    1. What are reasons for bumping the major version moving forward? Proposals below 👇
      1. Core API breaks (e.g. Distribution kwargs)
      2. Changes in seeding
      3. Changes in tuning
      4. …?
    2. When NOT to bump the major version?
      1. Breaks that were announced by a DeprecationWarning for >=6 months
      2. Breaks in submodules (.ode, .timeseries, .gp) that we consider part of the non-core API
      3. …?

  2. Can we get rid of manual Release Notes?

  3. pymc-examples status

  4. Size vs shape… :D

    1. 👉 keeping the status quo

  5. Summer of Code 2022

  6. PyMCon 2022

  7. PyMC Developers Summit (has the ice melted already?)

  8. Social media coordination

Friday May 6, 2022

  1. PyMC Development Updates
    1. v4 release
    2. Should we remove size from the user-facing API? https://github.com/pymc-devs/pymc/pull/5746 (size is only in the Distribution.dist() signature, not the Distribution.init signature.)
    3. pymc-examples status
  2. Summer of Code 2022
  3. PyMCon 2022
    1. Web series
  4. PyMC Developers Summit
  5. Social media coordination
  6. Are we opening our meetings to outsiders?

Friday April 1 (no joke), 2022

Agenda

  1. PyMC Development Updates
    1. Beta release
      1. No more betas, let’s move to release
    2. v4 release
      1. Just GaussianRandomWalk missing? → PR (https://github.com/pymc-devs/pymc/pull/5298) is really close to finish line. Just get it done.
      2. Deprecate EllipticalSlice step method? → Yeaah
      3. Installation issues: Upon conda create -n pmv4 "pymc==4.0.0” users should get environments that DON’T print warnings upon “import pymc”. At least on Windows this is not yet the case. Needs to be confirmed/investigated for Ubuntu+MacOS. See https://github.com/conda-forge/aesara-feedstock/issues/54
    3. PyMC-nightly broken?
      1. I’ve just created an issue
    4. PyMC-Experimental
      1. Move MLDA → Ask original contributors
      2. Are we releasing already?
      3. How are docs / tests / going on?
    5. Expecting users to be on beta?
    6. Review of pymc-examples
  2. Summer of Code 2022
    1. Candidate students
  3. Quick summary of the current CD/CI pipeline and what’s been recently optimized
    1. All new PRs should be created as a draft until they are ready for review and merge

Friday March 4th, 2022

Agenda

  1. PyMC Development Updates
    1. Beta release
    2. v4 release
      1. Missing basic time series
      2. Missing basic transition guide + changelog (see https://github.com/pymc-devs/pymc/projects/3)
    3. pymc-examples has a progress tracker: https://github.com/pymc-devs/pymc-examples/projects/1
  2. GPU testing infrastructure
    1. CZI grant funding
    2. What do we need? 👉 Tracking Issue to figure how where to buy/configure/run a GitHub Actions GPU runner.
  3. Season of Docs 2022
    1. Are we doing it?
  4. Summer of Code 2022
  5. Any thoughts on the questions posted in #PyMCon channel?
    1. How many folks want a conference?
      1. How many folks will help plan a conference?
    2. Ravin will read the notes async
  6. If there’s time: BaseTrace/MultiTrace/McBackend mini-deep dive (it’s not that hard)

Friday February 4th, 2022

Agenda

  1. PyMC v4 Codebase Deep-dive

Friday January 7th, 2022

Agenda

  1. PyMC v4 Release

    1. Think we are in pretty good shape, well
      1. Not too much as happened since first beta
      2. Release is amazing! Great job everyone
      3. Tweet has been announced with transition guide
      4. We could be good with explaining new features and make that full announcement with 4.0 release
      5. The technical release notes which have everything, we can definitely tweet more about it
      6. Something observed on twitter is whenever we tweet about version 4 or Aesara, everyone is really curious about JAX. Not being interested in writing about JAX
      7. JAX is one of the option but not the only optiona, missing elevator pitch on Aesara
      8. For the whole graph manipulation part, have not need a good quick start tutorial
      9. What do people care about? Answer for users is they’re more excited about JAX
      10. We’ve been too shy on how cool Aesara is, and by advertising more
        1. Its more unique, we went down went dynamic graph route, with control etc
        2. Static graphs has their place, here’s one that does it, and its even backend agnostic
        3. Doesn’t exist elsewhere, and a really mature tested codebase
        4. A trend that is that the tide is going back before tensorflow and pytorch
        5. Pytorch is overengineered
        6. Now people like JAX, because we associate with JAX we write that wave together
        7. Get DL crowd and more users flowing in through that
      11. Maybe need a more typical example for Aesara
        1. But it can still do a lot of that stuff, one of the popular NN architectures, or transformer
      12. Aesara is independent, so strictly speaking we still is close enough to support it
      13. Examples of Numba vs JAX PyMC, show where Numba is better than pymc
        1. Use c backend, great argument in favor of Aesara, there is not one fastest
      14. Good to spread marketing across multiple backend ideas
    2. How far along is Numba backend?
      1. The point of numba backend is to try and get to as good as C backend,
      2. C backend is very intertwined with C backend
      3. Idea with Numba is to get same base performance, but you’re writing python
      4. NUMBA is very concerned with no getting backend regression
    3. JAX Used to be very flexible, but they started making it more and more fixed shape only
      1. We do a lot of put all variables together, flatten them out, things that don’t work with JAX
      2. Now good news is Brandon is doing a big push with fixed shape tensor, once you have them with fixed variable sizes then you can compile various models to JAX
      3. Seems very promising to have JAX more flexible for things to compile to JAX
      4. More flexibility on Aesara side, to build things JAX can handle, with fixed tensor
    4. Mindful of discussion of features that are interested for 5 percent
      1. there’s also 95% of userbase where users don’t care about backend
      2. More concerned about understanding more models and domain problem where PyMC has a big userbase and JAX not so much
    5. ‘Theano died” is a common sentiment
      1. Switch messaging to Theano evovlled
    6. Emphasis flexibility

  2. What is missing for beta 2?

    1. PR for symbolic distributions, the way we want to implement time series
    2. VI at the verge of being mergeable because of some AEPPL dependency took it out of Beta 1, three test failures
    3. Existing GP stuff is all passing, so were all solid
      1. Examples are still not updated

  3. Push VI into next release

    1. We’ll release BETA 2, and push time series and VI into Beta 3
    2. We have to release using GUI in github, which create the correct pattern
    3. The pipeline kicks off, updating formatting of release notse section
    4. Bumping version number beforehand manually
    5. Conda feedback PR opened by bot, not much manual intervention is needed
    6. Manual release by pypi is made by pipeline
    7. Pin Numpy version to fix main branch in numpy compatibility
      1. Why dont we have CI failures in 1.22 in main
    8. Things that may delay more than 2 days then we don’t include in beta

  4. Porting of example NBs to v4

    1. Migration guide thats a bit more detailed than the migration guide
    2. Most notebooks can likely work if we change the imports
    3. We can try mass running them
      1. This time do one PR notebooks
    4. Three things to change
      1. Change aesara
      2. Change inf data to true (removes)
      3. Something else (Missed in notes)

  5. pymc-experimental repository

    1. Repo now exists; are there things we should move there now?

  6. Sync meetings going forward We have been having dedicated documentation meetings which I think was partially responsible for some lab meetings ending before the allocated hour. We plan on continuing with the dedicated doc meetings, should we try to organize something of the sort for dev and discourse (and pymcon?) teams? One option could be to have dedicated team meetings of 45min-1h every 1-2 months plus a monthly 30 min common meeting to coordinate and talk about no-team things like governance or grants.

Friday December 3rd, 2021

Agenda

  1. PyMC v4 Release
    1. Blockers
    2. Beta Release next week!
      1. Log p recording is broken but only really needed for az.compare
    3. Migration guide
      1. Coordinate release with Meenal for release notes
  2. PyMC Community Team
  3. Season of Docs Wrap-up
    1. Accomplished everything, except for V4
    2. Martina sticking around which we’re all excited about
    3. In the new website template there is a section of distributions to check them (link: https://pymc--5232.org.readthedocs.build/en/5232/api/distributions.html)
    4. Proposal to rewrite quick start to use physical units
      1. Current quickstart goes into benchmarking, what bayesian computation and evaluation is
  4. pymc-experimental repository
    1. Theres functionality in the main repository that is more experimental but isnt well tested because we don’t want it holding up the main release
    2. Idea is to have some parallel addon repo if you installed it would put things side by side
  5. PyMCon 2022
    1. Mid jan/ early Feb planning kickoff
    2. Virtual is fallback, but better than no conference
  6. Sync meetings going forward We have been having dedicated documentation meetings which I think was partially responsible for some lab meetings ending before the allocated hour. We plan on continuing with the dedicated doc meetings, should we try to organize something of the sort for dev and discourse (and pymcon?) teams? One option could be to have dedicated team meetings of 45min-1h every 1-2 months plus a monthly 30 min common meeting to coordinate and talk about no-team things like governance or grants.
  7. Discourse upgrade to paid plan

Friday November 5th, 2021

Agenda

Friday October 1, 2021

Agenda

  1. PyMC Renaming
    1. Outstanding issues
      1. readthedocs still seems to use pymc3
  2. Docs
    1. Forwarding to the same server
      1. Proposal: docs.pymc.io → https://pymc.readthedocs.io/ (plus making stable the default version, not latest), examples.pymc.io → https://pymc-examples.readthedocs.io (default to latest)
    2. Status update on docs projects
    3. Add page on history of PyMC → migrate from https://github.com/pymc-devs/pymc/wiki/Timeline and also include the visualization Ravin made!! (and add a forward there once the page is part of the RTD)
    4. Add a short description of PyMC4.0 (one or two paragraphs with a link to more information) on the documentation front page. Could be based on the work that Thomas and Chris are doing on blog posts and reports.
  3. PyMC v4
    1. Blockers for 4.0.0-beta1
      1. Initval framework: https://github.com/pymc-devs/pymc/pull/4983 (finish line)
      2. VI: https://github.com/pymc-devs/pymc/pull/4582 (finish line)
      3. Aeppl: https://github.com/pymc-devs/pymc/pull/4887
      4. Migration guide / Release Notes https://hackmd.io/7_BJXPrDT1ShtDMxghGfHA
      5. Updated and exhaustive api
    2. Blockers for 4.0.0-beta2
      1. Restauration of moments for most distributions & switching the default to them
      2. Rework initval/start/jitter mechanisms inside init_nuts
      3. Restoring support for the GP submodule
      4. Timeseries distributions
      5. Mixture distributions
    3. Blockers for v4.0.0 major
      1. Docs revamped to Martina’s mockup sample pages
      2. Update all beginner & quickstart pymc-examples to 4.0.0-beta2
      3. DeprecationWarnings and backports in v3.11.x release

Notes

We'll refer to the new release as PyMC4.0 in the documentation

Documentation goals: Merge all open PRs to pymc-examples this week, then creating a v3 release to trigger readthedocs to build the page for v3. Then once the beta release is out start running notebooks with it Also get the documentation-side changes we want to see in the examples in before updating them to PyMC4.0 code

Examples need to be ported to PyMC4.0 before the alpha release (maybe 1 or 2 months from now)

Update the upgrade guide, quickstart guide and put deprecation warnings.

Some notebooks will be updated before the PyMC4.0 release we need to choose which ones to update first. This can coincide with the list of examples the documentation team is planning on moving to the main repo (important/popular examples that we want to update more frequently) then work will continue for about 2 months (estimated) we can do a sprint/hackathon to speed it up

Friday September 3, 2021

Agenda

  1. PyMC3 v3 any relevant news?
    1. Release 3.11.4. Havent gotten any complaints so assuming no news is good news
    2. Considered a success 🎉
  2. Installation troubles
    1. Generally trying to push dependencies to Aesara recipes
    2. Still ongoing (probably good to fix that before v4.0.0)
    3. 👉 The fixes could be backported for v3/theano-pymc-feedstock, but we’ll discuss that in the next meeting.
  3. PyMC3 v4
    1. Blockers for beta
      1. Start/initial values
        1. 👉 We agree to revert the default behavior to the moment that was the default in v3, without allowing for choosing between different moments! @Michael O will take this on.
        2. 👉 Option to draw from the prior & API point of entry is still under discussion.
      2. Docs updates for v4
        1. 👉 Need to set up autodocs for Sphinx. @Sayam K agreed to take this on
      3. Release announcement https://hackmd.io/I5F8t9swRqKPfGQPYsR_cg
    2. Blockers for v4 major
      1. Variational inference. No hope for Normalizing flows to work in nearest future, pickling is broken
        1. try cloudpickle to fix pickling issues
        2. ADVI should work and be done soon
        3. AEVB is also problematic, probably no one is using it and we might want to deprecate
      2. DensityDist
        1. Needs API changes to make purpose of inputs in gives more transparent to the implementation. Ricardo already has a proposal in https://github.com/pymc-devs/pymc3/issues/4831 for the updated API.
        2. Needs info if it’s even compatible right now, or how difficult it is to get it working.
      3. Before we forget: Deprecating backends and other things marked as
        1. 👉 Want to add deprecation package & migrate the existing warnings. Meenal want to pick that up.
    3. Coordinated release announcement/event/materials? partially discussed above. Will re-raise later.
  4. CZI grant
    1. The EOSS grant awardees are public now: https://chanzuckerberg.com/eoss/proposals/?cycle=4
    2. What are our computing infrastructure needs for v4? Now that we have money its time to think about the specifics.
      1. Idea: Resources for CI testing installation on various OSes?
      2. Idea: Benchmarking
  5. Governance doc discussion: https://raw.githubusercontent.com/pymc-devs/pymc3/governance/GOVERNANCE.md. Key open questions:
    1. Tiers
      1. general feedback on adding/formalizing the 4 level structure: recurrent/core/council/bdfl
      2. (maybe leave for PR or future) how should we match tiers (and maybe teams too) to github permissions. i.e. triaging permissions to recurrent contribs, admin rights based on teams and/or steering council?… Also if teams should be org-wide or project-specific?
    2. Teams
      1. long term wise, once the doc team is more established, do we agree with this potential team structure?
    3. Steering council:
      1. Voting: currently the old steering council votes on the new steering council, we could change that to core contributors vote on new members/renewals
      2. Vote of no confidence: I think this is like the code of conduct, we need to have some process for core contributors to remove people from the steering council even if we hope and expect to never have to use it
      3. council membership constraints. I think we should have a minimum number of members, say 5, with at least one member per team and at most 2 institutional contributors of the same company. Or some other numbers but some kind of constraints on those ends.
    4. Joining the team
      1. becoming recurrent/core contributors works on a nomination based approach. Do we want the nominations to be public (i.e. like in ArviZ) or only public within the team/slack?
    5. Things to not talk about
      1. documentation team goals (i.e. pymc-examples based or also about resources) → we will discuss that next week in the doc meeting, come if you want to talk about that
  6. Summer internships updates
    1. Google Season of Docs
    2. Outreachy

Friday August 13, 2021

Agenda

  1. PyMC3 v3.11.3 release
    1. https://github.com/pymc-devs/pymc3/milestone/23 👉 We added a new issue #4854 to the milestone, because it’s a one-line fix and Ravin (the 3.11.3 release manager) is on vacation.
    2. What if we need to backport changes to Theano-pymc in the future? See: https://github.com/aesara-devs/aesara/issues/444#issuecomment-889648944 👉 We decided to NOT make backport fixes for Theano-pymc, because there are no automated release mechanisms. If someone needs such fixes for mission-critical production systems, they should fork, fix & deploy on their own.
  2. PyMC3 v4
    1. https://github.com/pymc-devs/pymc3/milestone/19
    2. Bound distributions: https://github.com/pymc-devs/pymc3/pull/4815/files
    3. Discussion: The codebase is morphing from OOP to functional programming, with lots of @register dispatching. Do we want to continue in that direction? What can we do to make it easier to understand/extend for new contributors? (dispatching is a rare pattern in the Python world; IDEs have a hard time making suggestions for functional programming styles, …) 👉 We agree that functional programming approaches make a lot of sense when working close to Aesara graphs, but multiple people were also concerned about codebase accessibility. To compromise we decided to attend to functional/OOP style in the developer guide and make the distinction based on “Is this related to Aesara things? Then functional if it makes sense. Otherwise prefer OOP.)” or the like.
    4. v4 timeline & communication
      1. 👉 Restoring moment-based initial values is a blocker (Ricardo, Michael)
      2. 👉 GaussianRandomWalk is a blocker
      3. 👉 Mark DensityDist, NormalMixture as “not ready, but we’re working on it” (Ricardo?)
      4. 👉 VI also “not ready, but WIP” (Max)
      5. 👉 Timeseries “not ready, API changes WIP”: We plan to use aeppl which enables us to evaluate log for any arbitrary time series, while this is an excellent option, it's still materializing so for the upcoming release we port three important distributions (ARIMA, AR and GaussianRandomWalk) based on Aesara Random Variables
  4. Summer internships updates
    1. Google Season of Docs
    2. Google Summer of Code 2021 - ARIMA tests and documentation left
    3. Outreachy
      1. going well so far. Unlike gsoc, outreachy internship can be extended if external circumstances delay the work. The project will finish on September 27th
  5. Next journal club (no papers on stack at the moment)

Friday July 2, 2021

  1. PyMC3 v3
    1. Can we cut a release now? Any last-minute notebooks or things that need to be merged? → https://github.com/pymc-devs/pymc3/milestone/23
      1. → Test failures on the v3 branch because of Scipy chisquare API change breaking some tests → Chris will fix it
      2. → https://github.com/pymc-devs/pymc3/pull/3792 Michael will take a look & either fix or close it.
    2. CI is currently red, might be a flaky test
      1. Chris to fix the Chi squared value
  2. PyMC3 v4
    1. Which blockers remain until a release? → https://github.com/pymc-devs/pymc3/milestone/19
  3. Aesara → Just mentioning that conda-forge packages are not very reliable. Some activity in the conda-forge pymc3-feedstock may hopefully improve the situation.
  4. Summer internships updates
    1. Google Season of Docs
    2. Google Summer of Code 2021
    3. Outreachy
  5. Next journal club

Friday June 4, 2021

Agenda

  1. PyMC3 v3 release
    1. Can we cut a release in June?
      1. Dont need to couple them
      2. Dont want to introduce new features to v3
      3. Cut v3.11.3
        1. Relevant milestone: https://github.com/pymc-devs/pymc3/milestones
        2. Maybe add this https://github.com/pymc-devs/pymc3/issues/4658
        3. Ravin will be release manager
  2. PyMC3/Aesara discussion
    1. Priorities
      1. Michael will rebase PR #4696 one last time (restores shape backwards compat & brings more capable dims) and then we merge it before other PRs break it again
      2. Upcoming change of how size works in Aesara - doesn’t need to delay PR #4696, but will be incoming shortly after (need to update a few tests in PyMC3)
      3. Merging v4 into master, so we can finally un-block lots of other PRs
      4. Rename of master → main
    2. …followed by
      1. Finalizing distribution refactors
      2. Documentation updates
      3. Beta Release of PyMC3 v4.0
  3. Summer internships updates
    1. Google Season of Docs
      1. Are are going to have versioned docs, if for no other reason than PyMC3 v3 final release
      2. Martina gave a great overview/plan for organizing the Docs. Could we put a link here to her spreadsheet?
    2. Google Summer of Code 2021
    3. Outreachy
  4. Next journal club (call for papers)

Friday May 7, 2021

Agenda

  1. PyMC3/Aesara discussion
    1. GLM submodule deprecation
    2. Status of v4 branch
      1. Need to resolve "Merge v4 into master” milestone blockers ASAP
    3. Timeline/roadmap
  2. Summer internships updates
    1. Google Season of Docs
      1. Review of candidates
      2. Timeline for project
      3. Switch to automated ReadTheDocs build beforehand?
    2. Google Summer of Code 2021
    3. Outreachy

Notes

  1. Aesara milestones
    1. Merge v4 into master milestone
    2. V4.1 milestone
    3. We can add labels to issue tickets to indicate which ones are blocking the above
  2. v4 update
    1. Brandons been taking a break to work on Numba
      1. Most of the operators are converted
      2. What’s been setup recently is taking the python implementations and running them in Numba without needing to map or write anything
      3. Not necessarily any speed gains, just demonstrating numba system meets all our need
      4. The C based compilation allows C and python to run together
      5. We can get rid all of the function stuff and just use NUMBA and call that within numba
      6. All things that have C implementations are going to have Numba implementations
      7. MLIR is the basis for XLA, JAX
        1. NUMBA works by compiled to llvmIR, but a specialized version that compiles ml stuff
    2. Working with Aesara PyMC combo is a bit hard
    3. v4 merge into Master planning
      1. Things blocking
        1. Integer casting issue in observations
        2. Size Shape PR
        3. After this we can merge and do an alpha release
    4. Ricardos cool work
      1. Just like we compose x+y we can compose distributions
      2. like a GRW we just take two Gaussian and just cumulative sum them together
  3. Google Season of Docs
    1. Deadline is May the 17th
    2. Go through the dropbox links

Friday April 2, 2021

Agenda

  1. PyMC3/Aesara discussion
    1. Aesara distributions - are we already feature-complete w.r.t. numpy.random dists?
      1. → Ravin will take a look
    2. Status of v4 branch
      1. New imputation mechanism was recently merged - now realized through masking instead of creating new tensors.
      2. Subtensor indexing now works for log-likelihoods - this allows, for example to do switching between different priors (like in a model comparison) using indexing. There are other ways to achieve the same mathematically, but the indexing is more elegant. (We should probably write a demo notebook for the gallery! Also this is something few other PPLs can do.)
      3. Outstanding tasks
    3. Brandon mentioned something about having to drop jax? → We don’t have to drop JAX. Some new features just won’t work with new JAX versions.
      1. https://smartinference.slack.com/archives/CCU6WGM5L/p1617310119041300
      2. Someone needs to dig into JAX and understand what’s going on below omnistaging
        1. We’re uncertain about how omnistaging affects model or which ones
        2. It might just be new dynamic indexing functionality that is affected
        3. We do want all features to be supported
        4. Current tests that are failing now seemed like by that point it should have been a constant
          1. Regardless no tests have been completely disabled at this moment
      3. Numba backend is looking promising
    4. Shape/dims/size discussion
      1. We all agree that “size” is internally the right way to thing about RV dimensionality/broadcasting.
      2. We all agree that “dims” are much more useful than “shape”.
      3. We’ll implement dedicated backwards compat. functions for the RV so we can keep supporting existing implementations
    5. DensityDist, Mixture, Bounds, Variational inference are the biggest not-yet-dealt-with things in v4
      1. For DensityDist we’ll reduce the supported API to something reasonably simple.
      2. VI internals are still broken
      3. intX problem (PR by Max) about downcasting
      4. Mixture - Brandon will probably give inputs here
    6. Branches: We want to rename master→main and merge v4→main.
    7. We’ll need a “Guide to v4” → Ricardo will work on this based on API Quickstart notebook
    8. We strongly favor building the docs with Readthedocs (it can be done) so their build is automated and we can have versioned docs. This is something we should get done before Google Season of Docs already.
  2. Summer internships updates
    1. Google Summer of Code 2021
    2. Outreachy
    3. Google Season of Docs

Friday March 5, 2021

Agenda

  1. PyMC3/Aesara discussion
    1. Project status updates
    2. Documentation, Maintenance & Bugs
  2. Summer internships updates
    1. Google Summer of Code 2021
    2. Outreachy
    3. Google Season of Docs
  3. Funding
    1. CZI “Essential Open Source Software for Science”
  4. Journal Club
    1. Next meeting, March 19

Notes

We would like to merge v4 into master so that it gets more attention, but there is concern that it would destabilize master.

Perhaps it would be a good idea to create a v3_stable branch that people could use if they need stability (and for bugfixes), then go ahead and merge v4 into master.

Do GSoC mentors have to be PyMC project devs?

Friday February 5, 2021

Agenda

  1. PyMC3/Aesara discussion
    1. Status update
      1. PyMC3 3.11.1 release
      2. Upgrade of PyMC3 backend from Theano-PyMC to Aesara
      3. RandomVariable PR
      4. We’ll switch to Semantic Versioning starting in 4.0
    2. Documentation, Maintenance & Bugs
  2. Summer internships
    1. Google Summer of Code 2021
    2. Outreachy
    3. Google Season of Docs?
  3. Funding
    1. Update on NASA/ROSES grant
  4. Journal Club
    1. Paper suggestions?

Notes

  • Will have further discussion of “how much” semantic versioning we will use
    • Marco G points out that it will mean maintaining branches for each major/minor/bugfix version
      • this adds maintainer version, but probably not contributor
    • Also a question of how long we port back bug-fixes to old versions
      • Seems like there’s a consensus that it is too much work to maintain things that are not at HEAD
      • [editor] I’m a little behind, apologies if I missed the counterpoint here
  • Doc/maint/bugs
    • Michael O may be able to run all the notebooks and ping on the stuff that is not passing for 3.11.1
  • Aesara
    • There’s a random variable PR that’s quite big. coming along pretty quickly.
    • Check out bullet points here and can start making PRs to the 4.0 branch
      • Should we make v4 the master branch?
        • Brandon says we might want to wait until “majority passes” instead of “majority fails”
        • Lots of distributions need random variable operators - pretty straightforward, but a little bit of effort.
      • How do we make sure nobody makes PRs that work on old version, but not v4?
        • Let’s definitely communicate quickly with new PRs about the changes
        • Add notice to pull request template (should @ tag someone here)
      • Question: why dispatch pattern rather than OOP?
        • [Arguably] cleaner
        • Hard to annotate nodes with methods. Can work, but it is a kludge.
          • The stuff that is carried around is in the .tag
          • Should update to use aesara’s printing subsystem for graphviz stuff
  • GSoC
    • List of ideas here
    • We should perhaps apply to Outreachy
      • GSoC is half the time of coding, so projects are smaller
      • Outreachy focuses on underrepresented groups, still 3 months
      • Costs $6500 to do Outreachy (price of 1 intern, but gives access to possibly more than 1)
      • Check (with @Chris F ) if we have the money
    • GSoD is later in the year, but good idea
      • Can create a wiki page (@Sayam K?) with ideas to add to until then
  • NASA/ROSES
    • Stan/ArviZ in on grant
    • Takes ~180 days to decide. Let’s see in November/December!
    • Is there contract negotiation?
      • NumFOCUS gets some money, and will hopefully handle haggling with NASA (in case this comes out well 😄 )
    • Ask Ravin if you want to see the grant!
  • Papers
    • Lots of people have papers almost out, but there are robots to maintain in the meantime

Friday January 8, 2021

Agenda

  1. PyMC3/aesara discussion
    1. Current Topics: Documentation, Maintenance & Bugs
      1. Documentation migration: Notebooks are now a submodule and live in /pymc-examples instead. → We should put a pointer into the Readme
        1. This is now done. README needs a bit cleanup. Marco G is working on this.
      2. MacOS performance/installation problems → We should improve our install instructions (in the Readme) and explicitly tell people to install dependencies through conda before using pip install on Theano/PyMC3
        1. Make these installation instructions clearer and adapt them to the OS: one Wiki page for each OS install and link those in the README
    2. Release Roadmap
      1. Theano-PyMC 1.1.0 (imminent)
        1. Currently, PyMC 3.10.0 only works with Theano-PyMC <= 1.0.12
        2. The PureOp and Op were renamed to Op and COp respectively, because you can have an Op which doesn’t have a C implementation —> every custom Op that someone wrote will have to now inherit from Op instead of PureOp
        3. The linkers were all moved to their module
        4. The gof module is gonna be renamed to graph → easy to migrate to though, not a lof breaking changes for users → have to continue pinning Theano-PyMC in PyMC3
      2. PyMC3 3.11.0 (depends on the above)
        1. Will be pinned to Theano-PyMC 1.1.0, while PyMC 3.10.0 will stay pinned to Theano-PyMC 1.0.12
      3. Criteria and Timing of Aesara 2.0
        1. We should define such a date soon, while continuing the refactoring of the non-public code without breaking user-facing stuff.
        2. We can continue to make major improvements like graphs rewrites in Aesara 2.1.0
        3. RandomVariable is now merged in Theano-PyMC, so we can already migrate PyMC to using them, as well as getting rid of the forward sampling code.
          1. Open issues on the PyMC3 repo to start this transition
          2. Pretty big investment, need more than 1 person doing it
          3. 100% a PyMC3 API refactor
          4. Need to replace each distribution .random method by RandomVariable, including everything that uses this machinery (i.e forward sampling methods).
            1. Can take a look at this blog post, but we probably a minimal reproducible example of this transition to kickstart developers’ work?
            2. This is actually a refactor of pm.Model and distributions’ random at the same time.
            3. Once this PR is done, it should be quite easy for people to implement the little changes that come out from this big change. → We should make this change as soon as possible, so that PyMC3 4.0.0 is the release directly following 3.11
        4. See the timeline document for more information
  2. Community Updates
    1. Collaborative Sampling Library? —> postponed to next meeting, to get people who are able to update us on that
    2. Apply to outreachy?
      1. Summary: Outreachy is a GSoC like project targeted at under represented minorities. Moreover, unlike next GSoC that has reduced the coding period to half the time it used to be, outreachy internships are still 3 months.
      2. Cost: $6500.
  3. Funding
    1. Update on NASA/ROSES grant
  4. Journal Club next Friday (2020-01-15)
    1. Paper suggestions?

Friday December 4, 2020

Agenda

  1. PyMC3/aesara discussion
    1. Development updates
      1. 3.10. release is very close
        1. need to fix the recursion problem with DensityDist (it’s a regression w.r.t. 3.9.3)
        2. more?
      2. Dev speed on Aesara is going up, with more people helping out, but we still need more.
    2. What happens after 3.10 (roadmap to 4.0.0)
      1. Shape handling done right!
      2. Changing defaults in the API
      3. InferenceData all the way - we have PRs to support it of prior/posterior predictive and so on.. 4.0.0 is the chance to make it the new default.
      4. Documentation overhaul! There’s some structure to be fixed. Getting rid of warnings, maybe moving to a new docs theme? Similarity with Aesara?
      5. Dependency on Aesara v2.0.0 - this means we should push Theano-PyMC/Aesara on a fast dev cycle to get it ready!
  2. Collaborative Sampling Library
    1. Meeting with Remi/Neeraj/Du Phan
  3. Funding
    1. NASA/ROSES grant
      1. Should https://github.com/aseyboldt/sunode be included, especially w.r.t. satellites?
  4. Journal Club next Friday

Friday November 6, 2020

Agenda

  1. PyMC3/Theano-JAX discussion
    1. Variational inference
      1. what are the implications for VI?
    2. Project organization
      1. Theano-PyMC name
        1. Two proposals for new name: Jeanet and Aesara
        2. Gonna be used for next major version (4.0), which will use new RandomVariable op (and all the nice benefits it has on dynaminc shape handling and forward sampling functions)
      2. Renaming PyMC4 work (PyMC-TFP?)
    3. Roadmap
      1. Samplers
        1. Use TFP / Numpyro / MCX jaxified samplers thanks to JAX linker → for 3.10
        2. Writing pure Theano samplers would be included in next major version, e.g 4.0
  2. Funding
    1. NASA ROSES grant
      1. Use of grant funds
      2. Writing 3-page proposal
      3. Joint submission with Stan?
        1. And Arviz
        2. Discussions already happening between ArviZ and Stan
        3. Next step: setup common discussions with ArviZ, Stan and PyMC folks
    2. Use of NumFOCUS funds for student projects
  3. Documentation
    1. Feedback from PyMCon
    2. docs.pymc.io vs. pymc3.readthedocs.io
    3. Moving notebooks out of main repository
      1. Move it to a new dedicated repo, with sub-directories for topics
    4. Build automation
  4. Release new version
  5. PyMCon: What did people think?
    1. Takeaways for next time (while we still remember them)
    2. Please fill out this retrospective if you get a chance
      1. https://docs.google.com/document/d/15DgRO3GHNiQXDMbFkXgDXI6jKnb_PtJEPiYRxyA5VsI/edit

Notes

  1. Theano
    1. Should we rename Theano PYMC?
      1. Yes
    2. Do we have people to help?
      1. Ravin will jump in
      2. Osvaldo knows some people
    3. What about the samplers?
      1. Osvaldo mentioned there may be issues
      2. Thomas says we just rely on other peoples samplers for the time being
        1. Those samples come from mcx, numpyro, and tfp
      3. Thomas said the whole thing doesn’t need to be theanofied but just parts of it
        1. The end goal is the whole sampler is theano, but that is difficult
        2. The key insight is that Theano used to think of Theano as a fixed set of ops, like lego bricks you can build certain things
        3. If you want to build a nuts sampler you can't build new pieces
        4. The key understanding is now that we own Theano we can build our own custom ops in Jax, and then assembled in that way
      4. Chris, low hanging fruit for things is to update documentation is to make it more user friendly
      5. Ravin, can we start deleting chunks of Theano?
        1. Chris: Yes, provided its modular
      6. Max: What are implications for VI?
        1. Random Ops not working for now
        2. NotImplementedError: No JAX conversion for the given Op: RandomFunction{normal}
        3. It is a blocker for VI
      7. Chris: What are things were do for 3.10
        1. Thomas: Just jax based samples that work under Jax backend
      8. Chris: Would anything break?
        1. Max: He thinks because Theano relies on buffers and stuff
        2. Also Max: my concern about shared variables is not more a concern
      9. Random Variable explainer
        1. For now, instead of random variables we have placeholders
        2. Forward sampling in PyMC3 is ridiculously complicated, RandomOps will mean we can delete the forward sampling code

Friday October 02, 2020

Agenda

  1. Theano-JAX discussion
    1. Consensus: We will focus our efforts on the new backend (currently “theano-pymc”) which has already become (on master) and will remain the backend for our library (“PyMC3”).
    2. Codebase roadmap:
      1. pymc-devs/pymc3 → this is and will remain our library
        1. current 3.9.3
        2. next 3.10.0 (will use theano-pymc as the backend)
        3. 4.0 (will use re-named backend and may have RandomVariable if it works out)
      2. pymc-devs/pymc4 → this was an experimental project that we’re not going to continue
        1. Message is that PyMC4 with TFP backend is not developed anymore — although we learned a lot with it and got great ideas — but the future is PyMC3 with the amazing, new Theano-JAX backend.
    3. Proposal: move to Theano-JAX as next PyMC backend
      1. General agreement + Theano-PyMC (because JAX doesn’t yet support Windows)
      2. We’re retaining Theano as the backend and adding JAX as compiler, which is a new feature and allows the use of new, vastly faster samplers. But current compilers (C through classic Theano) and PyMC3 samplers are still there, as well as the PyMC3 modeling API.

TABLEDProposal: Rename Theano-pymc and move to its own, repo. Instead of being a fork of Theano.

    1. jeanet? jeano? pymc-backend?
    2. Aesara? → daughter of Theano ;)
    3. Renaming: gives a clear message that this is a new Theano and that PyMC3 is not dead
    4. Not renaming: conveys continuity and avoids confusion for users
    5. Consensus for renaming, although we won’t choose the name today.
    6. Timing of the renaming? This means different entry for PyPi and different import names. Renaming will be for next major version, so that PyMC3 will always work with a backend called Theano. And then PyMC4 will run on Aesara / Jeanet, whatever name we came up with for Theano-PyMC
5. PyMC samplers → Not discussed
    1. use exclusively our own
    2. use exclusively third-party samplers
    3. have both (but with the "commitment" of developing   and improving our own
6. Variational inference → Not discussed
    1. what are the implications for VI?
7. Project organization → Not discussed
8. Follow-up tasks
    1. Prepare statement about PyMC3/PyMC4 future
    2. The roadmap on the Wiki should be updated based on the decisions above
  1. Developer meeting attendance
    1. Who is permitted to attend lab meetings?
      1. Should be open if we can → live-streams?
      2. We have the Discourse for public discussions, which will be even more important with Discourse. Update the README with link to discourse https://github.com/pymc-devs/pymc3/issues/4154
      3. The current way of waiting to observe people making consistent, useful PRs works well.
      4. The monthly meetings will remain private, insofar as they are purely useful for developers of the project and aren’t even a requirement of our project.
    2. Developing explicit criteria for (1) meetings, (2) Slack, and (3) repository access
    3. Do we need a public meeting or regular blog post to update user base?
  2. PyMCon updates
    1. Speakers announced and registration is open. Tell all your friends
    2. Really could use volunteers to help out with critical and day to day tasks
      1. Either direct volunteer help from people here or reaching out in your network for reliable people
      2. Async tasks prior to conference, day of volunteer help
      3. And abbreviated task list is here: https://docs.google.com/spreadsheets/d/1g0rQs4yxSE_ILk1d6fPlxNUmtk_sOyL0RUn1vVfjU1U/edit#gid=0
        1. Join the slack
    3. Announce, with a talk, pymc4 (the theano-pymc one)
      1. Ravin will touch on this topic during PyMC Welcome talk
    4. How will PyMCon income be used?
      1. Note from Ravin: Can we punt this to next lab meeting? Let’s make the money first before deciding how to spend it
      2. Hire one (or more) intern(s) to work on PyMC4 via outreachy
      3. setting up gpu testing for theano-pymc
      4. Ravin would like to buy tshirts or other swag for organizers

Friday September 4, 2020

Agenda

  1. PyMC3 Development Updates
    1. Increase in issues with parallel processing on different platforms: is this a coincidence or could this be a bug?
      1. Adrian suspects a bug in OpenBLAS that causes deadlocks with worker threads
      2. Models must be pickled on Windows AND OSX starting with Python 3.8 (on OSX the default changed from “fork” to “spawn”, but can be changed back manually via a new kwarg - see PR #3991)
      3. Adrian did a PR that improves the error message when pickling fails: https://github.com/pymc-devs/pymc3/pull/3991
      4. Most issues seem to be related/fixable by how the user implement stuff in notebooks. We’ll create a Wiki page with known problems and workarounds
    2. Should we aim for a virtual hackathon preceded by issue review sometime?
      1. Issue with list of NBs needing manual style update: https://github.com/pymc-devs/pymc3/issues/3959
      2. InferenceData/posterior predictive related
    3. Any big new feature targets?
      1. MLDA coming soon
      2. pm.DifferentialEquation move to sunode?
      3. Theano-JAX / symbolic PyMC discussion → deferred to next meeting
    4. Communicate collectively around PyMC being in Tidelift subscription now
    5. Set up dates and process for annual fund-raisers (Bayes Days, Laplace Day, etc.)
  2. Theano-PyMC Development Updates
    1. Adding Theano-PyMC to Tidelift
  3. PyMCon
    1. We got a lot of great proposals!!
    2. Will need volunteers to run the conference
      1. Please volunteer or help find volunteers
      2. Can we get 1 or 2 people to help with sprints?
    3. Will opening attendee registration this month
    4. Oriol and Alex got Tidelift to sponsor PyMCon!
    5. Things will really pickup by next Lab meeting
  4. ArviZ is now NumFOCUS sponsored
  5. Journal club
    1. September paper?

Friday August 8, 2020

Agenda

  1. Google Summer of Code 2020
    1. General updates
  2. PyMC3 Development
    1. Fixing the test env (we can’t merge PRs right now): candidate fixing PR
    2. Compile docs to 3.9.3 (currently on 3.8)
    3. Communication of releases
      1. Theano 1.0.5
      2. PyMC 3.9.3
    4. How do we proceed with the MLDA PR?
  3. Theano-PyMC Development
  4. PyMCon
    1. Help recruit volunteers, particularly a technology chair
    2. Share CFP with 2 people you know
    3. Refer sponsors (The money will go to PyMC)
  5. Journal club
    1. Next meeting Aug. 14: any topic proposals?

Friday July 3, 2020

Agenda

  1. Google Summer of Code 2020
    1. General updates
  2. PyMC3 development
    1. When do we drop py36? (see PR)
    2. Migration of from_pymc3 from ArviZ to PyMC code base
    3. Theano fork releases
    4. Symjax developments / Symbolic PyMC integration
  3. PyMC4 development updates
  4. Journal club
    1. Next meeting July 10
    2. https://arxiv.org/pdf/2004.12550.pdf

June 5, 2020

Agenda

  1. Google Summer of Code 2020
    1. schedule (bi)weekly meetings to sync up
    2. push for blogposts (blog seems to be now a NumFOCUS requirement: https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-students.md#during-the-summer)
  2. Tidelift
  3. Versioning
    1. introducing 3.x.x pattern
    2. Eric & Michael will try to increase release automation
    3. major ~quarterly
    4. bugifxes ~monthly & by priority
    5. PyMC4 will be 4.x.x
  4. PyMC3 development updates
    1. 3.9 release
      1. Lots of ValueError: Mass matrix contains zeros on the diagonal on master — is jitter+adapt_diag more unstable than on 3.8? See here for instance, or lots of questions on Discourse. - Few instance of this error in the last two weeks, either on GitHub or Discourse — good sign? Maybe was just a false positive? - Wait for 3.9 and see if there really is a problem. - Current workaround (changing initialization method to adapt_diag is not ideal insofar as it makes users loose some of the benefits of running parallel chains.
      2. New option to return InferenceData through pm.sample (merged). Set this as the default returned type in 3.1?.0? - Release the feature silently in 3.9 so that we can all test it internally - Implement FutureWarning in 3.10 and also potentially in 3.11 - Set InferenceData as the new default in 3.11 or 3.12 (~end of year)
      3. Theano fork releases?
        • Fix index issue, especially because Numpy will break one day.
        • Release with major PyMC version — 3.9? 3.10?
    2. Testing
      1. do we need to figure out how to further decompose our testing as it grows?
      2. how can we test to reduce breakage between ArviZ and PyMC3?
        • Migrate from_pymc3 from ArviZ to PyMC code base, to ease bug fixes and new features development. This would also make InferenceData native to PyMC3, as it is in PyMC4
        • Necessity to test against latest ArviZ release and ArviZ master in CI
  5. PyMC4 development updates
    1. From slack discussion is TFP a good backend or symjax? (symjax meeting was rescheduled)
  6. PyMC4 logo design

Notes

Move to Google Meet for future meetings

May 1, 2020

Agenda

  1. Google Summer of Code 2020
    • Waiting for NumFOCUS to make decisions. Nothing to be done until the students have acceptance notes.
  2. Tidelift
    • Waiting for more information from Chris about Tidelift — Would it be for funding?
  3. Returning InferenceData from sample Pain points for deploying model:
    • Parallelism — how do we assure ourselves that we are using all the resources of a particular high performance computing environment. Do we want multiple cores? Multiple chains? GPUs?
    • Decomposing operations onto a pipeline is difficult. Saving and reloading traces is a problem. Hence interest in replacing MultiTrace with InferenceData — no decision on that taken during meeting —> save it for future lab meeting. See discussion on GitHub.
  4. PyMC3 dependency issues
    1. Matplotlib / Seaborn conflicts (issue #3849)
      • Big pain point. Include fix in next release. Alex will pin Matplotlib (<= 3.0.0 ?) to the appropriate release in dependencies.
    2. Updating theano
      • Not discussed —> save it for future lab meeting.
    3. Synchronizing PyMC3 and ArviZ versions
      • ArviZ already pinned to 0.7 in dependencies. PyMC stats and diagnostics docs should link to ArviZ’s. Alex will see how to do that with Colin.
  5. PyMC4 development updates
    1. Docs with mkdocs
      • Eric is experimenting with it and will get back to us. (see #3900)
    2. TFP / JAX / NumPyro
      • Would these be interesting back-ends? Eric will experiment with mcx and get back to us.
  6. Issue and PR review (as time permits)
    • Initialization seems more sensitive on the master branch, making init="adapt_diag" and using testvals very often necessary. Where can it come from? What changed on the master branch? Robert will try to investigate this through the test suite.
  7. Miscellaneous
    • Kevin Systrom (Instagram founder) engaging with PyMC — see https://rt.live. Other interest from health care organizations. Big enthusiasm from PyMC devs to keep this momentum going.
    • Cutting 3.9 release soon? Adopting faster release cycles to reduce the gap between master and the latest released version? This would also make the docs and notebooks gallery more up to date with current functionnalities. Would a 6 months release cycle be appropriate? Or doing patch releases? No decision on that taken during meeting —> save it for future lab meeting.
    • Several Wiki pages seem out of date. Michael will review and modify or delete them.

March 6, 2020

Agenda

  1. Google Summer of Code 2020
    1. Need to start a document identifying students
    2. Summary of applicants of intensity of students in each project so we can start a selection
      1. Variational Inference.
      2. Students are reaching out to Maxim directly
  2. Forking Theano
    1. What are rules for merging things?
    2. Is there a general roadmap of things we should do?
      1. Fixing tests/Getting CI running?
      2. Porting over PRs from original Theano repo that look good
    3. Not sure of best path forward, everyone contributes to this
    4. Mentioned that there’s thing we can do.
      1. Colin has a big PR on original repository to the fork (https://github.com/Theano/Theano/pull/6729)
      2. Should merge the ones we opened into our own fork
      3. Add a github template informing folks where things will go
      4. There’s a few that Brandon opened that added graph
      5. Move all of our PRs over to the new repo
      6. Drop python 2 support and related code path (Ask Colin on this one)
        1. Hold off on making big code changes until we merge small prs
      7. Fix tests first? Or pull in Colin's test too much?
      8. One possible path
        1. Transfer all our pull requests first
        2. Comb through issues and other PRs on original theano repository and see what’s interesting
        3. Get CI working and come up with a plan
  3. Merging contributor attribution
    1. Should be fixed today 3/6
  4. PyMC4 development updates
    1. GP PR
      1. For those on call no one has time to look at PR
    2. Still discussing if Gaussian process is necessary
      1. Pr is trying to recreate a similar api compared to PyMC3
      2. But there’s pros and cons for this
      3. Chris is saying GP is hard to use because arrays need to be set ahead of time
      4. If we can come up with a nice api with not a lot a code
    3. What pull requests in TFP main repo would be useful in PyMC4
      1. For example for compound step is one of those
      2. Not sure how to proceed with that PR, whether it goes into PyMC4 or Compound Step
        1. Better to leave this compound step on PyMC4, Junpeng is not confident they’ll add sampler
        2. Compound step is controversial because it could be construed as inefficient
        3. Would be a good Google Summer of Code project
  5. PyMC3 PRs
    1. Several PRs are coming from us
    2. Do something like a PR bash in the time coming
    3. See if we can get those PRs merged
    4. Go through PRs and label bugfix or feature
    5. Focus on getting our fork of Theano first before clearing through PyMC3
      1. There’s a few Theano ops we never merged into Theano so these could be good to push up
      2. Let’s focus on getting our own fork working. Give some new momentum on PyMC development
  6. PY for vectorized posterior predictive
    1. Robert has permission from Chris to just merge it
    2. Bug review would be good
    3. Try and do bug bash before GSOC
  7. Issue and PR review (as time permits)

February 7, 2020

Agenda

  1. Google Summer of Code 2020
    1. Review of deadlines
    2. Project list review
    3. Student candidates
  2. NumFOCUS Open Source Sprints
    1. Bloomberg, April 4-5 in NYC
      1. Robert, maybe
    2. May 2-3 in London
    3. June 15 as part of PyData Amsterdam.
    4. Aug 20 something PyDataLA
      1. Ravin
  3. Forking Theano: see Notes.
  4. Vectorized posterior predictive sampling: clean up the context handling, and then merge in the current form, keeping the separate entry point: fast_sample_posterior_predictive
  5. PyMC4 development updates
    1. Proposed roadmap from Luciano +PyMC4 roadmap
  6. Issue and PR review (as time permits)

Notes

  • Thomas forked Theano to Theano-PyMC. We should look to prepare a release and make it a PyMC3 dependency.
  • Might be good to have a mass matrix adaptation project for GSoC

December 6, 2019

Agenda

  1. PyMC4 development updates
  2. Issue and PR review
  3. Observations vs. predictors(explanatory variables)
  4. PyMC3 default mass matrix adaptation

Notes

Observations vs predictors:

  • Can we update weight variables in a linear regression example using pm.Data?
  • Should there be a notion of pm.Constant, to distinguish from pm.Data that goes into observed=?
  • If there are deterministics that depend on pm.Data or tt.shared variables, this breaks the posterior predictive checks: interaction of model and trace is hard for users to reason about.
  • ArviZ needs a “blessed” reference to the model instead of using a private attribute, like it does now.
    • This also helps in the usecase where you have 2 models, one for inference, one for prediction, and want to be explicit about which to “bind to”

November 1, 2019

Agenda

  1. PyMC4 development updates
    • deterministic remains a blocker
      • make a PR to tfp (possibly in experimental)
    • context vs yield
      • yield seems nice
    • “Example driven development” can be useful
      • translate notebooks, even if they don’t work
  2. NumFOCUS Summit
  3. PyMC3 release
  4. NIPS presentation
    • will be presented by Thomas and Maxim
    • comments welcome for the poster
    • prepare answers for tough questions (reviewer comments etc)
    • FAQ at the poster itself
    1. other goals:
      1. meet with other PPL developers (pyro/numpyro)
  5. Xarray for Bayesians Examples/Challenges
  6. PyDataLA Sprints
    • Help tag issues that are small and beginner friendly when you see them!
    • Will be on December 3rd

October 2019

No meeting held

September 6, 2019

Agenda

  1. GSoC 2019 Wrap-up
    • Joseph
    • Demetri
    • Martin
    • Aniruddha
    • Oriol
  2. PyMC4 development updates (Will discuss in next meeting)
  3. Trademark protection (Will discuss in next meeting)

Notes

Joseph

Worked on Symbolic PyMC project
BaseMetaSymbol class was refactored to include a dispatcher
Why a gibbs sampler?
    That was part of the proposal and trying to move towards it
How does graph printing work?
    How does it work differently than tensorboard?
Is there an example of where we take a PyMC3 model and get a graph?
    Yes, and Joseph has it working against a PyMC4 model as well

Demetri

Adding Differential Equation to PyMC4
The to fit parameters is usually is fit a least squares problem
Modeled after Stans functionality
Potentially would like to add functionality where user can hot swap gradients
Adrian - Solver might not the slowness, but Theano call overhead might be the issue.
    We could put in numba functions instead of python functions
    Tensorflow or Jax compile functions but only give wrapper functions and we don’t always get the underlying function
    Might want to look at the library Adrian is writing
    Another thing we can also look at is surrogate models, if we have a relatively small system then we could find different functions that approximate the solution of the ODE, like Chaos polynomial expansion. PyMC would only see the surrogate model
    PyMC could work on the surrogate model
Colin - Are there notebooks on how to use this?
    Yes, its in the PR

Martin

Osvaldo, Martin and Austin worked on Bayesian Additive Trees
Not working fully at the moment but the idea is to grow the tree in a Bayesian way looking at the data
Started out with a non PyMC implementation and then are working with Osvaldo to start implementing it into PyMC3 model
Working on a more flexible way to set priors currently
Thomas - Is the split values probabilistic or discrete? Taken from a uniform distribution. 
Do we get posteriors over the split values?
    No
Is there a notebook or code example?
    The model isn’t quite working yet but there is a notebook showing progress
Junpeng - Any areas of difficulty we can help with?
    Talked to Osvaldo and Austin and in the beginning we have a problem replicating one of the priors but we do have a notebook
    Two problems - One was PyMC codebase onboarding for Martin.
    In a month we will likely have a model that works internally

Aniruddha

Find slow ArviZ places, and optimize with Numba
Profiled each and every line of code with a line profiler, remove the bottleneck with Numba, and then benchmark improvement
~30% improvement in stats and diagnostics
Next was plots, so most plots came from fast_kde, so if that was optimized then many plots could be optimized
The last thing working on was Ahead of time compilation with Numba, should be able to do it this month or so
To use the work, the user doesn’t have to do it’s enabled automatically, but have given everything in detail in the blog post
Junpeng
    Was this tried on a cloud platform like colab?
    Aniruddha, did not try anything across platform but numba is designed to work across platform so it should work

Oriol

Project was focused on Information Criteria. Check whether an MCMC run has converged or not
Got that done and additional diagnostic functionality as well
Resampling is holding up a diagnostic that is possible in PyStan. An issue is open
Second assessment is convergence assessment
Implemented additional functionality that Aki published in a recent paper
Third section was Model Checking 
Added LOO-PIT to ArviZ along with plotting

August 2, 2019

Agenda

  1. GSoC 2019
    • Status reports, if available
    • ode assimulo
  2. PyMC4 Development Updates
    • Progress blockers
  3. PyMC3 Development Issues
    1. Variable names regexp
  4. Next journal club

Notes

  1. PyMC4 Updates

    • Can define Logp function
    • No samplers
    • Other distributions
    • Max finds himself not having that much expertise in samplers so he can’t solve core path
      • Could use Generalize and modularize the backend API
    • Prior predictive samples are correct
      • Static graph versus dynamic graph was the issue but it seems to have been resolved
      • PyMC will have a small sampler meeting first
      • In a week or two weeks

  2. PyMC3 Update

    1. Should the strings for varnames be restricted?
      1. I [RPG] believe the sense of the group was that arviz dims could be limited to acceptable python variable names, since they are relative newcomers, but that restricting variable names might break too much legacy code. We mentioned that spaces in variable names were commonly used as was unicode, especially for Greek letters. [new note: it might be nice to have something that could be interpretable as superscript or subscript, like TeX’s “^” and “_” — underscore being problematic for python, since it’s so commonly used as a substitute for “ “.]
    2. Should the SMC portion be removed from sampler because it adds so many new keywords
      1. SMC is never an automatically chosen method
      2. The decision to do SMC is a big conscious step
      3. SMC and SMC/ABC are already combined
      4. The parallelization is a completely different sample size
      5. Might have a positive effect of seeing SMC because its more visible
      6. Osvaldo will move SMC (and SMC-ABC) to sample_smc
      7. No effort was made to check that all the step functions were added
        1. Possible that some may have been added and not documented
    3. Any lingering issues that need to be addressed?
      1. Categorical Memory Error: https://github.com/pymc-devs/pymc3/issues/3566
    4. Next Journal club,
      1. We also want to have a sampling meeting so we could skip Journal Club
    5. Any other non agenda items?
      1. None

July 12, 2019

Agenda

  1. GSoC 2019
    • Status reports
      • Symbolic pymc is going great
      • Harivallabha said he’s willing to keep contributing but likely in a milder scale.
  2. PyMC4 Development Updates
    • Observed variables
    • analog of pm.Normal.dist
  3. NumFOCUS Summit (November)
  4. Next journal club
    • Selecting the Metric in Hamiltonian Monte Carlo
    • Exact Gaussian processes on a million data points

Notes

Maybe schedule a review of open PyMC3 issues at a later meeting? Possibly this should be just for a subset of people interested in the maintenance of this code base (as opposed to people who want to focus on PyMC4).

  • Monthly bug hackathons are nice

June 7, 2019

Agenda

  1. GSoC 2019
    • Status reports
  2. Azure CI
  3. PyMC4 Development Updates
    • Development summit follow-up
    • Generator model API
  4. Next journal club
    • Selecting the Metric in Hamiltonian Monte Carlo
    • Exact Gaussian processes on a million data points

May 3, 2019

Agenda

  1. Spring Developer Summit
    • Followup call May 8
  2. GSoC 2019
    • Final student choices
    • Next steps
  3. PyMC4 Development Updates
  4. Next journal club
    • Colin(?)

Notes

Developer Summit:

— Dinner with Google folk first night (28th? Might interfere with Florence and the Machine!)
— Call on May 8
    — What is tf2 vs tf1 standard? Write so a graph mode could work, but don’t use session.
    —  Lots of ways to write a model. Will that settle down?

GSoC 2019

— Four spots instead of five. Don’t tell the students yet.
— Top four projects. Once public, (video-)meet with students

PyMC4:

— Rebump “observed” issue in `pymc4` repo
— Multiple chains is super cool. having 1k chains instead of 4 means you can do statistics instead of visually inspecting. Nice to use instead of MPI. See if stan has thought about this.
—Generators being able to “send” back is flexible and interesting. alternative to inheritance.

Journal Club:

— Next Friday! “Neutra-lizing”

Other Meetings:

  • Probabilistic and differentiable programming gathering in SF in June (Colin and probably Ravin)
  • Scipy: Eric is doing more PyMC3. Check out the work Ravin et. al. have been developing on a bayesian workflow
  • Workshop at Quantum Black in London (Thomas + Colin, maybe in the Fall)
  • PyData LA cfp coming up

Hey! Let’s cut a release!

  • What’s missing? Might need to rerun one last GP notebook to be good with ArviZ.
  • @Thomas W has a few he might need to push
    • Density regression
  • 3.7!
    • don’t wait for ArviZ, we’ll just have a >= version.

April 5, 2019

Agenda

  1. Spring Developer Summit
    • Confirmed dates May 28-29, Montreal
    • Prep calls
      • First call agenda
    • Review TF2 architecture before Montreal please!
      • Look at Sample vs Independent, in particular
  2. GSoC 2019
    • Potential students (and mentors)
    • Application deadline (timeline I think there’s a separate NumFOCUS deadline)
    • Evaluation rubric
  3. PyMC4 Development Updates
    • Junpeng and Josh prototype
  4. Talks and conferences
    • Austin 19th? in NYC
    • Quansight webinar today
    • Eric @ PyCon
    • Ravin, Colin and Eric @ SciPy
    • Junpeng will be in MTV for 2 weeks early May if there is anybody around
  5. Next journal club
    • Brandon(?)

Notes

  • Let’s make sure we can still edit proposals after the 9th (when applications are due)
  • if so, let’s have a meeting then, and figure out a first pass of students to give thorough feedback to
  • We can have a “canned response” until then

March 2019

Agenda

  1. Spring Developer Summit
  • Location (if it is in Zurich junpenglao can host)
  • Dates
  1. GSoC 2019
  1. PyMC4 Development Updates
  2. Next journal club
  3. Paying for Slack? Yes!
  4. Nightly builds for pymc3
  5. Tensorflow Dev Summit
  • Any burning questions?
  • Would attendance be helpful?

Notes

  • Meeting
    • Let’s figure out if London or Montreal is preferred?
      • Zurich? Maybe not…
    • Should do more video calls with google before then
      • New Stan compiler is doing an “open weekly standup”, which google could choose to attend
        • Colin might aim at helping with this starting mid-march
  • GSoC 2019
  • https://github.com/numfocus/gsoc/blob/master/2019/ideas-list.md
  • Potential Students
    1. +GSoC 2019 student list
  • PyMC4 progress
    • Need to hook the tfp inference up to models
      • Can also hook pymc3 samplers up to pymc4 models, looks at the slowdown
    • 2 nice PRs: one to auto-transform variables, another to rename parameters of distributions.
      • Eric will make a last change to the parameter renaming, and then we can merge
      • Transform has a tiny bit of work, then should go in
    • https://github.com/pymc-devs/pymc4/issues/84 Functional API by writing a Class as model
    • AST parsing: Agreement in principle to test it out on PyMC4 with it being off by default

Tensorflow Developer Summit

  • No burning questions for Tensorflow devs in general for TF Summit

  • TF devs are all busy porting code from Tensorflor 1 to Tensorflow 2. Guidelines of docs of good Tensorflow 2 code

  • We should probably care about writing for tensorflow 2 instead of tensorflow 1.

  • Maybe something on graph editing?

  • New release?

    • Lots of nice shape stuff
    • Give it a few days for arviz PR
    • Maybe next week or two

February 2019

No meeting

Friday January 4, 2019

Agenda

  1. PyMC4 Development
  • tf 2.0
  1. PyMC3 formatting standards
  • Adopting new standards
  • Add section to contributor’s guide?
  1. ArviZ update
  2. PyMC website update
  3. Greek symbol kwargs
  4. GSoC projects
  5. Next journal club

Notes

  1. Add tf-2.0 to requirements.txt
  • where is tf-2.0 being published from? where’s the source code?
    • It might be here, which looks like it is internal google code…
  • GSoC — should update wiki with new ideas and keep older good ideas
  1. Create document outlining the case for/against using Black for formatting
  2. ArviZ should implement
  • probably use aliases (traceplot = az.plot_trace)
  • good that numba is optional in arviz so it isn’t pulled in as a dependency
  1. Website looks good!
  2. Greek symbols
  • Attending members mostly think nothing is wrong with it
  • View of “this is confusing for beginners was presented”
  • It can be viewed as “an Easter egg”
  1. GSOC
  1. Next journal club

December 2018

No meeting

Friday November 9, 2018

Agenda

  1. Cut a new release
  • Readme and docs need updated
  • Deployment stuff on conda-forge
  1. What to do about random draws https://github.com/pymc-devs/pymc3/pull/3214
  • Invite Luciano to dev summit?
  1. PyMC4 Developers Summit
  • agenda
  • logistics
  • tensorflow materials
  1. ArviZ update and PyMC3 plotting deprecation road map
  2. PyMC website
  3. Next journal club

Notes

  1. cut small release, start adding .dev to end of master version
  2. Invite luciano to slack at least to discuss the PR
  • seems to be a preference to merge soon, since it does fix the problem
  • draw_valuesis doing a few jobs, which leads to problems like this and makes.random` slow
  • we might do a refactor to address that after
  • some question about adding then removing a requirement
  1. Check out design docs for PyMC4
  • Think about how much time designing vs coding
  • We are probably using tensorflow 2 instead of tf1
  1. ArviZ seems like it could have wrappers mapping or make a strong API change
  • Let’s make a PR for traceplot after the next release and talk it over there.
  1. New website prototype will get pushed later today to a branch
  • Sphinx is a little hard to work with for “nice” design (need to hack both sphinx and docutils to really do that)
  • Possibly have a static site that links into a sphinx-generated site?
  1. Journal club: a tensorflow/edward paper?

Friday October 5, 2018

Agenda

  1. NumFOCUS summit debriefing
  • roadmap
  • governance
  • infrastructure
  • culture/CoC
  • fund-raising
  1. Tensorflow backend for PyMC4
  • Dustin and TFP
    • Key question: how tight integration of interceptor in TFP?
  • Face-to-face development meeting
  1. Arviz update and PyMC3 plotting deprecation road map
  2. Let’s get a proper website around here
  3. Next journal club
  4. Hamiltonian Descent Methods (https://arxiv.org/abs/1809.05042)
  5. Semi-implicit variational inference (https://arxiv.org/abs/1805.11183)

Notes

  1. Next journal club
  • Hamiltonian Descent Methods — seems too heavy
  • Semi-implicit variational inference — softly planned in 2 weeks
  1. NumFOCUS summit debrief
  • Mo money mo problems
  • Should roadmaps have dates?
    • Misplaced expectations vs. estimates to work towards
    • Start doing quick review at lab meeting
    • PyMC4 roadmap should exist? (punt to later)
  • Infrastructure desires
    • Paying for CI or moving to Azure pipelines would save a lot of build time, but take upfront investment. Perhaps we can advertise (on the roadmap?!) that this is a task we’d like help with, and could support with a subscription to some CI service.
    • Upgrade slack? or some other real-time discussion method?
  • From Eric Schles at microsoft: “I meant to ask if you wanted funding things too? I know some folks in boston that could be helpful. Feel free to follow up over email - [email protected]”
  1. In person meeting for PyMC4
  • Dustin not with TfP team, but still at google.
    • going to try to develop edward2 as an independent project with more control
    • tfp team is more focused on internal use - distributions, for example. dustin is interested in bayesian inference.
    • Sounds more interesting to follow edward2 along?
    • Should have more regular meetings with TfP team - can we ask for a roadmap for edward2 and tfp?
    • Another approach is to build stuff, using tensorflow probablility as an open source library, and not worrying about co-operating with the developing ecosystem (note: we are not obligated to work with google, nor does anyone work for google)
  1. New documentation
  • 99 designs has been good in the past - can get logos, css, color stuff
    • don’t want it to look like a template
  • squarespace etc might be cool.
  • Stan has merch on theirs!

Friday September 7, 2018

Agenda

  1. NumFOCUS summit
  2. AWS resource needs (infrastructure budget)
  • NumFOCUS announcement
  1. First face-to-face development meeting planning
  2. Arviz update and PyMC3 plotting deprecation road map
  3. PyMC4 development updates
  4. Type annotations
  1. Next journal club

Notes

AWS needs:

  • running notebook suite
  • AWS specific or not?
  • Enterprise TravisCI
  • Benchmarking (add to airspeed velocity suite to directly compare GPU vs CPU on some tasks?)

Face to Face meeting:

  • Firstish week of December
    • 1 day of “developer sprint”
    • 1/2 day of community workshop
    • 1/2 day of conference style setting
  • “PyMC Developer Summit”, perhaps
  • Second in spring in North America (probably Mtn View, maybe Boston)

Release plan

  • 3.6 release that is Py3-only and supports Arviz plotting

Type Annotations

  • Start in 2019
  • Helps new developers get into the code base
  • Also helps users who are using the right tooling use pymc3
  • Go iteratively, not all at once

Journal Club

  • Let’s do a poll to not leave someone alone again 😞

Meeting Friday August 10, 2018

Agenda

  1. GSoC Project Updates (as availability permits)
  • Agustina
  • Sharan
  • Bill
  1. NumFOCUS summit
  2. ArviZ update
  3. Google TFP meeting debrief
  4. First face-to-face development meeting planning (what about vacations next year?🙂)
  5. Next journal club

Notes

  1. GSoC updates: a. Bill: cleaning up some (5!) PRs, fixing test suite to be more useful. CO2 example updated with input from climate scientist b. Agustina: SMC-ABC is working, but brittle/hacky. Could be because SMC is changing underneath (PR is out now). https://agustinaarroyuelo.github.io/jekyll/update/2018/08/08/final_evaluation.html c. Sharan: PyMC4 meeting happened, defun could be very useful, and they probably understand our problem. https://github.com/sharanry/gsoc18
  2. Google TFP meeting debrief Engaged, willing to help Still interested in eager vs. graph mode
    • should we support both?
    • what do they prefer?
    • NUTS is only in eager mode, it seems
    • If eager mode, what are the benefits over PyTorch
      • Can we do NUTS in graph mode? High overhead for calling, e.g. logp from python - “should only call it twice”
  3. NumFOCUS summit
  4. End of September: either Austin or Colin might go.
  5. Chris can forward email
  6. ArviZ update
  7. Osvaldo is using it in a course this semester
  8. Will be presentation in probprog on arviz
  9. xarray might turn into a backend for pymc3
  10. should deprecate plotting in a 3.5.x release
  11. Face to Face dev planning
  12. Start planning on the fall - either mountain view or europe 1. Europe: Amsterdam or London might have hosts
    1. Visa difficulties: amsterdam < london << USA
    2. Will also have remote call in b. Vanderbilt post-doc c. Vacation meeting in Europe
  13. Journal club
  14. 17 august to talk about variance networks (Maxim)

Meeting Friday July 6, 2018

Agenda

  1. GSoC Project Updates (as availability permits)
  2. Agustina
  3. Sharan
  4. Bill
  5. 3.4.2 release
  6. PyMC4 API next steps a. TensorFlow backend updates
  7. ArviZ update
  8. Next journal club

Notes

  • PyMC4: Prepare for another Tensorflow Probability meeting
    • clean up api proposal
    • share blog post with api example
    • ask graph question (every time the interceptor is used, the tensorflow graph gets larger)
    • submit PR for half cauchy?
    • make sure at least sharan and ferrine can be on call
  • Journal club:
    • July 20?
    • Yes, But Did it Work? Yao, Vehtari, Simpson, Gelman
  • Release in the next ~week

Meeting Friday June 1, 2018

Agenda

  1. GSoC Project Updates
    1. Agustina
    2. Sharan
    3. Bill
  2. Google collaboration updates
  3. ArviZ
    1. xarray?
  4. Docathon
  5. Next journal club

Meeting Friday May 4, 2018

Agenda

  1. PyMC4 TensorFlow backend
    • Updates from TensorFlow team
    • Questions for TensorFlow team
    • Project roadmap (+PyMC Timeline )
  2. Travis CI housekeeping (someone just needs to do this eventually)
  3. GSOC 2018
    • Project statuses
  4. Version 3.5 planning *Ordered, draw_values, sample_prior, ArviZ(?)
  5. Next journal club

Notes

  • Consensus on TF this week
    • Google (Rif) very keen, some funding for face-to-face travel
      • 1 North America (Mountain View?), 1 Europe
      • 1 Fall, 1 Spring
    • Get together roadmap
      • We should inquire about NUTS
    • Money for postdoc from Google? Plus protected time?
    • Should ask some of Maxim’s questions from other doc
  • Outside communication w.r.t. Tensorflow
    • Public announcement that we’re using Tensorflow?
    • Public announcement on Theano support?
    • Two roadmaps: PyMC3 is production ready, will be supported and developed for X years. PyMC4 highly experimental and exciting
    • One blog post
  • Chris will click a button for Travis. Eventually.
  • New repo for pymc4 when needed, experimental code in pymc4-prototypes
    • delete pymc4-prototypes when it is no longer useful?
  • Ordered done!
  • Rerun examples — add check_model_point, ArviZ,
  • Deprecate plotting if arviz is working out
  • Journal club — maybe Augustina can present on ABC? Two weeks from now?

Meeting Friday April 6, 2018

Agenda

  1. Plan a new release
  • Remaining issues/PRs (Sample prior PR and Ordered transform PR could wait)
  • Update docs
  1. PyMC4 backend updates
  • Discussion of call with TensorFlow team
  • Updates on Theano support
  1. GSOC 2018
  • Candidate selection
  1. Project roadmaps
  2. Hackathon
  • MAN AHL is organizing a Hackathon on April 21-22 (One of the organizer Slavi contacted us Junpeng, Thomas, Adrian, Peadar). I had a chat with him and said we can provide some online support (I cannot be there so are Thomas and Peadar, Adrian you interested?). Anybody has suggestion for good topics (docs/bugfixs/features)?
  1. Next journal club

Notes

  • Rerun thomas’ ADVI documentation/blog
  • Like tensorflow - adrian close to working mxnet example
  • colin will put together a timeline with new backend, theano, versions, python3, etc.
  • timeseries work isn’t a clear enough proposal. would be great to have timeseries support, though
  • someone else (adrian/colin?) should sign up to mentor GSOC backend project

Meeting Friday March 2, 2018

Agenda

  1. PyMC4 backend updates
  • Theano is dead; long live Theano!
  1. WIP PR that need more discussion
  • logp-caching in Metropolis - might not be correct to do afterall, especially when compound step is involved
  • sample_prior (1pr or 2?) - to be discuss in slack
  1. GSOC 2018
  • Candidates - Osvaldo has 1 for sure, couple more have contacted us. For now we wait until we know how many slot we have
  1. PyMC3 Symposium/Meetup
  • date to be decide around April (next meeting)
  1. Next docathon: schedule
  • instead of a docathon, we invest some time to draft the two road maps instead over a period of time.
  1. Next journal club
  • discuss in slack

Notes

  • Need to develop a project roadmap for both PyMC3 and PyMC4

Meeting Friday February 2

Agenda

  1. PyMC4 backend updates
  2. Pyro
  3. Tensorflow
  4. GSOC 2018
  5. Next docathon: schedule
  6. Next journal club

Notes

Pyro backend:

  • Junpeng’s prototype looks really good!
  • Tensorflow data in/out seems slow

documentation:

  • Automate notebooks
  • “Getting Started” is a little academic
  • “Quickstart” is not that quick

Other:

  • deprecate findMap?
  • don’t initialize NUTS with a point (Hessian computation is slow)

Meeting Friday January 5, 2018

Agenda

  1. 3.3 release
    • Recent Travis build problem: TODO Ask Travis about failures, does money fix the problem?
    • Theano 1.0
  2. PyMC4 backend updates
  3. Next docathon: schedule
  4. Next journal club: Colin on https://arxiv.org/pdf/1711.09268.pdf
  5. Invite Michael Osthege to slack

Meeting Friday, December 1 2017

Agenda

  1. New backend experiments
    • Updates on exploration of MXNet/TensorFlow/PyTorch
  2. CSG and DEMC PRs
  3. GSoC ideas
  4. Next Journal club

Meeting Friday, November 3 2017

Agenda

  1. Patreon update
  2. Debriefing from NumFOCUS conference call
    • Ideas for support targets
    • Updates for Patreon page
  3. Next Docathon
  4. Next Journal club
  5. New backend experiments
    • Updates on exploration of MXNet/TensorFlow/PyTorch

Meeting Friday September 30, 2017

Agenda

  1. Release 3.2
  2. Feature freeze (already done?)
  3. Making matplotlib optional (nearly ready?)
  4. Put out release candidate, and then full release
  5. Release notes: Chris + Thomas
  6. Patreon update
  7. possible to support our slack channel upgrade
  8. Release notes
  9. Add them to every medium to large sized pull-request
  10. https://github.com/blog/2111-issue-and-pull-request-templates
  11. Docathon
  12. Poll result of docathon
  13. Travis auto-build update
  14. Template for doc?
  15. Journal club
  16. Friday, same time as lab meeting 10/6
  17. New backend
  18. Static graph (Tensorflow)
  19. Dynamic graph (PyTorch, MXNet, Chainer)
  20. Others

Notes

Create RC today

  • need what’s new section

New Backend brain storm (RIP Theano 😞 https://groups.google.com/forum/m/#!topic/theano-dev/gCBAhE3Sb_8)

  • Tensorflow(Backed by Google) Pros:

    • Strong support, large community
    • Tensorboard for visualization
    • parallel within graph execution that makes things fast
    • Convenient deployment Cons:
    • Slow?
    • Too many similar package already (e.g., Edward, ZhuSuan, Greta in R)
    • Edward will be somewhat official as part of it? Compiler for graphs in development: XLA. It is supposed to support memory optimisations and Op fusion when it's done. Custom Ops can be written in python, but C++ ops require us to play games with that strange build system (written in java, and probably not going to end up in any linux packages) Old experiment for using it as backend: https://gist.github.com/aseyboldt/1054cf6d6b871041914c601c1efa11ae

  • PyTorch(Backed by Facebook) Pros:

    • Dynamic graph
    • easy GPU acceleration
    • seems to be growing fast and well supported.
    • use of standard debugging tools
    • Numpy-like syntax (probably easier for end-users)
    • higher-order derivatives Cons:
    • Not well suited for tricks we did in pymc3 (array_ordering)

    If we go for pytorch we should focus on variational inference for deep learning, it’s rather well suited. MCMC can be hard to implement because of pytorch design. If we ever wanted to do RL, seems like a dynamic graph would be the way to go. Would require us to change how models are defined, because we rely on a static graph right now. Not sure automatic graph optimisations are possible. There seems to be some work towards a tracing jit, but that seems to only eliminate runtime overhead right now (if I understand it correctly).

  • MXNet(Backed by Apache and Amazon) Static and dynamic graphs. Does optimisations for static graphs using nnvm (which?) Custom ops in python (similar to theano). C++ ops should be reasonably straight forward as well. Good control over memory locations of variables. Good support for automatic parallelisation (I heard, haven't checked myself) Small user group.

(JLao): I think it is important to have fast compile times (which Theano actually improved over the years I felt), so a nn library with dynamic graph would probably faster at that end.

General thoughts are that we already have a good tool for small models and MCMC, we can either try to recreate and extend it somewhere else or focus on things we can’t do with pymc3 (deep learning with large number of parameters). New backend should be deployable (theano is not).

Meeting: Friday August 4, 2017

Agenda

  1. Documentation
  • Schedule next Docathon
  • Reviewers of written docs
    • poll discourse for help (split time between new docs and review)
  • Decided on rst-format for new docs
  • PyMC3 gallery
    • Colin is going to try a thing in ~2wks if no one else does
  1. Google Summer of Code updates
  2. Bill
  3. Maxim 1. Upcoming Grouped VI API https://github.com/pymc-devs/pymc3/pull/2416 2. Hierarchical VI thoughts https://arxiv.org/abs/1511.02386
  4. Initialization defaults
  5. Courses and tutorials
  6. DataCamp
  7. NIPS 2018
  8. PyData NY
  9. ICML Papers
  10. There are a lot of good papers(https://sites.google.com/view/implicitmodels/accepted-papers):
    1. Gradient Estimators for Implicit Models
    2. Implicit Variational Inference with Kernel Density Ratio Fitting

Notes

Potential docathon times

  • weekends
  • Late-august/early september

New users for doc review

reST vs notebooks for documentation colin will have a look at a gallery Continuum for benchmarking models

GP

  • restructuring of GP codebase
  • accomodating several uses for a GP object

VI

  • grouped VI for separating different parts of the model with different complexity

Inirialization

  • general feeling that ADVI alone is not optimal for initialization
  • mass matrix initialization might be the way to go

Meeting 2017-06-02

Agenda

  1. Ongoing Python 2 support
  1. GSoC updates
  1. Setting up of discourse.pymc3.org
  • we can set up the discourse channel now - however we need to decide the name (future proofing basically): discourse.pymc3.com/discourse.pymc.com/discourse.pymc-dev.com
  1. 3.1 release
  2. Example notebooks and scripts
  3. Docathon
  • Splitting API docs and modeling how-tos
    • Open source PyMC3 book? (long term)
  • Add sphinx gallery
  1. NumFOCUS Summit

Notes

  • Add ourselves to python3statement
  • Add warning to PyMC 3.1
  • Commit to sunsetting Py2 support by 2020?
  • Discourse to be set up as a sub domain of pymc.io
  • Implement immediate feature freeze prior to 3.1 release
    • The major blocker: ensuring notebooks run in current master
    • We will "divide and conquer" to get all the notebooks running as soon as we can
  • There was support for continuing the maintenance of notebooks within the repository.
    • Recognition that while we would prefer to have notebooks pass unit testing with every commit, this is not realistic
    • Current approach: occasionally sweep through and manually test notebooks, with more deliberate testing prior to release
    • Colin has a nice tool for testing notebooks
  • Strong support for docathon.
    • Create doodle poll for a day (maybe a polling tool within Slack?)
    • Create an issue with potential doc targets
      • Create feature branch for docathon output

Meeting 2017-05-05

Agenda

  1. Documentation
    1. Docathon
    2. Documentation leader: Austin Rochford
    3. Separate documentation/book repository
      1. Separate API vs. math/stats documentation
  2. API changes
    1. New VI interface
    2. Spec out Results object functionality
  3. GPU support
  4. Removal of sqlite and text backend (Xray)
    1. develop a serialization API
    2. explore xray as solution
  5. Better defaults for sample() (draws=1000, tune=500, njobs=4)
  6. Adrian proposal: New results object returned by sample() that contains trace, but also Rhats, ELBOs, convergence report
  7. Release of 3.1
    1. Review release checklist
    2. Deprecation warnings
  8. Outreach and educationm
    1. Conference talks
    2. Tutorials
    3. Short courses — share materials?
  9. Google Summer of Code
    1. Maxim: Taku, Thomas
    2. Bill Engels: Chris, Austin
    3. Bhargav Srinivasa: John, Colin

Notes

  • Can we ask NumFOCUS to help funded expanded TravisCI testing?
  • We need a review of our testing runs
    • can some tests be dropped or run more infrequently?
  • Separate PP education from PyMC functionality
  • Need a simple common return object/structure across all inference methods
    • dict?
    • create a spec for return object
  • float32 throughout PyMC3 coming in GSoC
  • size/shape handling could use refactoring
  • Place to aggregate resources and tutorials
  • PyMC3 course at Harvard: Check it out!
Clone this wiki locally