Project
 
waiting for next time to build since
11/07/2009 04:56:28
progress: 04:56:28 next build in 1 minutes 30 seconds
 
Latest Build
09/04/2009 08:48:26 (build.6)
 

  
BUILD COMPLETE -  build.6
Date of build: 09/04/2009 08:48:26
Time to build: 3 minutes 33 seconds
Last changed: 09/04/2009 08:46:33
Last log entry: Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
Build Artifacts

 Errors/Warnings: (3) 
starting build-latex-docs

starting build-tutorials

starting copy-to-webserver

 Unit Tests: (0)
No Tests Run
This project doesn't have any tests
 

 Modifications since last successful build:  (8)
modified jrayers /trunk/opus_docs/manual/part-model-system/parcel-data.tex 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/models/development_project_proposal_sampling_model.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/development_project_proposal_component/percent_of_development_this_year.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/models/building_construction_model.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/models/development_project_proposal_regression_model.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
added jrayers /trunk/urbansim_parcel/development_project_proposal_component/annual_construction_schedule.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/development_project_proposal_component/cummulative_amount_of_development.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.
modified jrayers /trunk/urbansim_parcel/development_project_proposal/land_area_taken.py 09/04/2009 08:46:33 Fixing velocity functions and adding a new feature to velocity functions. It is no longer necessary to have a velocity function "pre-determined" for every template component (no more velocity_function_id on the develompent_template_components dataset). Now the velocity_functions dataset should have building_type_id, minimum_units, and maximum_units fields. The total number of units proposed combined with the building type will determine which velocity function gets selected. This way, the velocity at which the project builds can vary depending on how large the project is. Presumably larger projects will take longer to build.