-
Notifications
You must be signed in to change notification settings - Fork 15
397 add comments and example pins to help explain proration #404
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
base: master
Are you sure you want to change the base?
397 add comments and example pins to help explain proration #404
Conversation
|
|
||
| # PINs can be multi-card, and have different numbers of cards. | ||
| # In stage 3.1, tieback PIN 05283170010000 has PINs with 2 and 3 cards, | ||
| # and tieback PIN 01131010080000 has PINs with 1 and 2 cards. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
select meta_tieback_key_pin, meta_pin_num_cards, meta_pin
FROM "model"."assessment_pin"
where meta_tieback_key_pin IN ('05283170010000', '01131010080000')
and run_id = '2025-02-11-charming-eric'
| # We currently group by meta_tieback_key_pin, meta_card_num, and char_land_sf. | ||
| # Values for char_land_sf can be both the same and different in each tieback | ||
| # grouping. For example, tieback PIN 05283170010000 has 5 total cards with the | ||
| # same SQ footage, and tieback PIN 05283170030000 has 5 total cards with two |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SELECT
ap.meta_tieback_key_pin,
ap.meta_pin,
ap.meta_pin_num_cards,
ac.meta_card_num,
ac.char_land_sf
FROM "model"."assessment_pin" ap
JOIN "model"."assessment_card" ac
ON ac.meta_pin = ap.meta_pin
AND ac.run_id = ap.run_id
WHERE ap.run_id = '2025-02-11-charming-eric'
AND ap.meta_tieback_key_pin IN ('09263150040000', '09221110050000', '05283170010000', '05283170030000')
ORDER BY ap.meta_pin, ac.meta_card_num
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One observation with matching Card values and one with different Card values,
| # 09263150040000 has three cards for each PIN with different SQ footage values. | ||
|
|
||
| # They can also have capped land values in stage 4. An example of capped value | ||
| # are tieback PINs 16012030310000 or 29071130320000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
select meta_tieback_key_pin, meta_pin_num_cards, meta_pin, flag_land_value_capped
FROM "model"."assessment_pin"
WHERE meta_tieback_key_pin IN ('16012030310000', '29071130320000')
and run_id = '2025-02-11-charming-eric'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the only observation which really differs by run_id
| # They can also be part of town-home complexes (Stage 3.2). Town-home complexes | ||
| # are grouped based on different characteristics, such as the number of rooms, | ||
| # square footage, or proration rate, meaning tiebacks can be averaged in | ||
| # separate groupings (tieback PINs 15213010030000 or 30171010230000) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
select meta_tieback_key_pin, meta_pin_num_cards, meta_pin, meta_complex_id
FROM "model"."assessment_pin"
WHERE meta_tieback_key_pin IN ('15213010030000', '30171010230000')
and run_id = '2025-02-11-charming-eric'
Tieback PINs come from the following queries. I put more specified ones regarding the individual PINs in the pipeline/02-assess.R file. I kept the context surrounding decision making to a minimum since some of that will likely change.