-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate cog/over outside base years #3903
Comments
This is now blocked pending further conversation with OMB. |
One note from OMB: we need to clearly delineate the process difference between base years and non-base years. |
@danswick , I'm going to unassign me from this ticket, because it is not clear that I'm driving the work on it? However, we can re-add me at any time (including right away). |
I think the intent of this ticket is covered in other cog/over tickets. We can/should come back here to reference the flowchart once we're ready to create public docs! |
A question has been asked about the cog/over algorithm.
Specifically, the question is: are we handling assignments outside of base years correctly?
The flow, as-is, is shown below. (The flow was previously expressed as a Mural; this is a Mermaid transcription, which would allow us to put it under version control.)
The question is, should we do the following?
This would modify the cog portion of the algorithm. After modification, it would look like:
This ticket is to track the investigation of whether or not this update to the cog/over assignment algorithm is the right thing to do.
The text was updated successfully, but these errors were encountered: