Skip to content

Direct implementation of unbalanced panel #90

Closed

Description

@bcallaway11

Currently, with unbalanced panel, we play a trick and run it through the repeated cross sections code and then fix the standard errors at the end. But it would be nice to have a specific implementation for unbalanced panel:

  • This would likely be much faster
  • There are issues related to time-varying covariates in this case, see: use with unbalanced panels #76
  • Perhaps the sorts of underlying missing-at-random type assumptions that rationalize unbalanced panel could be weakened if we provide a direct implementation.

This one is probably a lot of work though!

Activity

  1. Repository owner locked and limited conversation to collaborators on Feb 11, 2022
  2. converted this issue into a discussion #110 on Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions