Skip to content
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 the role of parcel_sizes settings in proforma #160

Open
hanase opened this issue Dec 11, 2018 · 2 comments
Open

Investigate the role of parcel_sizes settings in proforma #160

hanase opened this issue Dec 11, 2018 · 2 comments

Comments

@hanase
Copy link
Collaborator

hanase commented Dec 11, 2018

The yaml file of the feasibility model sets parcel_sizes to 10000. It says here that the value does not matter because it cancels out in the pro-forma computation. Is that true? How do the forms change if we change this value?

@hanase
Copy link
Collaborator Author

hanase commented Dec 12, 2018

Various proforma values are computed "per sqft", so for those it does not matter. However, the parcel_sizes constant influences the construction time which influences the profit. It should be computed on the actual parcel sizes. Or, does it matter if construction time for all parcels was computed with the same value and thus, influences all proposals the same way?

@hanase
Copy link
Collaborator Author

hanase commented Dec 17, 2018

The settings of parcel_sizes does matter in terms of the profit comparisons between parcels. The picture below compares profits for parcels in the tcu form. The profit computed with parcel_sizes of 10,000 is on the x axis, while profit for parcel_sizes of 20,000 is on the y axis. Each dot is one parcel. In the profit computation, the building revenue is the same for both settings, but the total development cost differs because the construction time differs. The max profit difference for this form is 390,005.

profit_parcel_sizes_tcu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant