-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add ZORI to estimation panels #252
Comments
In the revision we planned to use the Zillow rental index for robustness @diegogentilepassaro @gabrieleborg. In this issue I:
I added the new ZORI index because the methodology seemed clear enough for a robustness check. We should probably also experiment with the ZRI which we obtained originally for our project. The methodology of the ZRI is here. I will move to PR to review the changes. Quick estimates using Zillow rental index downloaded recently. quick coefplot: We observe an effect a few months before the change. This is consistent with the methodology: "Once the index is computed, it is smoothed using a three-month simple moving average." |
Continues in #254 |
The ZORI methodology reports
What does this mean? ChatGPT's interpretation:
I read this as implying that we should observe an effect three months in advance to the MW change. |
Don't trust ChatGPT on this one @santiagohermo! Usually 3-month moving average means 1 month before, the current month, and the next month. Most statistical packages, like this, have a window parameter that governs periods around the period and not before! |
Anyways I read as we should observe effects starting the period before and through the second month after. |
Thanks @diegogentilepassaro! I agree, I would think of centering the window in the current month. But maybe data scientists in Zillow think differently? For example, this data.table function computes a moving average using the previous months by default (see In this figure I find effects that start in -4, which could be explained by a smoothing like the one proposed by ChatGPT. Anyway, after we do the analysis we can try to understand why it looks like it does! |
Thanks @santiagohermo! Actually, what you are saying makes a lot of sense in the light of the fact that they don't observe day one month ahead as one would do doing research based on past data. I agree with your plan |
* Adding zri to estimation_samples #252 * Dropping unwated pyc files #252 * Add new zori 2023 variable in `/base/` # * Add zori 2023 to `zipcode_month` and `estimation_samples` #252 * Add zori_2023 as a rental variable in `estimation_samples` #252 * Go back to original make_main_samples.do #252 #254 * Re-runnnn #252 #254 * Fix to bring back listings dataset #252 * Fix to keep all zipcodes #252 --------- Co-authored-by: santiagohermo <santiagohermo@users.noreply.github.com>
Summary: In this issue we added a ZORI variable to the repo. We plan to use this variable for estimation in #260 |
As part of our review of the paper we will estimate the effect of the MW on rents using the Zillow rental index. While this index on a particular month is a moving average of months around it, it adjust for variation in the available postings each month.
The text was updated successfully, but these errors were encountered: