-
Notifications
You must be signed in to change notification settings - Fork 101
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
Progress report and discussion topics for 12-19-14 meeting #10
Comments
One other thing to add to this list is naming conventions - PEP8 conventions say variables should be named number_persons_age_5_to_15 while most of the variables currently are named like numPersAge5to15. I've changed most of these in the code to match PEP8 conventions but want to make sure people are OK with this. Column names in tables might need to be changed too which I haven't done yet. |
@fscottfoti Thank you for pulling together this thorough update on the progress for the last two weeks. It's been nice to follow the progress you and Matt are making via the frequent documentation in GitHub. A few thoughts on where we are and where we may want to go on the issues outlined above. Code
Configuration Files:
Relationship to UrbanSim
Performance
Naming Conventions
Next Models
|
I concur with @danielsclint that this update was very fun to review and I appreciate the sending of this report with links to everything. Pretty Sweet. One thing that may be useful in the future is to discus specific design questions in their own issues so they are easier to follow. But for now, I will follow Clint's lead and just add my thoughts here. Config file formats
Performance
|
It was interesting to keep up with software development over the past couple of weeks, very transparent process, much appreciated, many thanks. That said, a few comments: I agree that we should not have to have Urbansim installed in order to run Activitysim, though leveraging the Urbansim architecture is most definitely ok and the way to go. Distributed processing across servers should be as flexible as possible. CDAP as the next model component to tackle is one more step heading in the right direction with this project moving forward. |
* NMTF person available periods * NMTF person available periods * blacken * remove bad path to annotate.py * remove bad path to annotate.py * time_periods_available unit test * removing outdated comment * estimation mode tour checking
Progress since the last meeting
Infrastructure
Specific Models
DataFrame.eval
or straight Pythoneval
when there is an@
as the first character. Allows more flexibility in the csv than is provided in current yaml files.TAZ
) should occur in the choosers and is used as the origin id and the alternatives and is used as destination idThoughts?
The text was updated successfully, but these errors were encountered: